Authentication and API keys
Create, use, monitor and revoke QuiQSol API keys, and how AI agents sign in with OAuth instead.
On this page
Every request to the public API carries an API key. A key belongs to one workspace, so it can only read and write that workspace's records.
1. Create a key
Go to Settings, Developer Platform and give the key a name, for example Zapier integration. Click Create.
2. Send it with every request
curl https://api.quiqsol.com/public/v1/contacts \
-H "Authorization: Bearer <your-api-key>"
A missing or revoked key returns 401.
3. Watch how it is used
The key list shows each key's name, prefix and when it was last used, so you can spot a key nobody needs.
4. Revoke a key
Click Revoke next to the key. It stops working at once. Create a new key first if a system still depends on it.
Who can manage keys?
People whose role has Developer permission: read to see keys, manage to create and revoke them. See Roles and permissions.
How do AI assistants sign in?
Claude and ChatGPT connect to https://api.quiqsol.com/mcp and sign in with OAuth. You choose what the assistant may do on the consent screen. Cursor and other clients that take a key use an AI agent key with scopes. See MCP.
How do integrations authenticate?
An integration created under Developer Platform, Integrations gets its own API key and a webhook secret. Both are shown once. See Integrations and webhooks.