nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

REST API URL Update

Retail Express is updating the supported base URL used to connect to the REST API. This change applies only to customers and partners who have been identified as using unsupported REST API base URL variations.

If you have received this communication, one or more integrations you operate may require action. To avoid disruption, you will need to review your REST API integrations and update any unsupported base URLs to use the supported Retail Express REST API base URL: https://api.retailexpress.com.au/

The FAQ below explains what is changing, what action is required, when the change will take effect, and how to validate your integration after the update.

What is changing?

We are updating how integrations connect to the Retail Express REST API.

Going forward, all REST API integrations must use only the following base URL: https://api.retailexpress.com.au/

This has always been the primary URL for the REST API. While alternative URL variations have been supported in the past, they will no longer be supported moving forward and must be updated to use the base URL.

When is the change coming into effect?

The changes will be implemented on the Retail Express side during September, 2026. The exact date wil be confirmed closer.

We encourage your business and any related systems to implement the required changes as soon as possible to allow adequate time for testing and review.

Why is this change being made?

This change is part of ongoing infrastructure improvements to enhance platform reliability, scalability, and performance.

It also ensures all REST API traffic is routed through a consistent and fully supported base domain.

Do I need to take action?

Yes. This communication has been sent to customers identified as using unsupported base URLs within one or more custom integrations.

One or more of your integrations have been developed either internally by your business or by a third-party developer or agency. As a result, any required updates will need to be reviewed and implemented within your custom integration(s) by your developer or agency.

It’s important to note that this does not apply to Retail Express’s native integrations (such as Shopify, Xero, or MYOB), as these are fully managed by Retail Express.

What do I need to do?

You will need to review one or all integrations you are operating and:

Identify any REST API base URLs currently in use where old base URL’s are currently in place.
Replace them with: https://api.retailexpress.com.au/
Test your integration to confirm everything is working as expected

In short: if your base URL does not match https://api.retailexpress.com.au/ it must be updated.

Which URL structures are affected?

Any URL that does not use https://api.retailexpress.com.au/ as the domain will no longer be supported.

This includes (but is not limited to):

https://prdappasvapi001.azurewebsites.net/
https://prdappasvapi02b.azurewebsites.net/
https://prdappasvapi03b.azurewebsites.net/
https://prdappasvapi01b.azurewebsites.net/

As well as any similar variations or environments using different base domains.

Are API endpoints or functionality changing?

No. There are no changes to:

API endpoints
Request and response formats
Authentication
Existing functionality

This is strictly a base URL update only.

When does this need to be completed?

We recommend completing this update as soon as possible to avoid any disruption.

Only https://api.retailexpress.com.au/ will be supported moving forward.

What happens if I don’t make this change?

Integrations using unsupported base URLs will no longer be able to connect to the Retail Express REST API. This will result in failed requests and disruption to any associated workflows.

How do I check and validate my update?

You should:

Review hardcoded base URLs, config files, and environment variables
Check any middleware, services, or scheduled jobs
Run your usual integration processes
Confirm data is syncing correctly and monitor for errors

I’m not sure how my integration is set up—what should I do?

If you’re unsure where this change needs to be made, you may wish to contact the owner or builder of the integration, or the provider you engaged during development.

If you’re unsure who that is, you may be able to review the API key naming within Retail Express Back Office under: Settings > Integrations > API Management
This may help identify the system or party responsible.

Please note, it is the responsibility of the external party managing or controlling the integration to make these changes. Retail Express is not able to make changes on your behalf.

What if I manage integrations for multiple Retail Express customers?

If you operate integrations across multiple Retail Express customers, you will need to review and update any or all integrations that use non-supported base URLs. Ensuring consistency across all implementations will help avoid disruption.

Are there any changes to the SOAP API?

No. There are no changes to our SOAP APIs.
This update only applies to the Retail Express REST API.

What if I need more time?

If you are unable, or believe you may be unable, to complete these changes within the proposed timeframe, please contact our Support team using this form or submit a ticket through the Support Case Portal

Where can I get help?

If you need assistance, please contact the Retail Express Support team via the Support Case Portal.

Why can’t Retail Express/Maropost make these changes for me?

Retail Express/Maropost can’t update the integration directly because it’s built and managed outside of Retail Express. While we can see the requests coming into our system, the actual code lives on your side (or with your developer/agency), so you’ll need to work with them to make the required changes.

How do I know what external integrations I have if I’m not sure?

Retail Express may not be able to identify all integrations on your behalf, particularly if they were built externally by your business or a third party.

You can review your API keys in Back Office > Settings > Integrations > API Management. It’s possible you have one or more API keys configured—any of these integrations may be impacted and should be reviewed. The details shown there can help indicate which systems are connected and who to contact regarding any required changes.

This update does not change REST API endpoints, request or response formats, authentication, or existing functionality. It is strictly a base URL update to ensure all REST API traffic is routed through the correct supported domain.