Acenda's REST API lets you manage your products, orders, inventory and fulfillment data programmatically, so you can automate workflows and connect Acenda to your own systems.
The full, up-to-date reference for every endpoint (request formats, parameters and example responses) lives in our Postman collection: Acenda API Documentation. Treat it as the source of truth. This article covers authentication, managing your API keys and common issues.
Don't need custom code? Connect Your AI Assistant to Acenda lets you ask questions about your orders, products and sales in plain language through the Acenda MCP server. It signs in with your normal Acenda login, so no API key is required.
Authentication
Every request to the API needs two headers:
An access token, sent as
Authorization: Bearer YOUR_ACCESS_TOKENYour organization name, sent as
X-Astur-Organization: YOUR_ORG_NAME, so Acenda knows which store's data to use
You get an access token by exchanging a Client ID and Client Secret, which you generate yourself under ADMINISTRATION > Users > API Keys (steps below). For the exact token request, see the authentication section of the Postman documentation.
Building a new integration rather than making a one-off call? The Acenda API v3.2 Guide covers common integration patterns, like processing Ship Advice, and security practices such as using a separate key per integration.
Creating and managing API keys
API keys are self-service. You don't need to contact support to get one.
To create a key:
In the sidebar, under ADMINISTRATION, click Users, then open the API Keys tab.
Click Create New Key.
Enter a Name and Description (for example, which system the key is for), then click Save.
Copy the Client ID and Client Secret shown in the table right away.
Important: your Client Secret is only shown in full right after you create or regenerate it. Once you leave the page it displays as hidden, so store it somewhere secure, like a password manager. If you lose it, regenerate the key. Never paste a real key or secret into a support ticket, email or shared document.
To revoke or rotate a key:
Click Delete next to a key to remove it permanently. Anything using that key stops working immediately.
Click Regenerate to issue a new secret for the same key without creating a new Client ID. The old secret stops working as soon as you do this.
Tip: create a separate key for each system you connect instead of sharing one key everywhere. That way you can revoke access for one integration without affecting the others.
Syncing a full catalog, inventory or pricing file instead of making live calls? See FAQ: Automating Catalog Updates with the Import & Export API. It uses the same kind of key but is built for bulk jobs, with its own request limits.
Troubleshooting
401 Unauthorized: your access token is missing or expired, or the key behind it was deleted or regenerated. Get a fresh token with your current Client ID and Secret, or check ADMINISTRATION > Users > API Keys to confirm the key still exists.
403 Forbidden: your access token is valid but doesn't have permission for that resource, or the
X-Astur-Organizationheader names the wrong organization. Check the header first, then contact Acenda Support to check what your organization's Api Client role allows.It worked before but stopped suddenly: someone likely deleted or regenerated the key under ADMINISTRATION > Users > API Keys. Regenerating keeps the same Client ID but issues a new secret, so anything using the old secret needs updating.
429 Too Many Requests: you've hit a rate or quota limit on that endpoint, for example the Import & Export API's limit on active previews. Space out your requests and check that endpoint's documentation for its specific limit.
Related articles
Still stuck? Contact Acenda Support and include your organization name and the endpoint or error you're seeing. Never include your Client Secret or access token.