Set up APIs & MCP access
Activate developer access, choose permissions, and securely generate a key for your store.
Select the right store and open developer access
In the CRM, select the store you want your integration to access. Go to Settings → More settings → APIs & MCPs. Each key and project ID belongs to the selected store.
Check your subscription
The APIs & MCP subscription is separate from the storefront’s one-time business investment. If developer access is inactive, choose View subscription to open License & subscriptions and activate APIs & MCP. The paid subscription is USD 60 per month; an active trial also provides access.
Choose API permissions
Under Choose API permissions, select the read and write scopes your integration needs. Select at least one permission. Editing the selection takes effect when you generate a new key; it does not change the current key on its own.
Generate and copy the key
Choose Generate API key and confirm. The page scrolls to Copy your API key now so you can use Copy API key. Save it securely before hiding it or leaving this page. A generated key is shown only in this page’s memory; Refresh status checks access but cannot retrieve a hidden or lost key.
Copy the project ID and follow the integration instructions
Use Copy project ID on the same page. REST requests need both Authorization: Bearer YOUR_API_KEY and X-Project-ID: YOUR_PROJECT_ID. Open Read the API documentation for endpoints, examples, the request tester, and the OpenAPI contract. Follow your connecting tool’s instructions for its API or MCP configuration.
Replace a key or change its permissions
To rotate access or change scopes, select the required permissions, choose Generate a new key, and confirm. The previous key stops working, so update every connected tool with the new key and the matching project ID.
Revoke access when it is no longer needed
Choose Delete API key and confirm to revoke it. Connected tools using that key lose access. Keep keys in your server’s secret store or a password manager; never put them in public websites, URLs, repositories, or messages.