Need help? Get answers from the docs with Omni's in-app AI! Log in to your Omni instance and open the Omni Agent in the sidebar.
curl --request PUT \
--url https://{instance}.omniapp.co/api/v1/api-keys/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"enabled": false
}
'{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"name": "CI deployment key",
"type": "organization",
"enabled": false,
"createdAt": "2026-04-20T10:00:00.000Z",
"membershipId": null
}This endpoint requires Organization Admin permissions.
Disable or re-enable an API token. To permanently revoke a token, use the Delete API token endpoint.
This operation is idempotent: calling it twice with the same body produces the same result.
curl --request PUT \
--url https://{instance}.omniapp.co/api/v1/api-keys/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"enabled": false
}
'{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"name": "CI deployment key",
"type": "organization",
"enabled": false,
"createdAt": "2026-04-20T10:00:00.000Z",
"membershipId": null
}Documentation Index
Fetch the complete documentation index at: https://docs.omni.co/llms.txt
Use this file to discover all available pages before exploring further.
Can be either an Organization API Key or Personal Access Token (PAT).
Include in the Authorization header as: Bearer YOUR_TOKEN
UUID of the API token. The token must exist in the authenticating user's organization.
Determines if the API token is enabled: false to disable the token, true to re-enable it.
Token updated successfully. Returns the current state of the token, or the same state if already in the requested state.
Unique ID for the token.
Token name.
Token type.
organization, personal, mcp Whether the token is enabled.
ISO 8601 timestamp of when the token was created.
Membership ID of the user who owns the token. null for Organization API keys.
Was this page helpful?