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 enter a descriptive name that identifies the integration — for example,
Klaviyo sync, Mobile app, or Internal dashboard. Good names make it easy to audit and revoke keys later.3
Copy the key immediately
The full key value is shown only once. Copy it and store it in your secrets manager or environment variable before leaving the page. If you navigate away without copying it, you must create a new key.
4
Store the key securely
Add the key to your application as an environment variable:Never hard-code the key in source code or commit it to version control.
Using the API key
Include your key in theX-API-Key header on every Admin API request.
Key management
You can create up to 10 active API keys per store. Each key has:- A display name you choose at creation time
- A last-used timestamp so you can identify stale keys
- Individual revocation — revoking one key does not affect others
Rotating a key safely
1
Create the replacement key
Go to Settings → API Key Management and create a new key with the same or updated name.
2
Update your integration
Deploy the new key value to your application and verify it works.
3
Revoke the old key
Return to the dashboard and revoke the old key. Revocation is immediate.
Partner integration keys
If you are building an app that connects to multiple merchants’ stores, use the Partner Integration Framework instead of asking merchants to share API keys manually. The Partner Framework:- Provisions a scoped
apst_token per merchant automatically during a one-click handshake - Lets merchants approve, review, and revoke access from their own dashboard
- Bypasses the paid API plan — merchants are never charged for partner API usage
- Revokes tokens automatically when a merchant disconnects or uninstalls Appstle
X-API-Key. See the integration guide for details on the X-App-Key legacy header and the full partner framework walkthrough.
New integrations should use the Partner Integration Framework. The legacy
X-App-Key header continues to work for existing partners but is not recommended for new builds.