ABA Keyword Trends
Use the ABA Keyword Trends API for Amazon keyword research. Review request parameters, response fields, and runnable examples.
/v1 /amazon /keywords /aba /trendsAPI data samples
Inspect the request body and complete response shape used by this endpoint.
{
"marketplace": "US",
"keyword": "test",
"timeGranularity": "M"
}{
"request_id": "8fb43e59-4ff9-4dc8-a4b7-2ed164e45ab8",
"data": [
{
"date": 1709222400000,
"rank": 302628,
"searches": 5260,
"label": "202403"
},
{
"date": 1711900800000,
"rank": 292310,
"searches": 5475,
"label": "202404"
}
]
}Availability: Available
This endpoint is active in the v1 gateway, OpenAPI, and subscription catalog. A successful call consumes 1 billing unit.
POST /v1/amazon/keywords/aba/trends
The request and response fields below match the current public contract.
Quick call
First create an API key, then store it in a server-side environment variable:
export ECOMMERCE_DATA_API_KEY="your_api_key"curl --request POST \
--url https://ecommercedataapi.com/v1/amazon/keywords/aba/trends \
--header "Content-Type: application/json" \
--header "X-API-Key: ${ECOMMERCE_DATA_API_KEY}" \
--data '{
"marketplace": "US",
"keyword": "test",
"timeGranularity": "M"
}'Integrate with an AI CLI
Copy for your AI CLI
Paste this task into Codex, Claude Code, Gemini CLI, or another coding agent.
Integrate the "ABA Keyword Trends" endpoint from Ecommerce Data API into the current repository. Make the changes directly instead of only returning sample code.
API documentation: https://ecommercedataapi.com/en/docs/amazon/keywords/aba-trends
Endpoint: POST https://ecommercedataapi.com/v1/amazon/keywords/aba/trends
API key environment variable: ECOMMERCE_DATA_API_KEY
Example request:
{
"marketplace": "US",
"keyword": "test",
"timeGranularity": "M"
}
Requirements:
1. Read the API documentation first, then inspect the repository's language, framework, HTTP client, directory structure, and environment-variable conventions.
2. Reuse the existing API client and error-handling patterns. If none exist, add the smallest reusable Ecommerce Data API client and an endpoint-specific wrapper.
3. Read the key from the server-side ECOMMERCE_DATA_API_KEY environment variable and send Content-Type: application/json plus the X-API-Key header. Never write a real key into source code, browser code, logs, test snapshots, or Git.
4. If the environment variable is missing, tell me to configure ECOMMERCE_DATA_API_KEY myself. Do not request, print, or invent the real key, and continue implementing code and tests that do not require a live request.
5. Implement request and response types from the documentation. Handle non-2xx responses, request_id, error.code, error.message, and 429 rate limits.
6. Add a minimal usage example or test that follows the repository's conventions. Run one minimal live request only when the key is already configured and external requests are allowed; otherwise use mocks or static validation.
7. Run the relevant formatter, type checker, and tests. Report changed files, usage, verification results, and any environment variable I still need to configure.Open this request in Postman
Download the preconfigured collection for this endpoint, then import it into Postman.
Node.js example
const response = await fetch(
'https://ecommercedataapi.com/v1/amazon/keywords/aba/trends',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-API-Key': process.env.ECOMMERCE_DATA_API_KEY,
},
body: JSON.stringify({
marketplace: 'US',
keyword: 'test',
timeGranularity: 'M',
}),
}
);
const result = await response.json();
if (!response.ok) {
throw new Error(`${result.error?.code}: ${result.error?.message}`);
}
console.log(result.data);Python example
import os
import requests
response = requests.post(
"https://ecommercedataapi.com/v1/amazon/keywords/aba/trends",
headers={
"Content-Type": "application/json",
"X-API-Key": os.environ["ECOMMERCE_DATA_API_KEY"],
},
json={
"marketplace": "US",
"keyword": "test",
"timeGranularity": "M",
},
timeout=30,
)
response.raise_for_status()
print(response.json()["data"])Request body
Send the fields below directly in the JSON body without an extra wrapper. Undefined fields are rejected.
| Field | Type | Required | Description | Example |
|---|---|---|---|---|
marketplace | String | Yes | Amazon marketplace code. Supported values are listed in the schema. | US |
keyword | String | Yes | Keyword used by the query. | wireless charger |
timeGranularity | String | No | Time granularity. Date or timestamp value. | W:周,M:月 |
returnFields | String | No | Optional comma-separated response fields. Omit it to receive the standard payload. | date,rank,searches |
Response structure
| Field | Type | Description |
|---|---|---|
request_id | String | Unique identifier for this request. |
data | Array | Endpoint business data. |
The fields below are inside data. For array endpoints they describe one array item; for paginated endpoints they describe one record in items[].
Response fields
| Field | Type | Description | Example |
|---|---|---|---|
date | Integer | Date. Date or timestamp value. | - |
rank | String | Rank. | - |
searches | String | Searches. | - |
label | Integer | Label. Date or timestamp value. | - |
Response example
{
"request_id": "8fb43e59-4ff9-4dc8-a4b7-2ed164e45ab8",
"data": [
{
"date": 1709222400000,
"rank": 302628,
"searches": 5260,
"label": "202403"
},
{
"date": 1711900800000,
"rank": 292310,
"searches": 5475,
"label": "202404"
}
]
}See Errors and rate limits for error payloads, request tracing, and rate-limit headers.