Skip to main content
Every Admin API request must include a valid API key in the request header. Keys are created and managed directly in your Appstle dashboard, scoped to a single Shopify store, and can be revoked individually without affecting your other integrations.

Creating an API key

1

Open API Key Management

Log in to your Appstle admin panel and navigate to Settings → API Key Management.
2

Create a new key

Click Create New Key and give it a descriptive name that identifies the integration — for example, Klaviyo Integration, Mobile App, or Zapier Workflow.
3

Copy the key immediately

Your new key is displayed only once. Copy it now and store it in a secure location such as an environment variable or a secrets manager. You cannot retrieve the full key value again after leaving this screen.
4

Use the key in your requests

Pass the key in the X-API-Key header of every Admin API request.
Never expose your API key in client-side JavaScript, browser applications, or public source code repositories. API keys must only be used in server-side code.

Sending the API key

Include your key in the X-API-Key request header:
You can also pass the key as a query parameter using ?api_key=apst_your-api-key-here, but the header approach is recommended for security.

Key format

All API keys use the apst_ prefix. Existing legacy keys created before this prefix was introduced continue to work without any migration required.

Key management

You can create up to 10 active API keys per store. Managing keys from the dashboard gives you fine-grained control over which integrations can access your membership data.
Create a separate API key for each integration. This way you can revoke access for a single integration without disrupting others — for example, if a third-party tool is compromised or decommissioned.

Storing keys securely

Store your API key as an environment variable and read it at runtime. Never hardcode it in your source files.

Authentication errors

If your request is rejected due to authentication, you will receive a 401 Unauthorized response:
Common causes:
  • The key was revoked from the dashboard
  • The key was copied with extra whitespace
  • The X-API-Key header is missing from the request
  • You are using a key that belongs to a different store

Partner integrations

If you are building a product that integrates with Appstle Memberships on behalf of multiple merchants (a CRM, helpdesk, email platform, or automation tool), use the Partner Integration Framework. Merchants connect your app with one click — no manual key exchange — and Appstle issues your app a scoped apst_... token for each approved store. Send the merchant’s scoped token as X-API-Key, exactly like a regular API key. Tokens are revoked automatically when a merchant disconnects or uninstalls Appstle. To get onboarded, email support@appstle.com with your company name, product description, base URL, and contact email.
Partner integrations bypass the paid API plan — merchants are never charged for your integration’s API usage. Direct API access (without a partner connection) requires an active API plan.