API Keys
API keys are used for organization-scoped TIA APIs.
API key management
Create a key, then use it from your backend
Open API keys and create a named key
Create one key per service or environment so it can be identified and revoked independently.
Copy a server-side example
Use the cURL, JavaScript, or Python request example and keep the key out of browser code.
Create a key
Open Settings → API keys, choose Create API key, and give the key a name that identifies the system using it—for example, production-zapier or order-service.
Copy the secret when it is shown. For safety, TIA does not display the full secret again. Store it in your server's secret manager and never place it in browser code, a public repository, or a support message.
Use and rotate keys
Send the key from your backend using Authorization: Bearer YOUR_API_KEY or the x-api-key header. Keys are bound to the workspace in which they were created.
Create a replacement before revoking an in-use key. Update the consuming service, verify one successful request, then revoke the old key.
Use them for backend integrations that manage agents, sources, tools, or organization metadata. Keep API keys server-side and rotate keys when access changes.