membershipRecoverySnapshot
Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.
All HTTP operationsRequires an sk01_ key with membership read scope and no Origin header. Reads only existing same-tenant recovery evidence; never prepares a charge or writes custody. DTOs exclude payment-method references, custody and stored PSP values. A discovered console_managed generation returns 409 conflict without recovery evidence.
serverSecretKeyAuthorizationBearer <token>Public integration credential: opaque sk01_ secret API key only; PAT and Customer JWT are not supported by this scheme. Requires tenant binding and the read or write scope named by the operation.
application/json- body
membershipId*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidcustomerRef?string1 <= length <= 512Successful operation
application/json- response
snapshot*Examples may be generated from schemas; they are illustrative, not recorded successful API calls. Example snippets may omit required authentication headers.
curl -X POST 'https://api.01.software/api/memberships/recovery/snapshot' \ -H 'Content-Type: application/json' \ -d '{ "membershipId": "8072cc74-4782-4f2c-827c-699c48ce2092"}'{ "snapshot": { "id": "string", "customer": "string", "plan": "string", "price": "string", "subscribeIntentKey": "string", "customerRefMatches": true, "status": "incomplete", "amount": 0, "currency": "string", "subscribePeriodStart": "string", "subscribePeriodEnd": "string", "currentPeriodEnd": "string", "billingInterval": "month", "intervalCount": 1, "updatedAt": "string", "prepared": { "membershipId": "string", "status": "trialing" } }}