Amazon-Ads authentication
This page documents the authentication and configuration options for the Amazon-Ads 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 |
|---|---|---|---|
client_id | str | No | The client ID of your Amazon Ads API application |
client_secret | str | No | The client secret of your Amazon Ads API application |
refresh_token | str | Yes | The refresh token obtained from the OAuth authorization flow |
Example request:
from airbyte_agent_amazon_ads import AmazonAdsConnector
from airbyte_agent_amazon_ads.models import AmazonAdsAuthConfig
connector = AmazonAdsConnector(
auth_config=AmazonAdsAuthConfig(
client_id="<The client ID of your Amazon Ads API application>",
client_secret="<The client secret of your Amazon Ads API application>",
refresh_token="<The refresh token obtained from the OAuth authorization flow>"
)
)
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 |
|---|---|---|---|
client_id | str | No | The client ID of your Amazon Ads API application |
client_secret | str | No | The client secret of your Amazon Ads API application |
refresh_token | str | Yes | The refresh token obtained from the OAuth authorization flow |
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 '{
"customer_name": "<CUSTOMER_NAME>",
"connector_type": "Amazon-Ads",
"name": "My Amazon-Ads Connector",
"credentials": {
"client_id": "<The client ID of your Amazon Ads API application>",
"client_secret": "<The client secret of your Amazon Ads API application>",
"refresh_token": "<The refresh token obtained from the OAuth authorization flow>"
}
}'
Bring your own OAuth flow
To implement your own OAuth flow, use Airbyte's server-side OAuth API endpoints. For a complete guide, see Implement your own OAuth flow.
Step 1: Initiate the OAuth flow
Request a consent URL for your user.
| Field Name | Type | Required | Description |
|---|---|---|---|
customer_name | string | Yes | Your unique identifier for the customer |
connector_type | string | Yes | The connector type (e.g., "Amazon-Ads") |
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 '{
"customer_name": "<CUSTOMER_NAME>",
"connector_type": "Amazon-Ads",
"redirect_url": "https://yourapp.com/oauth/callback"
}'
Redirect your user to the consent_url from the response. After they authorize, they'll be redirected back to your app with a secret_id query parameter.
Step 2: Create a connector with the secret ID
| Field Name | Type | Required | Description |
|---|---|---|---|
customer_name | string | Yes | Your unique identifier for the customer |
connector_type | string | Yes | The connector type (e.g., "Amazon-Ads") |
name | string | Yes | A name for this connector instance |
server_side_oauth_secret_id | string | Yes | The secret_id from the OAuth callback |
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 '{
"customer_name": "<CUSTOMER_NAME>",
"connector_type": "Amazon-Ads",
"name": "My Amazon-Ads Connector",
"server_side_oauth_secret_id": "<secret_id_from_callback>"
}'
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_amazon_ads import AmazonAdsConnector, AirbyteAuthConfig
connector = AmazonAdsConnector(
auth_config=AirbyteAuthConfig(
customer_name="<your_customer_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
@AmazonAdsConnector.tool_utils
async def amazon_ads_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-Ads 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 | https://advertising-api.amazon.com | The Amazon Ads API endpoint URL based on region: |
- NA (North America): https://advertising-api.amazon.com
- EU (Europe): https://advertising-api-eu.amazon.com
- FE (Far East): https://advertising-api-fe.amazon.com |