Account

Request API key handoff

Changed on

Builds a dashboard link that opens the create-key form prefilled with a suggested name and permissions. Requires only account:read, because it creates nothing, changes nothing, and returns no secret - the new key is issued in the owner's authenticated browser session. Use it when key management is blocked because the calling key lacks api_keys:manage, which cannot be granted through the API by the key that is missing it. Pass replaceApiKeyId to rotate; the dashboard then offers to revoke the predecessor once the replacement exists.

post/api-key-handoff

Request

  • Base URL
    https://api.sequenzy.com/api/v1
  • URL
    https://api.sequenzy.com/api/v1/api-key-handoff
  • Auth
    HTTP bearer

Request body

namestring

Suggested name for the new key. Trimmed to 80 characters in the link.

preset'full_access' | 'read_only' | 'agent_safe' | 'ai_drafting' | 'data_ingest_safe' | 'data_ingest_automations' | 'transactional_sender' | 'marketing_sender'

Suggested permission preset.

scopesstring[]

Suggested explicit permission scopes. Overrides preset when provided.

replaceApiKeyIdstring

ID of the key the new one replaces. Pass the literal string "current" for the key making the request.

Response

Handoff link prepared

successboolean required
messagestring
nextStepsstring[]

Example response

{
  "success": true
}

Changes

  • db3873ca3d4dRevision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

  • ba3a29c6eb33Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status