Revoke resource access

Revoke one identity resource relationship.

DELETE/api/v1/tenant/customer-identities/{id}/access/{accessId}

Authorization

Use a server-side API key with the listed grants and permitted resource access.

identities:access:manage

Request headers

X-Api-Keyrequired: Your server-side integration credential.

Path parameters

idstring · required: Opaque identifier in the authorized resource scope. Nested identifiers must belong to their parent resource.
accessIdstring · required: Opaque identifier in the authorized resource scope. Nested identifiers must belong to their parent resource.

Response

204No content

A successful deletion has no response body.

Behavior to account for

Provisioning access is separate from issuing sessions. Requested resources must already lie within the integration’s administratively approved resource and delegation policy.

Errors

Authentication failures return 401 or 403. Inaccessible resources return 404. Business and idempotency conflicts return 409. Rate limits return 429 with retry guidance.

Error handling guide

REQUESTAPI key

curl --request DELETE 'https://api.wincora.com/api/v1/tenant/customer-identities/id_example/access/accessId_example' \
  --header 'X-Api-Key: YOUR_API_KEY'

const response = await fetch('https://api.wincora.com/api/v1/tenant/customer-identities/id_example/access/accessId_example', {
  method: 'DELETE',
  headers: {
    "X-Api-Key": process.env.WINCORA_API_KEY
  }
});

if (!response.ok) throw new Error(await response.text());
// No response body.

import os
import requests

response = requests.request(
    'DELETE',
    'https://api.wincora.com/api/v1/tenant/customer-identities/id_example/access/accessId_example',
    headers={
      "X-Api-Key": os.environ["WINCORA_API_KEY"]
    },
    timeout=30,
)
response.raise_for_status()

Keep this API key on your server. Never embed it in browser or mobile code.