01.software Docs

revokeCustomerRefresh

Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.

All HTTP operations
POST
/api/customers/revoke-refresh

Non-enumerating legacy-direct family logout. Missing/null/malformed/non-JSON/non-string/oversized/foreign/hosted/consumed refresh credentials return identical success; valid <=512-character credentials may revoke a rotated successor. Storage failure returns shaped 503, never fake success.

Authorization

publishableKey
headerX-Publishable-Key<token>

Tenant publishable key for authentication (sent via X-Publishable-Key header)

Request Body

body?CustomerRevokeRefreshInputapplication/json

Any JSON value is tolerated. The handler optionally reads refreshToken only from an object, revokes only string values of at most 512 characters, and otherwise returns the same success. Absent, malformed or non-JSON bodies are also accepted; this schema describes only JSON bodies, not their transport acceptance.

Response Body

Actual shaped success body

application/json
  1. response
success*true
Value intrue

Examples may be generated from schemas; they are illustrative, not recorded successful API calls. Example snippets may omit required authentication headers.

Example Request
curl -X POST 'https://api.01.software/api/customers/revoke-refresh'
Example Response
{  "success": true}