Update Reward Statuses in Bulk (Beta)

This endpoint provides significant performance advantages, over PATCHing single rewards, when updating large numbers of reward statuses. The behavior of the two endpoints is nearly the same except for some minor differences in how errors are handled.

You should check the result_type of the response to handle errors for individual items. If the top-level request returns a Client Error response (response codes 400-499), no rewards from the batch were updated.

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

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.