This change fixes a long-standing oversight. Now, when an order is submitted using the POST /orders endpoint with an already used (reused) externalRefID, it returns a 200 status code instead of 201. The returned payload will remain the same, returning the original payload from the existing externalRefID, preventing a duplicate order.
Tango has added HMAC-SHA256 as an alternative authentication method for Tango webhooks to improve integration compatibility with third-party products.
The Tango Model Context Protocol (MCP) services enable AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with your Tango API and documentation.
Manage complex, multi-line-item orders where each recipient gets customized rewards via different delivery methods, without exposing sensitive credentials
Low balance alert management is now available through the API, expanding on the existing functionality that has always been accessible via the Tango portal.
You can now send rewards to your recipient's mobile phone! For eligible rewards, you can send them via a text message. We have deprecated the "sendEmail" flag and introduced the "deliveryMethod" to determine how you want to send the reward. Don't worry, if you still use "sendEmail", it will work. You must use "deliveryMethod" if you want to send via text messaging.
With the introduction of Mobile Reward Delivery, we have renamed the emailTemplates endpoints to digitalTemplates. Don't worry, for those using the emailTemplate endpoints - they will still work.
Just like there are "Reasons" for our Freeze, Cancel, and Reissue endpoints, we now have a "Reason" for Resends on the POST /v2/lineItems/{referenceLineItemId}/resends endpoint.
Receive a webhook notification when a transaction has hit an account. Use this endpoint to track this information:GET {URI}/ accounts/{accountIdentifier}. Additionally, use externalRefID to prevent any duplicate fund transfers when calling these endpoints: POST {URI}/creditCardDeposits and POST {URI}/transferFunds.
As of May 14, 2025, the Tango API will require Client ID, Client Secret, Service Account Username, and Service Account Password to generate the Access Token when using OAuth.
