Has anyone successfully migrated to the new API version for Amazon Selling Partner? I was testing it today and after much troubleshooting with assistance from Ora and ChatGPT I'm not having any luck. It's either returning no results or I'm getting this error:
{
"code": "not_supported",
"message": "The flag "useMWSDataFormat" is not yet supported for the endpoint: "".",
"occurredAt": 1778539817059,
"resolved": false,
"source": "resource"
}
URI - https://sellingpartnerapi-na.amazon.com/orders/2026-01-01/orders?marketplaceIds=**********&createdAfter=2026-05-01T00:00:00Z&maxResultsPerPage=100
Paging - I updated it according to documentation but that shouldn't affect the preview
Path to records - /orders (returns error) orders (returns nothing)
Connection:
I'd appreciate any assistance here. Thanks!
Could this be the issue? When I delete the mwsAuthToken, it authenticates but automatically adds it back. Seems like it's on the Celigo side of things. Not pointing fingers 
Hi Chris,
I tried making the same API call on my end and didn’t run into issues with the response, so the endpoint itself seems to be working as expected.
Regarding the mwsAuthToken object, even though it appears to get added back into the connection, it isn’t actually referenced or used in how the Amazon SP connection operates. So it’s unlikely to be the root cause of the error you’re seeing.
Given that, this might be something specific to how the connection is configured in your flow. I’d recommend raising a ticket with Celigo support so we can take a closer look at your setup and help pinpoint what’s going wrong.
Thank you
Hi Chris, I've raised a support ticket on your behalf, so someone from the support team should reach out to you, and take a look at this.
Thank you both for your help!
Was this issue resolved by Celigo Support? What is the resolution for connection working some times and then giving some time in same day as token expired?
We are facing same issue.
Hi @Anuradha_Mohril 
Our team suggested creating a new connection and a new export for Amazon SP API using the new API documentation, but we didn't hear back if this solution worked.
Are you getting the same error? If not, can you please share more details about the issue you're encountering? Thanks!
Thanks for reply !! We are getting this error , in a day it works once and then failed , ours is scheduled flow, because of this error , we miss some back of transactions in between and we cannot every time refresh token
{ "errors": [ { "code": "Unauthorized", "message": "Access to requested resource is denied.", "details": "The access token you provided has expired." } ] }
Hi @Anuradha_Mohril
Thank you for sharing the error.
The Unauthorized error indicates that the access token used for the request has expired. Normally, the Amazon SP-API connection should automatically obtain a new access token using the stored refresh token, so you should not need to manually refresh it for scheduled flows.
As a first step, I recommend reauthorizing the Amazon connection to ensure the refresh token is still valid. If the issue persists after reauthorization, check whether the failures are isolated to the 2026-01-01 Orders API endpoint or if they also occur with other SP-API endpoints using the same connection. This will help determine whether the issue is related to the connection's authentication or specific to the API request.
It would also be helpful to note whether you're using the standard Amazon SP-API connector or a custom HTTP export, as well as whether this behavior started after migrating to the new API version.
Hope this helps.
Hi @ravencorrales ,
Me and Anuradha working on this,
Our Amazon Seller Central SP-API connection remains Online and passes connection testing, but scheduled flows (Order Export Tile) repeatedly fail with HTTP 401 after the LWA access token expires.
Connection
Standard Amazon SP-API
SP-API region: North America
Affected resource
Error response
{ "errors": [ { "code": "Unauthorized", "message": "Access to requested resource is denied.", "details": "The access token you provided has expired." } ] }
HTTP status: 401
Example recent error ID: 4457220297
Example timestamp: August 4, 2026 at 2:05:48 AM Eastern
Original error ID: 4374927660
Observed behavior
The connection is shown as Online.
Bulk operations and occasional scheduled runs succeed.
Most scheduled runs later fail when the short-lived access token expires.
We reauthorized and tested the connection, but the failures continued.
At least 50 repeated 401 expired-token errors occurred between July 30 and August 4, 2026, often approximately every two hours.
Configuration finding
The connection configuration appears to recognize only HTTP 403 under connection.http.auth.failures. Amazon returns HTTP 401 when the LWA access token expires. This may prevent Celigo from recognizing the response as an authentication failure and automatically refreshing the token and retrying the request.
We want to understand solution for this as this is in production and has impact on business. Also, it was working fine before for scheduled flows as well.
Hi @Hitesh_Joshi
We'll need to investigate this further. I'm creating a support ticket on your behalf so our team can look into this on a deeper level.
Hi Meng: Ticket # **285206.
**
We have a solution suggested by support, but after trying that we didn't have the success.
As part of the troubleshooting, we tested the suggested approach together with the customer and observed the following behavior:
- We created a new Amazon Seller Central connection using the Standard Connector.
- We selected HTTP under the Simple authentication option.
- In the Auth tab, under Non-Standard API Responses, the response code 403 was selected by default.
- We added 401 as an additional response code and saved and authorized the connection.
- Although the connection successfully came online, when we reopened/checked the connection, 401 was not retained and the configuration had reverted to 403.
We also tested replacing 403 with 401, but the connection continues to default back to 403.
This is a critical concern because the Amazon SP-API access token is returning 401 Unauthorized when the token expires, and we need the connection to handle this response appropriately and reliably. The current behavior does not provide a robust solution for handling token expiration.
We request that the Celigo Support/Engineering team investigate this behavior and provide a permanent and robust solution in the Standard Connector.
Please let us know the recommendation.
Hi @Hitesh_Joshi
I've raised this with the support team, and someone should reach out via the follow-up ticket.
