auth.v1.ApiKeyService

DeleteAssistantKeys

Revoke the caller's whole Polyester AI assistant key set. Revocation only removes access, so it needs no step-up proof. Revocation is permanent. As for DeleteApiKey, key management sees it at once, and requests signed with a revoked key are refused within a few seconds of the response.

Method

POST

Path

auth.v1.ApiKeyService/DeleteAssistantKeys

Service

auth.v1.ApiKeyService

Visibility

Authentication required

Authentication

Session token

MFA Requirement

Not required

POST

auth.v1.ApiKeyService/DeleteAssistantKeys

Request

Testnet

curl --request POST \ \
  --url 'https://api.testnet.polyester.com/auth.v1.ApiKeyService/DeleteAssistantKeys' \
  --header 'Content-Type: application/json' \
  --header 'Connect-Protocol-Version: 1' \
  --data '{}'

Responses

{
  "revokedKeyIds": [
    "ak_1a3c6de8153d5a5b04cd2a6529779542"
  ]
}

Request

auth.v1.DeleteAssistantKeysRequest

Response

auth.v1.DeleteAssistantKeysResponse

revokedKeyIds string[]

Opaque identifiers of the keys revoked by this request. Empty when the set was already empty.

Possible errors: 5

Key	HTTP status	Connect code	Error	When
unauthenticated	401	unauthenticated	Unauthenticated	Authentication required.
permission-denied	403	permission_denied	Permission Denied	Permission denied.
invalid-argument	400	invalid_argument	Invalid Argument	Invalid argument.
not-found	404	not_found	Not Found	Not found.
unavailable	503	unavailable	Unavailable	Service unavailable.