Tango Reserve Backend URL Routing Update (Action May Be Required)

We have made  infrastructure and application changes to Tango Reserve to route backend traffic through centralized API gateways. This enables enhanced traffic management to improve reliability and observability.

ACTION MAY BE REQUIRED SOON

If you already allow-listed the new URLs, there’s no need to undo that change. Once we have a more concrete timeline, we will provide at least one month’s notice for the migration. However, you may begin using the new URLs now.

What's changing:

Our service endpoints now use new base URLs. These changes are automatically handled by our applications and interfaces.

Who this affects:

Most Reserve customers do not need to take any action. However, you may be affected if either of the following applies:

• You consume our APIs directly (outside of our provided interfaces)
• You’ve configured URL or IP allowlists (whitelists) on your network

Customers who use our applications only and have no network restrictions for Reserve URLs do not need to take any action.

If this affects you:

Please ensure that the following “new” URLs are allowed in your firewall or networking configuration, based on your Reserve region and environments:

• CANADA PROD: cabackend.tangoreserve.com (previous) → caforumgateway.tangoreserve.com (new)
• US PROD: prodbackend.agilquest.com → forumgateway.agilquest.com
• SANDBOX: apiforumbackend.agilquest.xyz → sandboxgateway.agilquest.xyz
• STAGING: stagingbackend.agilquest.com → sforumgateway.agilquest.com

You may begin allow listing and using the new URLs now. We will announce a date when we will complete the switch and route all internal traffic through the new URLs.

If your systems depend on allow listed URLs or direct API access, you must update your configuration before the set date  to avoid service disruption.

If you have any questions or need assistance, please open a support ticket.