ixidocs
Sign in
your organizationfeature

secrets and API keys

store keys your sandbox scripts need, and create org keys for ixi's developer APIs.

Two tabs in Organization settings hold credentials. Secrets keeps other services' keys for your sandbox scripts. API keys gives your own server access to ixi. Both are for owners and admins; everyone else gets "Only org admins can manage secrets" or "…API keys".

secrets

A secret is a name and a value. Open Secrets, type a name such as OPENWEATHER_KEY, the value, and click Save.

  • Names are uppercase letters, digits and underscores, start with a letter, and run up to 64 characters.
  • Values can't be read back. Saving an existing name replaces its value, which is how you rotate a key.
  • The list shows names only. The trash icon (Delete) removes one.

A sandbox script uses a secret by writing $IXI_SECRET:NAME in a request URL or header. ixi fills in the value on the server, so it never reaches the browser or the canvas. See secrets in sandboxes for how a script declares and uses them.

API keys

Open API keys, type a name such as "prod backend", and click Create key. The new key appears once, starting with ixi_sk_: copy it with the copy button and put it in your server's secret manager. After you leave, only its name and prefix remain.

Click the trash icon (Revoke) to retire a key. Revoking is immediate and invalidates the short-lived tickets it issued.

These keys are server credentials. They start process runs and read tables for the whole organization, so never put one in a browser or an app bundle. Use them with:

Each key can start 200 process runs per 24 hours.

connect claude

The top of the API keys tab has Connect with Claude. It needs no key: you sign in with your own account. See mcp.

limits & good to know

  • Secrets are stored encrypted, and a script that uses one runs only for someone who can edit the canvas.
  • An ixi key sees only its own organization's data.

checked against the product · 2026-10-23