Countdown API

These are the Countdown API actions available to the apps you build with Snow. Connecting an account does not make Snow run these on its own.

• Clear Collection Requests

  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.

• Create Collection Request

  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.

• Create Destination

  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.

• Delete Collection

  Tool to delete a collection and its configuration by ID. Use when you need to remove an existing, non-running collection.

• Delete Destination

  Tool to delete a destination by ID. Use when you need to remove an existing destination.

• Delete Single Request

  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.

• eBay Autocomplete

  Tool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API.

• Export Requests as JSON

  Tool to download all requests in a collection as JSON. Use when you need to export the entire request history for a collection.

• Export Requests CSV

  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.

• Find Collection Requests

  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.

• Get Account Information

  Tool to retrieve account usage and current platform status. Use when needing to check plan, usage, and quota details for the authenticated user.

• Get Collection

  Tool to retrieve details for a single collection by ID. Use when you need collection metadata and counts for a given collection ID.

• Get Result Set

  Tool to retrieve a collection run's result set payload. Use after a collection run completes to fetch metadata and download links.

• List Collections

  Tool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints.

• List Destinations

  Tool to list all destinations configured for the account. Use when you need to inspect or paginate through configured destinations.

• List Error Logs

  Tool to list error logs from collection executions. Returns recent errors encountered during request processing with details about failed requests and their causes.

• List Result Sets

  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 Result Set Webhook

  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 Collection

  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

• Stop All Collections

  Tool to stop all collections. Use when you need to halt any running or queued collections after reviewing operations.

• Stop Collection

  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

  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.

• Update Destination

  Tool to update a destination's configuration by ID. Use after creating or retrieving a destination to modify its settings.

• Update Single Request

  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.

• Create a new collection

  Tool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule.