Create an API key

Creates an API key. You can bind the key to one or more corpora. A personal key has the same permissions as its owner; any other key carries exactly the roles assigned to it with api_roles, corpus_roles, and agent_roles.

Callers with the corpus_administrator, administrator, or owner role create any API key. Callers holding only other roles must set api_key_role to personal. Only a user can create a personal API key; a request authenticated with a machine credential — an API key, app client, or service account — receives a 403 error.

:::note For more information about the different types of API keys, see API Key Management. :::

Request-Timeoutinteger

The platform makes a best effort to complete the request in the specified seconds, or it times out.

Request-Timeout-Millisinteger

The platform makes a best effort to complete the request in the specified milliseconds, or it times out.

Request body

namestring required

The human-readable name of the API key.

api_rolesApiRole[]

Customer-level roles for this API key.

api_key_role'serving' | 'serving_and_indexing' | 'personal'

The role of the API key. A personal key has the same permissions as its owner. A serving API key can only perform query type requests on its corpora, and a serving_and_indexing key can perform both indexing and query type requests; these two roles are deprecated for creation — assign roles with api_roles instead.

corpus_keysCorpusKey[]

Deprecated: Use corpus_roles instead. Corpora this API key has roles on.

Example request

{
  "corpus_keys": [
    "my-corpus"
  ]
}

Response

The response includes the assigned API key ID, name, secret key, enabled status, API key role, and API policy.

idstring required

The ID of the API key.

namestring required

The human-readable name of the API key.

secret_keystring required

The key used in API requests. Keep the key secure.

enabledboolean

Indicates whether the API key is enabled.