Sanaf AI
Start free
Ecommerce

Countdown API, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Countdown API account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Ecommerce
  • Connects with a key
  • 23 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Countdown API is

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.

You paste in a key from your own Countdown API account. It is kept encrypted, and you can withdraw it from inside Countdown API whenever you like.

How a run works

One message in, the work done in Countdown API.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Countdown API. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Countdown API account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

23 tools it already has

What it can do in Countdown API

These are the ready-made tools your AI employee already has in Countdown API. It is not limited to them, but it never has to be taught these.

  • Clear Collection RequestsTool to clear all requests from a specified collection. Use when you need to remove all queued requests for an idle collection.
  • Create a new collectionTool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule.
  • Create DestinationTool to create a destination. Use when you need to set up a new destination for results or notifications.
  • Delete CollectionTool to delete a collection and its configuration by ID. Use when you need to remove an existing, non-running collection.
  • Delete DestinationTool to delete a destination by ID. Use when you need to remove an existing destination.
  • Delete Single RequestTool to remove a specific request from a collection. Use when you need to delete one request by ID.
  • eBay AutocompleteTool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API.
  • Export Requests as JSONTool to download all requests in a collection as JSON. Use when you need to export the entire request history for a collection.
  • Export Requests CSVTool to export all requests in a collection as CSV download links. Use when you need per-page CSV URLs for a given collection.
  • Get Account InformationTool to retrieve account usage and current platform status. Use when needing to check plan, usage, and quota details for the authenticated user.
  • Get CollectionTool to retrieve details for a single collection by ID. Use when you need collection metadata and counts for a given collection ID.
  • Get Result SetTool to retrieve a collection run's result set payload. Use after a collection run completes to fetch metadata and download links.
  • List CollectionsTool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints.
  • List DestinationsTool to list all destinations configured for the account. Use when you need to inspect or paginate through configured destinations.
  • List Requests PagedTool to list requests for a collection by page. Use when you need to fetch a specific batch of up to 1000 requests for a given collection.
  • 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.
  • Resend Result Set WebhookTool to resend the webhook for a previously generated result set. Use when a result set's webhook delivery needs a retry.
  • Start CollectionTool to start processing a collection's queued requests. Use after creating or pausing a collection to initiate its queued requests.
  • Stop All CollectionsTool to stop all collections. Use when you need to halt any running or queued collections after reviewing operations.
  • 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.
  • Update an existing collectionTool to update an existing collection. Use when you need to modify collection settings before scheduling runs.
  • Update DestinationTool to update a destination's configuration by ID. Use after creating or retrieving a destination to modify its settings.
  • 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.
Access, and who is in charge of it

You stay the boss of your Countdown API account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Countdown API account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Countdown API is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Countdown API and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Countdown API

Can an AI employee really work inside Countdown API?
Yes. It signs in to your own Countdown API account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Countdown API?
No. Nothing moves and nothing is replaced. Your records stay in Countdown API, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Countdown API account?
You paste in a key from your own Countdown API account. It is kept encrypted, and you can withdraw it from inside Countdown API whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Countdown API?
It has 23 ready-made tools in Countdown API today, among them Clear Collection Requests, Create a new collection and Create Destination. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Countdown API and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Countdown API and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Countdown API?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Countdown API is written down with what it did and when.