Skip to main content

​
Get your API key

Open your account settings to generate a personal API key. Only the owner and admin roles with Public API permission can generate a key and use this API. The API acts as the key’s owner in their workspace. Resource permissions and request visibility still apply; a valid key does not grant access to every resource. Store the key securely in your server-side environment or secret manager. Do not commit it, log it, or expose it in browser code. Revoke a key in your account settings if it is compromised or no longer needed.

​
Send the bearer token

Set SIIT_API_KEY in your local environment, then send it in the Authorization header on each request:
If authentication succeeds, the API returns HTTP 200:
/ping does not use the /v1 prefix. A successful check confirms authentication; individual resource endpoints can still reject a request based on permissions.

​
Troubleshooting

  • 401: Check that the header contains Bearer followed by a valid, active API key.
  • 403: Check your role’s Public API permission and access to the requested resource.
  • 404 on a request: Check the UID and whether the key’s owner can see that request.
See Errors for response formats, and the quickstart for a first resource query. To connect an MCP client, follow the separate MCP server guide.