Resend a specific order
Did your recipient accidentally delete or misplace their reward email or text? They may have mistaken it for spam, or perhaps they no longer have access to that email address. Tango portal allows you to resend an email or text to the recipient using POST /orders/{referenceOrderID}/resends
. Resending a reward does not create a new order—it simply resends the original reward. There are no additional fees for resending a reward. Using this endpoint, you can resend the reward to the original recipient at any time.
Use the following endpoint to resend a specific order:
Endpoint | Purpose |
---|---|
POST {URI}/orders/{referenceOrderID}/resends | Resend a specific Order. |
Note:
- You can resend an order to a different email address or phone number, but it must still belong to the same recipient.
- You must have the original order number to resend an order. The Tango order history call allows searching past orders. The order number is included in the order response.
- You can only resend an order once every 30 seconds. If you attempt to resend it sooner, the system will return an error message that includes a timestamp indicating when the last resend occurred.
- If you’ve delivered the reward credentials directly to your recipients—or prefer not to have Tango handle delivery—you can retrieve the reward details using
GET {URI}/orders/{referenceOrderId}
.
Best practice:If you need to verify reward information for a given order, consider getting information on a list of orders
GET {URI}/orders
.
Resending an email does not guarantee its delivery. If the recipient does not receive an email due to spam filter settings, corporate firewalls, etc. resending an email may not be enough. The underlying problem must be determined and resolved.
The following path parameter is used to identify the order to resend:
Path params | Data type | Requirement | Description |
---|---|---|---|
referenceOrderID | string | required | Reference Order ID (returned in the Order response payload) is required to resend a reward. |
To resend a specific order via PHONE use newDeliveryMethod
and newMobile
as body parameters:
newDeliveryMethod
determines your mode of delivery. If bothnewEmail
andnewMobile
are submitted, you can update both email and phone number but resend your reward based onnewDeliveryMethod
.- If an original order was sent using
EMAIL
, you can choose to resend withPHONE
, and vice versa. - If
deliveryMethod=NONE
, you can update the existing email and phone number, but the system will not resend the message. IfdeliveryMethod
isNULL
, however, the system will use the original order’sdeliveryMethod
value. - If your original order had not used Tango for delivery (
deliveryMethod=NONE
), you can resend the order using Tango (newDeliveryMethod=EMAIL
ornewDeliveryMethod=PHONE
).
The following body parameters are available for resending orders with this endpoint:
Body params | Data type | Requirement | Description |
---|---|---|---|
newEmail | string | optional | A new email address to resend the Order to. If not provided, the original order email will be used when original |
newMobile | string | optional | A new mobile number to resend the order to. If missing, use the original order mobile number when original
|
newEtid | string | optional | A new ETID (Electronic Template ID) to resend the order. If missing, use the original order ETID. ETID is a unique identifier for each reward digital template saved to your Tango platform. The default Template ID is E000000. |
newDeliveryMethod | enum | optional | Specify the delivery method for an order to determine how the reward will be resent to the recipient.
|
The following payload example shows an order being resent using POST {URI}/orders/{referenceOrderID}/resends
.
{
"id": 0,
"legacyId": "string",
"createdAt": "2024-03-25T22:46:39.922Z",
"email": "string"
}
The possible response codes for this endpoint are as follows. For details, see i18nkey codes and their error messages:
Response code | Meaning |
---|---|
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. |
Updated 8 days ago