Theme
Insufficient scope
403 · INSUFFICIENT_SCOPE
The key is valid and belongs to this workspace, but was not granted the scope this endpoint needs.
json
{
"type": "about:blank",
"title": "Insufficient scope",
"status": 403,
"code": "INSUFFICIENT_SCOPE",
"detail": "This key does not carry the survey_links:write scope."
}| Endpoint | Needs |
|---|---|
POST /campaigns/{campaign_id}/links | survey_links:write |
DELETE /campaigns/{campaign_id}/links/{link_id} | survey_links:write |
GET /campaigns/{campaign_id}/links | survey_links:read |
GET /campaigns/{campaign_id}/links/{link_id} | survey_links:read |
POST /conversation-metadata | conversation_metadata:write |
Write does not imply read. A key granted only survey_links:write can mint a link and revoke it, but cannot list one back.
What to do
Do not retry. Scopes are fixed at creation and cannot be edited afterwards — create a key with the scopes you need and retire the old one. See Authentication.
Distinguish this from a plain 403 with body {"message":"Forbidden"}, which means the credential itself was rejected at the gateway.
