Resend a specific order

Did your recipient accidentally delete or misplace their reward email? They may have mistaken it for spam or perhaps they don’t have access to that email address anymore. Tango portal allows you to resend an email to the recipient using POST /orders/{referenceOrderID}/resends. Resending a reward does not create a new order—it simply reissues the original reward email. There are no additional fees for resending a reward.

Using this endpoint, you can resend reward emails to the original recipient on demand. To resend an order via mail, you must set the sendEmail=true. This triggers Tango to send the original reward email.
If sendEmail was originally set to false, the email was never sent—so it cannot be resent.

Use the following endpoint to resend a specific order:

EndpointPurpose
POST {URI}/orders/{referenceOrderID}/resendsResend a specific Order.

📘

Note:

  • You can resend an order to a different email address, 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 instead of resending the reward email using this endpoint.

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 paramsData typeRequirementDescription
referenceOrderIDstringrequiredReference Order ID (returned in the Order response payload) is required to resend a reward.

🚧

Coming soon

This endpoint will soon be modified to allow resending a specific order via PHONE using newDeliveryMethod and newMobile as body parameters:

  • If both newEmail and newMobile are submitted (not NULL) you can update both email and phone number but resend your reward based on newDeliveryMethod.
  • If an original order was sent using EMAIL , you can resend withPHONE, and vice versa.
  • If deliveryMethod=NONE , you can update the existing email and phone number, but the Tango system will not resend the message.
  • If your original order had not used Tango for delivery (deliveryMethod=NONE), you can resend the order using Tango (newDeliveryMethod=EMAIL or newDeliveryMethod=PHONE).
  • If deliveryMethod is NULL, you can use the original order’s deliveryMethod or sendEmail value.

The following body parameters are available for resending orders with this endpoint:

Body paramsData typeRequirementDescription
newEmailstringoptionalA new email to resend the Order to. If not provided, the original order email will be used for when sendEmail=true.

(🚧 Coming soon) If new email value is missing, use the original order email. deliveryMethod indicates email as the method of delivery only when deliveryMethod=EMAIL.
newMobile
(🚧 Coming soon)
stringoptionalA new mobile number to resend the order to. If missing, use the original order mobile number when deliveryMethod=PHONE.
Consider the following rules when adding new mobile numbers for PHONE delivery:

- Country Code: Must be included.
- Format: +CCCPPPPPPPPPPPP (where C is the country code, 1-3 digits, and P is the phone number, up to 12 digits).
- Initial Release: Only accepts US phone numbers (Country code = +1) and 10 digits for the phone number.
-Standard: Follows ITU E.164, allowing (+) and up to 15 digits for the combined country code and phone number.
newEtidstringoptionalA new ETID (Email Template ID) to resend the order to. If missing, use the original order email whendeliveryMethod=EMAIL. ETID is a unique identifier for each reward email template saved to your Tango platform. The default Email Template ID is E000000.
newDeliveryMethod
(🚧 Coming soon)
enumoptionalSpecify the delivery method for an order to determine how a reward is sent to a recipient. deliveryMethod will replace sendEmail once released:
-NONE: Tango does not deliver. You are responsible to deliver the rewards to your recipient. This option is similar to sendEmail=false.
-EMAIL: Tango delivers the reward to the recipient via email. You must include the recipient email. This option is similar to sendEmail=true.
-PHONE: Tango delivers the reward to the recipient via text. You must include the recipient mobile number.
-ADDRESS: Tango delivers the physical rewards via a carriers such as the post office, FexEx, UPS, etc. You must include the recipient address.
-EMBEDDED: You will embed Tango's lading page into your application. Tango will not deliver the rewards.

The following payload example shows an order is 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 codeMeaning
201New resource has been successfully created as a result of the request.
400The server could not understand the request due to invalid syntax.
401Authentication is required and has either not been provided or failed.
403The server understood the request but refuses to authorize it.

© 2025 Tango API are provided by Tango, a division of BHN, Inc.