Skip to main content
GET
/
v1
/
api-keys
/
{id}
Retrieve an API token
curl --request GET \
  --url https://{instance}.omniapp.co/api/v1/api-keys/{id} \
  --header 'Authorization: Bearer <token>'
{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "name": "CI deployment key",
  "type": "organization",
  "enabled": true,
  "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.

Authorizations

​
Authorization
string
header
required

Can be either an Organization API Key or Personal Access Token (PAT).

Include in the Authorization header as: Bearer YOUR_TOKEN

Path Parameters

​
id
string<uuid>
required

Token UUID. The token must exist in the authenticating user's organization.

Response

Token found successfully.

​
id
string<uuid>
required

The token's unique identifier.

​
name
string
required

The name given when the token was created. Not unique within an organization.

​
type
enum<string>
required

Token type:

  • organization - Organization API key
  • personal - Personal Access Token (PAT)
  • mcp - MCP OAuth PAT
Available options:
organization,
personal,
mcp
​
enabled
boolean
required

Whether the token can currently authenticate. Organization API tokens can be disabled by Organization Amins; disabled tokens remain visible but cannot authenticate. Personal and MCP tokens are always true.

​
createdAt
string<date-time>
required

ISO 8601 timestamp of when the token was created (UTC).

​
membershipId
string<uuid> | null
required

The user membership the token is scoped to. null if type is organization.