Skip to main content
PATCH
/
v1
/
organization
/
api-keys
/
{id}
Update API Key
curl --request PATCH \
  --url https://api.signa.so/v1/organization/api-keys/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "scopes": [
    "<string>"
  ],
  "expires_at": "<string>",
  "metadata": {}
}
'

Documentation Index

Fetch the complete documentation index at: https://docs.signa.so/llms.txt

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

​
Overview

Updates an API key. The raw key value is never affected — use Rotate API Key to issue new credentials. Metadata uses merge semantics (null values remove keys). Scope changes are subject to escalation prevention: you cannot grant scopes that the calling key does not already hold. System keys cannot be modified. Requires the api-keys:manage scope.

​
Path Parameters

​
id
string
required
API key ID (key_...).

​
Request Body

​
name
string
New name (1-255 characters).
​
scopes
string[]
Replacement scope list (at least one). Subject to escalation prevention.
​
expires_at
string
New expiry as an ISO 8601 timestamp, or null to clear. Must be in the future.
​
metadata
object
Metadata patch. Values may be strings or null.

​
Response

Returns the updated API key. Same shape as Get API Key.

​
Code Examples

curl -X PATCH "https://api.signa.so/v1/organization/api-keys/key_abc123" \
  -H "Authorization: Bearer sig_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Production server (renamed)",
    "scopes": ["trademarks:read"],
    "metadata": { "owner": "platform-team" }
  }'

​
Errors

StatusTypeDescription
400validation_errorEmpty name, invalid scope, expires_at not in the future
401unauthorizedMissing or invalid API key
403forbiddenAPI key lacks api-keys:manage, target key is a system key, or scope escalation attempted
404not_foundAPI key does not exist or belongs to another org