Revoke an M2M API client. The local row is revoked FIRST (that is what cuts access, because the auth middleware rejects tokens for revoked rows immediately), then the Stytch client is deleted best-effort. A Stytch cleanup failure is logged at ERROR (routed to the internal error notifier) but does not fail the request: access is already cut.

DELETE

/account/m2m_client/{m2m_client_id}

const url = 'https://api.siteqwality.com/account/m2m_client/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';
const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url https://api.siteqwality.com/account/m2m_client/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'Authorization: Bearer <token>'

Authorizations

bearer_auth

Parameters

Path Parameters

m2m_client_id

required

string format: uuid

M2M client identifier (local id, not the Stytch client_id)

Responses

200

Client revoked

401

Missing or invalid authentication

403

Caller lacks the owner or admin role

404

Client not found

500

Internal server error