Update Reward Statuses in Bulk
PATCH/partner/rewards/_bulk_v2
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
toDENIED_BY_MERCHANT
orPENDING_MERCHANT_FUNDING
.- When updating reward statuses to
DENIED_BY_MERCHANT
, thenotes
field must be populated with an explanation for the denial.
- When updating reward statuses to
- Publishers (and Portfolio Managers) may only update rewards with a
status of
DISTRIBUTED_TO_PUBLISHER
toDISTRIBUTED_TO_CARDHOLDER
. - Only Triple may set the
rejection
andnotification
fields. - Updates to the same allowed status are also accepted. (e.g. PENDING_MERCHANT_FUNDING to PENDING_MERCHANT_FUNDING)
Request
Responses
- 200
- 400
- 403
- 409
- 415
- 422
- 429
- 500
- 501
- 503
Rewards Bulk Response
TripleBadRequestError
TripleNotAuthenticatedError
TripleIntegrityError
TripleUnsupportedMediaType
Rewards Bulk Response
TripleTooManyRequests
Response Headers
The minimum number of seconds to wait before retrying the request.
Request limit per minute.
The number of requests left for the time window.
The time at which the rate limit resets, specified in UTC epoch time (in seconds).
TripleInternalServerError
TripleNotImplementedError
TripleServiceUnavailable