Skip to main content
All API requests require a Bearer token in the Authorization header.

API keys for your own code

Create a read-only key in Settings > Connected apps. It starts with hdk_ and is shown once. Copy it then. For a no-code walkthrough, see API keys.
An API key can call Store data and GET /sync/status. Other endpoints return 403 developer_route_not_allowed. Rotate a key to get a new secret; the old one stops working right away. Revoke it to turn it off.

Desktop agent key

  1. Go to Settings > Profile
  2. Your API key is displayed in the “Account” card (any paid plan)
  3. Click “Reveal” to see it, “Copy” to copy it

Using the API key

Include it in every request:

Hosted MCP usage

After your monthly assistant allowance, one credit covers a 100-unit block. Two one-unit reads share that credit.

Examples

curl

Python

Node.js

Security

  • Your API key is unique to your account
  • It provides full read and write access to your account: inventory, orders, sales, pricing rules, lists, and pricing actions. Unlike OAuth connector tokens, it is not scope-limited
  • Never share it or commit it to version control
  • Store it in your .env file, not in workflow YAML or scripts
  • If compromised, regenerate it from Settings > Profile. Click “Regenerate key”. The old key stops working immediately, so update your agent’s .env with the new key to reconnect

Error responses

401 — Invalid or missing API key

The code: "unauthorized" field is machine-readable. Check for it programmatically to distinguish authentication failures from other errors.

403 — Account suspended