Resend a line item
This endpoint is particularly useful to ensure a reward is received again when the recipient has accidentally deleted, or hasn't received their reward due to an email delivery issue or technical glitch.
Note:
- You can't change the brand, value, or message of a reward that has been sent to its recipient. However, you can resend rewards to a different email address of the original reward recipient.
- You can resend a reward email to a different email address of the original recipient if they no longer have access to the original email address. for example, an outdated work email.
- You can't resend a reward email if any reward or physical gift card is sent by mail.
Use the following endpoint to resend a specific Line Item to the same email address on the platform.
Endpoint | Description |
---|---|
POST {URI}/lineItems/{referenceLineItemId}/resends | Resend a specific line item on this platform. |
Replace {URI} with the base URI of your API, and replace {referenceLineItemId}
with the unique identifier of the line item you want to resend.
The following path parameter is a required parameter. It represents the unique identifier of the line item you want to resend. This ID is autogenerated by the system and can be found in the response payload when you initially retrieve the line item:
Path params | Data type | Requirement | Description |
---|---|---|---|
referenceLineItemID | string | required | Reference line item ID is returned in the line item response payload. |
🚧 Coming soon: The following body parameters can be used to provide a "Reason" when performing a resend action for a reward. It enables you to specify why a reward is being resent to a recipient, improving tracking and context for resend actions
Body params | Data type | Requirement | Description |
---|---|---|---|
newDeliveryMethod | string | optional | The delivery method used to re-deliver the reward. If no delivery method is designated, the redelivery will use the delivery method used on the original order. |
newEmail | string | optional | A new email address to re-deliver this order to. If missing, use the original order email if |
newMobileNumber | string | optional | A new mobile number to re-deliver this order to. If missing, use the original order |
newEtid | string | optional | A new Email Template Identifier (ETID) is used to re-deliver an order. If missing, use the original order ETID. |
reasonCode | string | optional | Provide a reason why you are resending a reward such as: not received or lost/deleted. See Get all reason codes. The available reason codes are: |
otherReason | string | optional | Required when |
The following example shows the payload for when you resend a specific line item to the same email address:
{
"id": 0,
"legacyId": "string",
"createdAt": "2025-08-11T21:44:21.656Z",
"deliveryMethod": "NONE",
"email": "string",
"mobileNumber": "string",
"reasonCode": "NOT_RECEIVED",
"otherReason": "string"
}
The possible response codes for this endpoint are as follows. For details, see i18nkey codes and their error messages:
Response | Description |
---|---|
201 | New resource has been successfully created as a result of the request. |
400 | The server could not understand the request due to invalid syntax. |
401 | Authentication is required and has either not been provided or failed. |
403 | The server understood the request but refuses to authorize it. |
404 | The server could not find the requested resource. In other words, the URL you’re trying to access doesn’t point to anything that exists on the server. |
Updated about 22 hours ago