Listadum API
Listadum API
The Listadum API lets you programmatically access your store data, manage listings, and build custom integrations. Whether you want to automate bulk updates, connect Listadum to your own tools, or build reporting dashboards, the API gives you full flexibility.
Getting access
The API is a paid add-on: $10/month, or $120/year if your shop is billed yearly (the add-on follows the same billing period as your main subscription). It sits on top of any paid plan, so you'll need Starter, Growth, or Max. On the Max plan it's included by default, so there's nothing extra to enable.
Turn it on from your Store settings, under the API tab. The add-on has to be active before you can create an API key. API Access stops while your subscription is paused or canceled.
API Access also turns on the MCP connection for AI agents. See Listadum MCP integration. The API can upload photos, videos and digital download files, which MCP can't.
Documentation
The full API reference, including available endpoints, request and response formats, and authentication details, is at https://api.listadum.com/docs. The documentation is interactive: once you have an API key, you can try calls directly from your browser.
Managing API keys
API keys authenticate your requests. Create and manage them from your Store settings, under the API tab. When you create a key, you set:
Name: a label to help you identify what the key is for (for example, "My reporting script").
Scopes: choose the scopes. Read (access store data) and Write (modify listings and store data) are both ticked by default.
Only store owners can create and revoke API keys. Creating a key means accepting the API Terms of Service. For security, the full key is shown only once, at creation, so copy it and store it somewhere safe. If a key is ever compromised, revoke it from the same settings page. Revoked keys stop working immediately.
Rate limiting
To keep the platform stable and usage fair, the API enforces rate limits on all endpoints. If you go over, requests return a 429 Too Many Requests status. Check the response headers to see when you can retry, and build in exponential backoff to handle limits gracefully. Rate limits apply per API key, so using multiple keys for the same store won't raise your overall limit.
Best practices
Use the most restrictive scope your integration needs. Prefer Read when you only need to fetch data.
Store your keys securely and never expose them in client-side code or public repositories.
Handle errors properly and respect rate limits with exponential backoff.
Rotate your keys periodically and revoke any you no longer use.
Requires a paid plan (Starter, Growth, or Max) with the API add-on. Included on Max.
Was this helpful?