API keys

An API key lets your own system talk to Clakta, most often to send orders from your server. Keys belong to the team, not to a project, and have their own permissions, separate from your personal role. You only need one if a developer is connecting your system to Clakta.

Create a key

Go to Team settings → API keys and click Add API key. Only team owners can create, edit or delete keys; members can see the list.

Name

Name it after where it runs, such as Production backend or Staging. If you ever need to delete one in a hurry, the name tells you which.

Permissions

Each area gets a level: None, Read or Write. Write includes read.

You can start from one of three presets, All, Read only or Restricted, and adjust.

Copy it right away

The key is shown only once, right after you create it. Nobody can see it again afterwards, not even Clakta support. If you lose it, delete the key and create a new one.

Use it

Send the key in the Authorization header, with Bearer before it:

curl https://api.clakta.com/v1/orders \
  -H "Authorization: Bearer $CLAKTA_API_KEY"

await fetch("https://api.clakta.com/v1/orders", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.CLAKTA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify(payload),
})

Without Bearer , you get a "Misconfigured authorization header" error.

Keep keys safe

Follow and delete keys

The keys list shows when each key was Last used, the quickest way to find keys nobody uses any more. Team settings → API logs shows the requests made with your keys, which is where to look when an integration starts failing.

Deleting a key takes effect immediately and can't be undone: anything using it fails on its next request. When replacing a key, update your system first and delete the old key after.

Request limits

How many requests per minute you can make depends on your plan: 60 on Free, 300 on Starter, 600 on Pro, 1,200 on Business. See Plans and limits.