Choose SDK or API
Antla has two developer integrations on the same Shopify store. Both use one Headless key. They differ in who renders Try On and whether Shopify Storefront tokens are stored in Antla.
Pick a path
Section titled “Pick a path”| You want | Connect in Antla | You build |
|---|---|---|
| Antla’s button, modal, upload, and cart on a headless Shopify page | Headless SDK | Placement, product and variant IDs, cart identity |
| Your own UI, a partner app, or a native client, talking HTTP only | Headless API | UI, photos, identity, polling, errors, cart |
The Online Store theme embed is a third path. It is documented at antla.io/docs. It is not this site.
Shared key, two flags
Section titled “Shared key, two flags”The merchant copies Antla SDK key or Antla Headless key. Those labels are the same publicKey. Every HTTP request sends it as X-Antla-SDK-Key.
Connecting the SDK stores Storefront tokens and sets sdkEnabled. Connecting the API sets apiEnabled and does not ask for tokens. Either flag is enough for generation endpoints. Both flags can be on at once.
Refreshing the key stops the SDK and the API immediately.
What /context does
Section titled “What /context does”GET /context returns the Storefront GraphQL URL and public token. It requires the SDK connection. An API-only installation responds 403 with SDK_NOT_CONFIGURED.
The browser SDK calls /context for you. A custom UI that already has product IDs does not need it. Cart still uses Shopify’s Storefront Cart API. API-only apps obtain those Shopify credentials from the merchant’s Shopify admin, not from Antla.
For Antla’s UI, Connect Headless SDK, then Headless storefront.
For your own HTTP client, Connect Headless API, then Custom UI workflow.