<@U04S8PLJWMT> Im having troubles setting the amaz...
# ask-ai
m
@kapa.ai Im having troubles setting the amazon seller partner connector, Im getting this error. 'Encountered an error while checking availability of stream Orders. Error: 400 Client Error: Bad Request for url: https://api.amazon.com/auth/o2/token', how can I solve this?
k
That specific 400 error comes from Amazon’s OAuth token endpoint, so it means Amazon is rejecting the credentials/parameters Airbyte is using to get or refresh the LWA token. From the docs and issues you shared, these are the concrete things to check: 1. Connector type and required fields - In Airbyte Cloud, you should just click Authenticate your account and grant access via Amazon’s UI; you don’t manually enter LWA credentials. [[Amazon Seller docs](https://docs.airbyte.com/integrations/sources/amazon-seller-partner#step-2-set-up-the-source-connector-in-airbyte)] - In Airbyte Open Source, you must provide: -
LWA Client Id
-
LWA Client Secret
-
Refresh Token
[[Amazon Seller docs](https://docs.airbyte.com/integrations/sources/amazon-seller-partner)] - Make sure you are using the correct mode (Cloud vs OSS) and filling the fields that apply. 2. Verify your LWA application and refresh token For OSS, the docs explicitly require a registered, published SP-API application and a refresh token generated from it. [[Amazon Seller OSS setup](https://docs.airbyte.com/integrations/sources/amazon-seller-partner)] - Confirm your SP-API app is published (not a draft). - Regenerate the refresh token via Amazon’s self-authorization flow and paste it again into Airbyte. [[Amazon Seller OSS setup](https://docs.airbyte.com/integrations/sources/amazon-seller-partner#step-2-set-up-the-source-connector-in-airbyte)] - Double‑check for: - Any typos or extra spaces in
client_id
,
client_secret
, or
refresh_token
. - Using credentials from the right region/account. Very similar 400 errors are being reported in open issues for this connector when the OAuth call to
<https://api.amazon.com/auth/o2/token>
fails. [[Issue 57754](https://github.com/airbytehq/airbyte/issues/57754); [Issue 58081](https://github.com/airbytehq/airbyte/issues/58081)] 3. Check date fields format The connector expects
Start Date
and
End Date
in
YYYY-MM-DD
format (no time /
T00:00:00Z
). [[Amazon Seller docs](https://docs.airbyte.com/integrations/sources/amazon-seller-partner#step-2-set-up-the-source-connector-in-airbyte)] - If you entered a full ISO timestamp (e.g.
2023-04-17T00:00:00Z
), change it to
2023-04-17
. - In one forum thread, a 400 error was fixed by simply removing the End Date parameter. [[Forum ISO-8601 error](https://discuss.airbyte.io/t/2436)] 4. Re-run the check after adjusting config After: - Verifying LWA app + permissions, - Regenerating and pasting a fresh refresh token (OSS), - Correcting/removing Start/End Date, save the source and run “Check connection” again. 5. If it still fails - This exact 400 OAuth error is currently tracked as an open connector issue. [[Issue 57754](https://github.com/airbytehq/airbyte/issues/57754); [Issue 58081](https://github.com/airbytehq/airbyte/issues/58081)] - If your credentials work in Postman / curl but fail in Airbyte, you’re likely hitting that same connector bug; in that case, you may need to: - Comment on the GitHub issue with your Airbyte version, connector version, and a redacted config snippet, or - Open a new issue referencing those tickets. If you share whether you’re on Cloud or OSS, your connector version, and how you filled the Amazon Seller Partner form (redacted), I can help pinpoint which of these is most likely affecting you.