Update Reward Statuses in Bulk

This endpoint provides significant performance advantages, over PATCHing single rewards, when updating large numbers of reward statuses.

This endpoint is currently rate limited at 5 requests per minute.

Request Semantics:

This endpoint uses all-or-nothing semantics. If even one reward fails to update, the entire request will return a failure response.

Constraints:

• Content Providers may only update rewards with a status of PENDING_MERCHANT_APPROVAL to DENIED_BY_MERCHANT or PENDING_MERCHANT_FUNDING.
  • When updating reward statuses to DENIED_BY_MERCHANT, the notes field must be populated with an explanation for the denial.
• Publishers (and Portfolio Managers) may only update rewards with a status of DISTRIBUTED_TO_PUBLISHER to DISTRIBUTED_TO_CARDHOLDER.
• Only Triple may set the rejection and notification fields.
• Updates to the same allowed status are also accepted. (e.g. PENDING_MERCHANT_FUNDING to PENDING_MERCHANT_FUNDING)