Supplier API
API Keys
API keys provide secure access to the Mediloop Supplier API. Each key is unique to your partner account and can be managed from the Developer Portal.
Your API keys
Unique & secure
Each key is unique and can’t be shared.
HTTPS only
All requests must use HTTPS (TLS 1.2+).
Revocable
Revoke or rotate keys at any time.
Scoped access
Keys inherit permissions from your roles.
Your API keys
You can create, view, revoke, and rotate your API keys below.
| Key name | Key | Created | Last used | Status | Permissions | Actions |
|---|---|---|---|---|---|---|
Production KeyPrimary | ml_live_••••••••••••a7f2 | May 10, 2026 | Today, 09:41 | Active | All scopes | |
Sandbox KeySandbox | ml_test_••••••••••••3c9b | May 02, 2026 | Yesterday, 16:22 | Active | Read only | |
Reporting KeyLimited | ml_live_••••••••••••9d1e | Apr 28, 2026 | May 12, 2026 | Revoked | Analytics:read |
Create a new key
Example: Create a new key
cURLJavaScript (fetch)PythonPHP
1curl -X POST "https://api.mediloop.com/v1/keys" \2 -H "X-Tenant-Id: 2f8c9d41-68a6-4b36-8a5b-f8d1c2e3f4a77" \3 -H "Authorization: Bearer YOUR_PORTAL_TOKEN" \4 -H "Content-Type: application/json" \5 -d '{"key_name":"Production Key","scopes":["catalog:write","inventory:write"]}'Available scopes
Scopes define the level of access your key has.
catalog:readRead catalog datacatalog:writeCreate and update catalog datainventory:readRead inventory and stock levelsinventory:writeUpdate inventory and stock levelsorders:readRead orders and order itemsorders:writeCreate and update ordersanalytics:readRead analytics and reportswebhook:manageManage webhook subscriptionsThe response will include the new key. Make sure to copy and store it securely.
You won’t be able to view it again.
You won’t be able to view it again.
Available scopes
Use the minimum scope set needed for the workload. Separate production, sandbox and reporting credentials.
Rate limits
Per-key limits protect integrations from accidental bursts. Monitor returned rate-limit headers.
Best practices
Rotate keys regularly, never place them in client-side code and revoke unused credentials immediately.
Troubleshooting
If a key stops working, verify its status, tenant association, scope set and environment.