ASIN Data API provides detailed product data from Amazon, including price, rank, reviews, and more, enabling real-time insights for e-commerce professionals, marketers, and data analysts.
ASIN Data API provides detailed product data from Amazon, including price, rank, reviews, and more, enabling real-time insights for e-commerce professionals, marketers, and data analysts. On Nagent, ASIN Data API is exposed as a fully-configurable ecommerce integration that any agent can call — 6 actions, and API key authentication. No code is required to wire ASIN Data API into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use ASIN Data API to automate the kinds of tasks ecommerce teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire ASIN Data API into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against ASIN Data API, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ASIN_DATA_API_CLEAR_COLLECTION_REQUESTSDelete multiple requests from a collection by their IDs using the bulk delete endpoint. Use this tool when you need to remove a selected set of request entries from an existing collection. Note: Requests can only be deleted when the collection is not running.
Input parameters
Array of request ID strings to delete. Use LIST_COLLECTION_REQUESTS to get valid request IDs for a collection.
Unique identifier of the collection to clear requests from. Use LIST_COLLECTIONS to get valid collection IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASIN_DATA_API_DELETE_DESTINATIONDelete a destination from your account. Use this when you need to remove a destination that is no longer needed.
Input parameters
The unique identifier of the destination to delete. Can be obtained from the List Destinations action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASIN_DATA_API_GET_COLLECTIONGet details of a specific collection including status and request counts. Use when you need to check collection configuration, operational status, or aggregate statistics.
Input parameters
Unique identifier of the collection to retrieve. Can be obtained from the List Collections action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASIN_DATA_API_LIST_COLLECTION_REQUESTSList all requests in a Collection (paginated). Use to retrieve and paginate through all requests added to a specific collection. Returns up to 1000 requests per page with pagination info.
Input parameters
Page number for pagination (starts at 1). Each page returns up to 1000 requests.
Unique identifier of the collection whose requests are to be listed. Can be obtained from the List Collections action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASIN_DATA_API_LIST_DESTINATIONSList all destinations configured on your account. Use to retrieve and filter destination configurations for data export. Maximum 50 destinations allowed per account. Returns 10 destinations per page with pagination support.
Input parameters
Page number for pagination (starts at 1). Each page returns up to 10 destinations.
Sort criteria for destinations.
Filter destinations by name. Only destinations matching this search term will be returned.
Sort order for destinations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASIN_DATA_API_UPDATE_DESTINATIONUpdate an existing destination's configuration. Use to modify cloud storage settings, change the destination name, or enable/disable a destination. Only include fields you want to update.
Input parameters
New name for the destination.
Whether the destination should be enabled (true) or disabled (false).
Alibaba Cloud OSS region ID.
The unique identifier of the destination to update. Can be obtained from List Destinations action.
Google Cloud Storage access key for GCS authentication.
Google Cloud Storage secret key for GCS authentication.
Alibaba Cloud OSS access key for OSS authentication.
Alibaba Cloud OSS secret key for OSS authentication.
AWS S3 bucket name for S3-type destinations.
Path prefix within the S3 bucket where files will be stored.
Google Cloud Storage bucket name for GCS-type destinations.
Path prefix within the GCS bucket.
Alibaba Cloud OSS bucket name for OSS-type destinations.
Path prefix within the OSS bucket.
AWS access key ID for S3 authentication.
Azure storage account key for Azure authentication.
Path prefix within the Azure container.
Azure storage account name for Azure-type destinations.
Azure container name where files will be stored.
AWS secret access key for S3 authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 45 agents privately built on Nagent that already use ASIN Data API.
Build on Nagent
Connect ASIN Data API to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find ASIN Data API, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, ASIN Data API is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once ASIN Data API is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop ASIN Data API steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a ASIN Data API event fires, the agent kicks off automatically.
Every ASIN Data API action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While ASIN Data API ships with 6 pre-built ecommerce actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching ASIN Data API together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build ASIN Data API-based workflows tailored to your business.