Countdown API provides real-time eBay product data, including product details, customer reviews, seller feedback, and search results, enabling businesses and developers to access comprehensive eBay marketplace information.
Countdown API provides real-time eBay product data, including product details, customer reviews, seller feedback, and search results, enabling businesses and developers to access comprehensive eBay marketplace information. On Nagent, Countdown API is exposed as a fully-configurable ecommerce integration that any agent can call — 25 actions, and API key authentication. No code is required to wire Countdown API into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Countdown 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 Countdown 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 Countdown API, with input parameters and output schema. Drop these into any step of an agent built in Helix.
COUNTDOWN_API_CLEAR_ALL_REQUESTSClears (removes) all pending requests from a collection. Use this to reset a collection before adding new requests, or to cancel all queued requests. The collection must be in 'idle' status. Returns the updated collection details after clearing.
Input parameters
The unique 8-character alphanumeric ID of the collection to clear. Get this from list_collections or create_collection actions.
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
COUNTDOWN_API_COLLECTIONS_CREATE_COLLECTIONTool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule.
Input parameters
Collection name
Enable or disable scheduled runs
Collection priority
Lock collection to a specific request type; cannot be changed after creation. Use 'mixed' to allow any request type.
Run schedule type
Hours (0-23) to run
Destination IDs to upload results to
Minute interval when schedule_type='minutes'. Determines how frequently the collection runs within each hour.
Email to send notifications to
Output/upload results as CSV
Output/upload results as JSON
Webhook URL to POST when results are available
Days of week (0=Sun ... 6=Sat) for weekly schedules
Days of month (1-31) for monthly schedules
Comma-separated field list when CSV enabled
Output/upload results as JSON Lines
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
COUNTDOWN_API_COLLECTIONS_GET_COLLECTIONTool to retrieve details for a single collection by ID. Use when you need collection metadata and counts for a given collection ID.
Input parameters
Unique 8-character hexadecimal collection identifier (e.g., '51AE51AB')
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
COUNTDOWN_API_COLLECTIONS_LIST_COLLECTIONSTool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints.
Input parameters
Page number to retrieve (default is 1).
Filter by status. Default is 'all'.
Field to sort by (default 'name').
Results per page (default 25, maximum 1000).
Limit results to collections whose name contains this term.
How to match the search_term. One of: contains, starts_with, ends_with, exact.
Only collections created after this ISO UTC timestamp (ISO 8601).
Only collections created before this ISO UTC timestamp (ISO 8601).
Only collections with the specified destination id.
Only collections with last run after this ISO UTC timestamp (ISO 8601).
Sort direction (default 'ascending').
Only collections with last run before this ISO UTC timestamp (ISO 8601).
Only return collections that have result sets available.
Only return collections with no result sets available.
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
COUNTDOWN_API_COLLECTIONS_START_COLLECTIONStart processing a collection's queued requests on the Countdown API. Use this tool to manually trigger a collection to begin executing its requests. The collection must have at least one request added to it before it can be started. You need sufficient API credits to run all requests in the collection. Prerequisites: - Collection must exist (use List Collections or Create Collection first) - Collection must have at least one request added - Sufficient API credits available for the number of requests - Collection must not already be running
Input parameters
The unique identifier of the collection to start. Must be a valid collection ID obtained from creating or listing collections.
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
COUNTDOWN_API_COLLECTIONS_UPDATE_COLLECTIONUpdate an existing collection's settings. Use this to modify collection properties like name, schedule, priority, notification settings, or enabled status. The collection_id must be obtained from list_collections or create_collection. Only specified fields are updated; omitted fields retain their current values.
Input parameters
New name for the collection
Enable or disable scheduled runs
Collection priority
ID of the collection to update (obtained from list_collections or create_collection)
Lock collection to a specific request type; cannot be changed after creation
Run schedule type
Hours (0-23) to run
Destination IDs to upload results to
Minute interval when schedule_type='minutes'
Email to send notifications to
Output/upload results as CSV
Output/upload results as JSON
Webhook URL to POST when results are available
Days of week (0=Sun...6=Sat) for weekly schedules
Days of month (1-31) for monthly schedules
Comma-separated field list when CSV enabled
Output/upload results as JSON Lines
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
COUNTDOWN_API_CORE_API_SEND_REQUESTTool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API.
Input parameters
The type of request. Must be "autocomplete" to retrieve autocomplete suggestions.
eBay domain to retrieve autocomplete suggestions from. Supported domains include ebay.com, ebay.co.uk, ebay.de, ebay.fr, ebay.com.au, ebay.ca, etc.
The search term to get autocomplete suggestions for.
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
COUNTDOWN_API_CREATE_COLLECTION_REQUESTTool to create new requests within a collection for bulk eBay data retrieval. Use when you need to add search, product, reviews, or other eBay data queries to a collection that will be executed on schedule. Collections must be in 'idle' status to accept new requests.
Input parameters
Array of request objects to add to the collection. Maximum 1,000 requests per call. Collections support up to 15,000 total requests
The 8-character alphanumeric ID of the collection to add requests to. Collection must be in 'idle' status. Use 'List Collections' to find available 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
COUNTDOWN_API_CREATE_DESTINATIONCreates a cloud storage destination where batch result sets will be automatically uploaded. Supports Amazon S3, S3-compatible services (MinIO, DigitalOcean Spaces), Google Cloud Storage, Microsoft Azure Blob Storage, and Alibaba Cloud OSS. When enabled=true, the API validates credentials by uploading and deleting a test file. Set enabled=false to create the destination without credential validation.
Input parameters
A descriptive name to identify this destination.
Cloud storage provider type: 's3' for Amazon S3, 's3compatible' for S3-compatible services (MinIO, DigitalOcean Spaces), 'gcs' for Google Cloud Storage, 'azure' for Microsoft Azure Blob Storage, 'oss' for Alibaba Cloud OSS.
Whether automatic uploads to this destination are active. Set to false to create destination without validating credentials.
AWS region or S3-compatible service region (e.g., 'us-east-1'). Optional for S3-compatible services.
S3-compatible service endpoint URL (e.g., 'https://minio.example.com:9000'). Required when type is 's3compatible'.
Alibaba Cloud OSS region ID (e.g., 'oss-cn-hangzhou', 'oss-us-east-1'). Required when type is 'oss'.
Google Cloud Storage interoperable storage access key (HMAC key). Required when type is 'gcs'.
Google Cloud Storage interoperable storage secret key (HMAC secret). Required when type is 'gcs'.
Alibaba Cloud RAM user access key. Required when type is 'oss'.
Alibaba Cloud RAM user secret key. Required when type is 'oss'.
Name of the S3 bucket to upload files to. Required when type is 's3' or 's3compatible'.
Optional path prefix for uploaded files. Supports replacement tokens: %BATCH_ID%, %BATCH_NAME%, %RESULT_SET_ID%, %DATE%.
Name of the GCS bucket to upload files to. Required when type is 'gcs'.
Optional path prefix for uploaded files. Supports replacement tokens: %BATCH_ID%, %BATCH_NAME%, %RESULT_SET_ID%, %DATE%.
Name of the Alibaba Cloud OSS bucket to upload files to. Required when type is 'oss'.
Optional path prefix for uploaded files. Supports replacement tokens: %BATCH_ID%, %BATCH_NAME%, %RESULT_SET_ID%, %DATE%.
AWS IAM access key ID. Required when type is 's3' or 's3compatible'.
Azure Storage account access key. Required when type is 'azure'.
Optional path prefix for uploaded files. Supports replacement tokens: %BATCH_ID%, %BATCH_NAME%, %RESULT_SET_ID%, %DATE%.
Azure Storage account name. Required when type is 'azure'.
Name of the Azure Blob container to upload files to. Required when type is 'azure'.
AWS IAM secret access key. Required when type is 's3' or 's3compatible'.
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
COUNTDOWN_API_DELETE_COLLECTIONTool to delete a collection and its configuration by ID. Use when you need to remove an existing, non-running collection.
Input parameters
ID of the collection to delete
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
COUNTDOWN_API_DELETE_DESTINATIONTool to delete a destination by ID. Use when you need to remove an existing destination.
Input parameters
ID of the destination to delete
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
COUNTDOWN_API_DELETE_SINGLE_REQUESTDelete a specific request from a Countdown API collection by its ID. Use this to remove individual requests that are no longer needed. The collection must not be running when deleting requests.
Input parameters
The unique identifier of the request to delete from the collection. Obtain this from the 'List Requests Paged' action.
The unique identifier of the collection containing the request to delete. Obtain this from the 'List Collections' or 'Create Collection' 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
COUNTDOWN_API_DESTINATIONS_LIST_DESTINATIONSTool to list all destinations configured for the account. Use when you need to inspect or paginate through configured destinations.
Input parameters
Page number to return; 10 destinations per page
Sort field; valid values: 'type' or 'name'; use with sort_direction
Filter results to destinations whose names contain this term
Sort direction; valid values: ascending or descending; use with sort_by
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
COUNTDOWN_API_FIND_COLLECTION_REQUESTSTool to find requests in a collection by custom_id or search query. Use when you need to search for specific requests within a collection using either an exact custom_id match or a text search query.
Input parameters
Search query to find requests. Searches across request fields and custom_id. Mutually exclusive with 'custom_id' parameter - provide either custom_id or q, not both.
1-indexed page number of matching results to retrieve. Each page returns up to 1000 requests. Start with page 1 and check requests_page_count in the response for total pages.
Find requests with this exact custom_id. Mutually exclusive with 'q' parameter - provide either custom_id or q, not both.
The 8-character alphanumeric ID of the collection to search. Use 'List Collections' to find available 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
COUNTDOWN_API_GET_ACCOUNTTool to retrieve account usage and current platform status. Use when needing to check plan, usage, and quota details for the authenticated user.
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
COUNTDOWN_API_LIST_ERROR_LOGSTool to list error logs from collection executions. Returns recent errors encountered during request processing with details about failed requests and their causes.
Input parameters
Page number to retrieve (1-indexed). Use page_count_total from the response to determine the total number of pages available.
Number of error log entries to return per page (default 25, maximum 1000).
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
COUNTDOWN_API_REQUESTS_EXPORT_CSVExport all requests from a collection as downloadable CSV files. Returns URLs to CSV files containing the request data. Use this tool when you need to bulk export or download collection request data in CSV format. The response includes paginated download links if the collection has many requests. Collections with no requests will return an empty pages array.
Input parameters
The ID of the collection whose requests you want to export as CSV.
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
COUNTDOWN_API_REQUESTS_EXPORT_JSONTool to download all requests in a collection as JSON. Use when you need to export the entire request history for a collection.
Input parameters
ID of the collection to export requests from
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
COUNTDOWN_API_REQUESTS_UPDATE_SINGLE_REQUESTTool to modify parameters of an existing request in a collection. Use when the collection is not running and you need to update eBay Product Data API parameters.
Input parameters
Complete request parameters conforming to the eBay Product Data API schema. Must include required fields: 'type' (product/search/reviews/seller_profile/seller_feedback/category/autocomplete/deals), 'ebay_domain' (e.g., ebay.com, ebay.co.uk, ebay.de). Type-specific parameters: for 'product' use 'epid'; for 'search' use 'search_term'; etc.
ID of the specific request to update within the collection.
ID of the collection containing the request to update.
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
COUNTDOWN_API_RESULTS_GET_RESULT_SETTool to retrieve a collection run's result set payload. Use after a collection run completes to fetch metadata and download links.
Input parameters
Unique identifier of the collection containing the result set. Obtain from List Collections or Create Collection actions.
Numeric ID of the result set to retrieve. Obtain from List Result Sets action or from collection's next_result_set_id minus 1 after a run completes.
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
COUNTDOWN_API_RESULTS_LIST_RESULT_SETSTool to list result sets produced by a collection. Use when you need to retrieve all summary status of result sets generated by a collection within the 14-day retention window.
Input parameters
Unique identifier of the collection to list result sets for. Obtain this from the List Collections action or from a previously created collection.
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
COUNTDOWN_API_RESULTS_RESEND_RESULT_SET_WEBHOOKResend the webhook notification for a collection's result set. Use this tool to retry webhook delivery when the original webhook POST failed or timed out. The collection must have a notification_webhook URL configured (either on the collection itself or on the account profile). Result sets are only available for 14 days after creation. Prerequisites: - Collection must exist with a valid notification_webhook URL configured - Result set must exist and not be expired (14-day retention) - Use List Result Sets to find valid result_set_id values
Input parameters
The unique 8-character alphanumeric identifier of the collection containing the result set. Obtain this from List Collections or Create Collection actions.
The numeric ID of the result set within the collection (must be >= 1). Each time a collection runs, it generates a new result set with an incrementing ID. Obtain valid IDs from List Result Sets 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
COUNTDOWN_API_STOP_ALL_COLLECTIONSTool to stop all collections. Use when you need to halt any running or queued collections after reviewing operations.
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
COUNTDOWN_API_STOP_COLLECTIONTool to stop (pause) a single collection’s processing by ID. Use when you need to halt a running or queued collection after confirming the target collection ID.
Input parameters
The unique identifier of the collection to stop. The collection must be in 'running' or 'queued' status.
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
COUNTDOWN_API_UPDATE_DESTINATIONTool to update a destination's configuration by ID. Use after creating or retrieving a destination to modify its settings.
Input parameters
Destination name
Destination type
Whether uploads are active for this destination
S3 region (optional when type is s3compatible)
S3 endpoint URL (required when type is s3compatible)
OSS region ID (required when type is oss)
Unique identifier of the destination to update. Obtain from list_destinations or create_destination.
GCS access key (required when type is gcs)
GCS secret key (required when type is gcs)
OSS access key (required when type is oss)
OSS secret key (required when type is oss)
S3 bucket name (required when type is s3 or s3compatible)
S3 path prefix (optional); supports tokens %collection_id%, %collection_name%, %result_set_id%, %date%
GCS bucket name (required when type is gcs)
GCS path prefix (optional); supports tokens %collection_id%, %collection_name%, %result_set_id%, %date%
OSS bucket name (required when type is oss)
OSS path prefix (optional); supports tokens %collection_id%, %collection_name%, %result_set_id%, %date%
S3 access key id (required when type is s3 or s3compatible)
Azure account key (required when type is azure)
Azure path prefix (optional); supports tokens %collection_id%, %collection_name%, %result_set_id%, %date%
Azure account name (required when type is azure)
Azure container name (required when type is azure)
S3 secret access key (required when type is s3 or s3compatible)
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 46 agents privately built on Nagent that already use Countdown API.
Build on Nagent
Connect Countdown 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 Countdown API, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Countdown API is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Countdown API is connected, you configure its 25 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Countdown 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 Countdown API event fires, the agent kicks off automatically.
Every Countdown 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 Countdown API ships with 25 pre-built ecommerce actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Countdown API together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Countdown API-based workflows tailored to your business.