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.
Clears (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.
Tool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule.
Tool 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.
Creates 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.
Tool to delete a collection and its configuration by ID. Use when you need to remove an existing, non-running collection.
Tool to delete a destination by ID. Use when you need to remove an existing destination.
Delete 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.
Tool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API.
Tool to download all requests in a collection as JSON. Use when you need to export the entire request history for a collection.
Export 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.
Tool 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.
Tool to retrieve account usage and current platform status. Use when needing to check plan, usage, and quota details for the authenticated user.
Tool to retrieve details for a single collection by ID. Use when you need collection metadata and counts for a given collection ID.
Tool to retrieve a collection run's result set payload. Use after a collection run completes to fetch metadata and download links.
Tool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints.
Tool to list all destinations configured for the account. Use when you need to inspect or paginate through configured destinations.
Tool to list error logs from collection executions. Returns recent errors encountered during request processing with details about failed requests and their causes.
Tool 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.
Resend 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
Start 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
Tool to stop all collections. Use when you need to halt any running or queued collections after reviewing operations.
Tool 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.
Update 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.
Tool to update a destination's configuration by ID. Use after creating or retrieving a destination to modify its settings.
Tool 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.
The Countdown API integration connects your Dench AI CRM directly to Countdown API, so agents can read and act on your Countdown API data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
25 actions are available for agents to invoke on your behalf. Every call runs through Countdown API's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Countdown API and click Connect — you'll authorize access through Countdown API's own sign-in flow. No API keys or code required.
Ask an agent to use Countdown API in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Countdown API integration connects your AI CRM to Countdown API, so AI agents can work with your Countdown API data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Countdown API integration currently exposes 25 actions, including Clear Collection Requests, Create a new collection, Create Collection Request, Create Destination, Delete Collection, and Delete Destination. Agents invoke them on your behalf from chat or from automations.
No. You connect Countdown API from your Dench workspace using Countdown API's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Countdown API's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Countdown API connection from your workspace settings at any time.