Your store, site or API
Connect WooCommerce, WordPress, Shopify, or a REST or GraphQL API you already run; your key never ships in the app.
Updated Oct 20, 2026

Steps
- Click Server › Backend › HTTP API (with no backend yet: Already have a store or website? › Connect it).
- Pick what the app connects to: WooCommerce, WordPress, Shopify, My own API or GraphQL API.
- Fill in the two or three fields it asks for, then Save and test.
| Backend | You enter |
| --- | --- |
| WooCommerce | Store address, and a consumer key and secret from WooCommerce › Settings › Advanced › REST API › Add key |
| WordPress | Site address; an application password only for private content |
| Shopify | Store address and the public access token from the Headless channel |
| My own API, GraphQL API | The address and how it signs in: no key, a key, a token, username and password, OAuth, or an app ID and secret |
Good to know
- The key is the assistant's, for building and testing. The app calls your API without it: people sign in through your own login, or the endpoints are public. Tick Safe to put in the app only for a key made for apps, such as a search-only key.
- The assistant reads your API freely and asks you in chat before it changes anything there.
- More settings › Test address (such as
/me) lets the test check the key, not only the address. - A Test account (a test customer, not your login) lets the assistant check signed-in screens.
- If every request needs a server key, the assistant puts a Supabase Edge Function or a Cloudflare Worker in between and hands it this connection's key by name.
- An API on your own computer needs a tunnel (Cloudflare Tunnel, ngrok) with an https address.
- Up to four APIs: once one is connected, choose Add another API and give it a short name and a line on what it is for. The assistant then names the API on every call, so it never mixes them up.
- A FluxNative Commerce app reads its store from Your store instead (Connect your store and website).
Related
Did this page help?