Skip to main content
POST
/
v1
/
dev
/
keys
Create API key
curl --request POST \
  --url https://api.omi.me/v1/dev/keys \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "My New Integration"
}
'
{
  "id": "key_789ghi",
  "name": "My New Integration",
  "key_prefix": "omi_dev_ghi789",
  "key": "omi_dev_ghi789_full_secret_key_here",
  "created_at": "2025-01-20T15:00:00Z",
  "last_used_at": null
}

Documentation Index

Fetch the complete documentation index at: https://docs.omi.me/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Developer API key. Get one from Settings → Developer → Create Key in the Omi app. Keys are prefixed with omi_dev_.

Body

application/json
​
name
string
required

Descriptive name for the key.

​
scopes
enum<string>[]

Optional scopes to assign. Defaults to read-only (conversations:read, memories:read, action_items:read, goals:read) if not provided.

Available options:
conversations:read,
conversations:write,
memories:read,
memories:write,
action_items:read,
action_items:write,
goals:read,
goals:write

Response

The created API key with full secret.

​
id
string
​
name
string
​
key_prefix
string
​
key
string

The full API key. Only returned once during creation.

​
created_at
string<date-time>
​
last_used_at
string<date-time> | null
​
scopes
string[] | null

Permission scopes assigned to the API key. Null for legacy keys (treated as read-only).