Skip to main content
POST
/
v1
/
developer
/
keys
/
{id}
/
revoke
RevokeApiKey
curl --request POST \
  --url https://sdk.anghami.com/v1/developer/keys/{id}/revoke \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "<string>"
}
'
{
  "apiKey": {
    "id": "<string>",
    "name": "<string>",
    "keyPrefix": "<string>",
    "status": "API_KEY_STATUS_UNSPECIFIED",
    "scopes": [
      "<string>"
    ],
    "createdAt": "<string>",
    "lastUsedAt": "<string>",
    "expiresAt": "<string>"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.sdk.anghami.com/llms.txt

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

Headers

​
Authorization
string
required

OAuth 2.0 Bearer token. Required for all key management operations. Format: Bearer <access_token>.

Example:

"Bearer eyJhbGciOiJSUzI1NiIs..."

Path Parameters

​
id
string
required

Unique identifier of the API key to revoke.

Body

application/json

RevokeApiKeyRequest is the request message for permanently revoking an API key. Once revoked, the key can no longer be used for authentication.

​
id
string
required

Unique identifier of the API key to revoke.

Response

Successful response

RevokeApiKeyResponse is the response message confirming the key has been revoked.

​
apiKey
object

ApiKey represents a developer API key used for server-to-server authentication. API keys are passed in the x-api-key HTTP header and are billed per key. The full secret is only returned on creation and rotation.