Reactivate Cards in Batch
Reverts the cancellation of up to 100 cards in one call - the way back from Cancel Cards in Batch. Without it, undoing a batch of 100 would be 100 calls.
Same shape as the batch cancel: 200 with the outcome of each item, and 400 only for a
malformed request. Outcomes here are reactivated, not_canceled (the card was not
canceled, nothing done) and not_found. The summary carries amountRestored - how much
balance returns to circulation.
Validity is not touched: a card reactivated after its expiresAt comes back expired,
with the original expiresAt. Reactivating is not extending.
dryRun works the same way as in the batch cancel.
A range never crosses organizations: an id that belongs to another account comes back
not_found and is left untouched - every query here is scoped by organization.
Try-it values populated from environment ACME (Demo)
Authentication
Token
Send your user token in the x-guper-authorization header. Endpoints that
support a Public mode (e.g. acúmulo and resgate previews) accept the same
request without the header — Private mode adds customer data and a
confirmation token to the response.
Headers
Request body
Content-Type:
application/json