Skip to navigation

Void entitlements

View as Markdown

Voids up to 50 entitlements. Entitlements are voided independently, so one entitlement failing doesn’t stop the others from being voided. Check each entry in results for an error field to see which succeeded. If any entitlement fails, the response status is 207 instead of 200. For each entitlement voided:

  • live is updated to false
  • expiration is updated to the time of execution
  • grace_period is updated to 0
  • An EntitlementTransaction is created
  • An entitlement.entitlements_voided event is triggered upon successful modification

The request is checked as a whole before anything is voided. If any ID is invalid, or doesn’t match an entitlement belonging to the authenticated merchant, the request returns 400 or 404 and no entitlements are voided.

Requires Application API Scope authentication.

Request

This endpoint expects an object.
entitlement_public_idslist of stringsRequired
IDs of the entitlements to void. Provide 1 to 50 IDs, with no duplicates or empty values.

Response

resultsmap from strings to objects

Void results, keyed by entitlement public_id.

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
500
Internal Server Error