Amazon-Seller-Partner authentication
This page documents the authentication and configuration options for the Amazon-Seller-Partner agent connector.
Authentication
Open source execution
In open source mode, you provide API credentials directly to the connector.
OAuth
credentials fields you need:
| Field Name | Type | Required | Description |
|---|---|---|---|
lwa_app_id | str | Yes | Your Login with Amazon Client ID. |
lwa_client_secret | str | Yes | Your Login with Amazon Client Secret. |
refresh_token | str | Yes | The Refresh Token obtained via the OAuth authorization flow. |
access_token | str | No | Access token (optional if refresh_token is provided). |
Example request:
from airbyte_agent_sdk.connectors.amazon_seller_partner import AmazonSellerPartnerConnector
from airbyte_agent_sdk.connectors.amazon_seller_partner.models import AmazonSellerPartnerAuthConfig
connector = AmazonSellerPartnerConnector(
auth_config=AmazonSellerPartnerAuthConfig(
lwa_app_id="<Your Login with Amazon Client ID.>",
lwa_client_secret="<Your Login with Amazon Client Secret.>",
refresh_token="<The Refresh Token obtained via the OAuth authorization flow.>",
access_token="<Access token (optional if refresh_token is provided).>"
)
)
Token
This authentication method isn't available for this connector.
Hosted execution
In hosted mode, you first create a connector via the Airbyte API (providing your OAuth or Token credentials), then execute operations using either the Python SDK or API. If you need a step-by-step guide, see the hosted execution tutorial.
OAuth
Create a connector with OAuth credentials.
credentials fields you need:
| Field Name | Type | Required | Description |
|---|---|---|---|
lwa_app_id | str | Yes | Your Login with Amazon Client ID. |
lwa_client_secret | str | Yes | Your Login with Amazon Client Secret. |
refresh_token | str | Yes | The Refresh Token obtained via the OAuth authorization flow. |
access_token | str | No | Access token (optional if refresh_token is provided). |
replication_config fields you need:
| Field Name | Type | Required | Description |
|---|---|---|---|
replication_start_date | str (date-time) | Yes | UTC date and time in ISO 8601 format (e.g. 2024-01-01T00:00:00Z). Any data before this date will not be replicated. This sets the earliest date for order creation and financial event queries. For most sellers, a start date of 1-2 years ago is a good default. Must include the time component and Z timezone suffix. |
Example request:
curl -X POST "https://api.airbyte.ai/api/v1/integrations/connectors" \
-H "Authorization: Bearer <YOUR_BEARER_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"workspace_name": "<WORKSPACE_NAME>",
"connector_type": "Amazon-Seller-Partner",
"name": "My Amazon-Seller-Partner Connector",
"credentials": {
"lwa_app_id": "<Your Login with Amazon Client ID.>",
"lwa_client_secret": "<Your Login with Amazon Client Secret.>",
"refresh_token": "<The Refresh Token obtained via the OAuth authorization flow.>",
"access_token": "<Access token (optional if refresh_token is provided).>"
},
"replication_config": {
"replication_start_date": "<UTC date and time in ISO 8601 format (e.g. 2024-01-01T00:00:00Z). Any data before this date will not be replicated. This sets the earliest date for order creation and financial event queries. For most sellers, a start date of 1-2 years ago is a good default. Must include the time component and Z timezone suffix.>"
}
}'
Bring your own OAuth flow
To implement your own OAuth flow, use Airbyte's server-side OAuth API endpoints. For a complete guide, see Build your own OAuth flow.
Step 1: Initiate the OAuth flow
Request a consent URL for your user.
| Field Name | Type | Required | Description |
|---|---|---|---|
workspace_name | string | Yes | Your unique identifier for the workspace |
connector_type | string | Yes | The connector type (e.g., "Amazon-Seller-Partner") |
redirect_url | string | Yes | URL to redirect to after OAuth authorization |
Example request:
curl -X POST "https://api.airbyte.ai/api/v1/integrations/connectors/oauth/initiate" \
-H "Authorization: Bearer <YOUR_BEARER_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"workspace_name": "<WORKSPACE_NAME>",
"connector_type": "Amazon-Seller-Partner",
"redirect_url": "https://yourapp.com/oauth/callback"
}'
Redirect your user to the consent_url from the response.
Step 2: Handle the callback
After the user authorizes access, Airbyte automatically creates the connector and redirects them to your redirect_url with a connector_id query parameter. You don't need to make a separate API call to create the connector.
https://yourapp.com/oauth/callback?connector_id=<connector_id>
Extract the connector_id from the callback URL and store it for future operations. For error handling and a complete implementation example, see Build your own OAuth flow.
Token
This authentication method isn't available for this connector.
Execution
After creating the connector, execute operations using either the Python SDK or API.
If your Airbyte client can access multiple organizations, include organization_id in AirbyteAuthConfig and X-Organization-Id in raw API calls.
Python SDK
from airbyte_agent_sdk.connectors.amazon_seller_partner import AmazonSellerPartnerConnector, AirbyteAuthConfig
connector = AmazonSellerPartnerConnector(
auth_config=AirbyteAuthConfig(
workspace_name="<your_workspace_name>",
organization_id="<your_organization_id>", # Optional for multi-org clients
airbyte_client_id="<your-client-id>",
airbyte_client_secret="<your-client-secret>"
)
)
@agent.tool_plain # assumes you're using Pydantic AI
@AmazonSellerPartnerConnector.tool_utils
async def amazon_seller_partner_execute(entity: str, action: str, params: dict | None = None):
return await connector.execute(entity, action, params or {})
API
curl -X POST 'https://api.airbyte.ai/api/v1/integrations/connectors/<connector_id>/execute' \
-H 'Authorization: Bearer <YOUR_BEARER_TOKEN>' \
-H 'X-Organization-Id: <YOUR_ORGANIZATION_ID>' \
-H 'Content-Type: application/json' \
-d '{"entity": "<entity>", "action": "<action>", "params": {}}'
Configuration
The Amazon-Seller-Partner connector requires the following configuration variables. These variables are used to construct the base API URL. Pass them via the config parameter when initializing the connector.
| Variable | Type | Required | Default | Description |
|---|---|---|---|---|
region | string | Yes | na | The seller's marketplace region. This determines both the API endpoint and the marketplace ID used for queries. Select the country code where you sell: |
| North America (NA endpoint): US (Amazon.com), CA (Amazon.ca), MX (Amazon.com.mx), BR (Amazon.com.br) | ||||
| Europe (EU endpoint): DE (Amazon.de), FR (Amazon.fr), IT (Amazon.it), ES (Amazon.es), UK/GB (Amazon.co.uk), NL (Amazon.nl), SE (Amazon.se), PL (Amazon.pl), BE (Amazon.com.be), TR (Amazon.com.tr), EG (Amazon.eg), SA (Amazon.sa), AE (Amazon.ae), IN (Amazon.in), ZA (Amazon.co.za) | ||||
| Far East (FE endpoint): JP (Amazon.co.jp), AU (Amazon.com.au), SG (Amazon.sg) | ||||
| The region is automatically mapped to the correct API endpoint (na/eu/fe) and marketplace ID. You only need to specify your country code. |