Resources

API keys (public REST API)

On the Integrations API keys tab you create a key that lets Zapier, Make, n8n or your own script read the products, stock and orders of your company, read-only. The tab is usable once the public API is switched on…

Revised:

1. What is it for?

On the Integrations API keys tab you create a key that lets Zapier, Make, n8n or your own script read the products, stock and orders of your company, read-only. The tab is usable once the public API is switched on for the platform; until then an information message is shown and no key can be created. Only an owner or an administrator can manage keys.

2. Steps – API keys (public REST API)

• Name the key, pick the permissions (products, stock, orders, company details), the expiry and the calls per minute, then choose Create key. • The full key (starting with wra_live_) is shown only once: copy it into a password manager or into the tool that will use it. Later only its beginning is shown. • In the tool, send the key in the Authorization: Bearer header, never in the web address. • The Call log button shows the latest calls of the key (path, status, time). • Rotating creates a new key and the old one keeps working for 24 hours. Revoking stops the key immediately. The daily number of calls depends on your plan (Starter 1 000, Business 10 000, Pro 100 000). When the limit is reached the API answers with a 429 error. The full description is in the developer guide and the OpenAPI description.