The eBay API for sellers: what it is, how tools use it, and what to ask a vendor

What is the eBay API for sellers?

The eBay API for sellers is the set of official interfaces that let software read and change an eBay account on the seller's behalf. API stands for application programming interface: a defined way for one program to ask another to do something. When a repricer changes your price, a listing tool publishes a draft, or an order tool uploads tracking, it does it by sending a request to eBay's API, and eBay carries it out.

You do not need to write code to benefit. Almost every seller tool is built on eBay's APIs. Knowing roughly how they work helps you judge which tools are well built and which questions to ask before connecting one.

How does a tool get access to your eBay account?

Access works through a consent step on eBay's own site. The tool sends you to an eBay sign-in page; you sign in there, eBay shows what the tool is asking to do, and you approve or decline. If you approve, eBay gives the tool a permission to act for you. The tool never needs your eBay password.

• You stay in control: the permission can be withdrawn from your eBay account settings at any time.
• The scope is visible: the consent screen lists the kinds of access the tool requests.
• A password request is a warning: a tool that asks for your eBay password instead of using this consent step is not following the official route.

When access stops working

Permissions do not always last for ever. A connection can stop working if you change certain account settings, withdraw access, or if the permission needs renewing. When that happens, the tool can no longer send changes, and your listings keep whatever price and quantity they had. A good tool tells you clearly when its connection to eBay has failed, so you can reconnect before prices and stock drift. Ask how the vendor alerts you, and check the connection status after any change to your eBay account.

What can sellers' tools do through eBay's APIs?

eBay's APIs cover most of what you can do in Seller Hub, which is why tools can automate so much. The table groups the main areas by the jobs sellers use them for.

eBay has more than one family of interfaces, built at different times. Newer and older interfaces can overlap in what they do. Some listing features are handled differently between them, so ask a vendor which ones their tool uses and whether listings created elsewhere, for example in Seller Hub or by a previous tool, can be managed by it.

Reading versus changing

Some access only lets a tool read information, such as orders or fees. Other access lets it change things, such as prices, quantities or listings. A reporting tool needs only to read; a repricer needs to change prices and quantities. When a tool asks for more than its job requires, ask why. Less access means less that can go wrong if the tool, or the vendor, ever has a problem.

Why do eBay API call limits matter?

eBay limits how many requests an application can send in a given period. The exact limits depend on the interface and the application, and they are set out in eBay's developer documentation at developer.ebay.com. For you, the practical point is that a tool cannot update unlimited listings as often as it likes.

Well-built tools work within limits by being efficient: they update only listings whose price or quantity actually needs to change, group changes where eBay allows it, and put the most important updates first, such as a listing that just sold or went out of stock.

Example (hypothetical): suppose a tool can make a fixed number of updates per day for your account, and you have 5,000 listings. A tool that sends every listing's price every hour, changed or not, would run through its allowance quickly and then stall. A tool that checks the supplier first and sends only the 300 listings whose price really moved uses a fraction of the allowance and keeps room for urgent stock changes.

If you use several tools on one eBay account, remember that each has its own application and limits, but they all change the same listings. Efficiency in each tool does not help if two tools are both rewriting the same prices.

Notifications instead of constant checking

Some events, such as a new order, can be sent by eBay to a tool as they happen, rather than the tool asking again and again. Tools that use these notifications where available react faster to sales and use less of their allowance on checking. Ask a vendor how quickly a new eBay order appears in their tool.

What should a tool record about its API changes?

Every change a tool makes through the API should leave a trace you can read. When a price looks wrong or a listing changes unexpectedly, the log is how you find out what happened.

1. What changed: the field, the old value and the new value.
2. When: the time the change was sent.
3. Why: the reason, such as "supplier price up" or "supplier out of stock".
4. The result: whether eBay accepted or refused the change, and eBay's reason for a refusal.

For sellers who source from Amazon, Dropizon sends changes to eBay through eBay's official APIs, with a reason recorded for every push and every hold. The documentation explains what each reason means.

Does API access change what eBay allows?

No. API access is a technical channel; your listings and sourcing still have to follow eBay's policies. eBay allows dropshipping from a wholesale supplier, but listing an item and then buying it from another retailer or marketplace that ships directly to your buyer is not allowed, and that includes Amazon. Read eBay's drop shipping policy. You remain responsible for delivery within your stated time and for buyer satisfaction.

Should you build your own eBay API connection?

Some larger sellers build their own connection to eBay. It gives full control: your own database, your own pricing logic and your own reports. It also brings everything a software company deals with.

• Registration: you need to register with eBay's developer programme and follow its terms for applications.
• Building: a developer has to write and test the code that lists, revises and reads orders.
• Limits: your application has its own call limits, which you must design around.
• Upkeep: eBay updates and retires interfaces over time, so the code needs maintaining.
• Security: you become responsible for storing access permissions and buyer data safely.

For most sellers, an existing tool built on eBay's APIs is cheaper and faster. Building your own makes sense when your needs are unusual, your volume is high and you have someone who can maintain it for years, not just build it once.

Which API questions should you ask a vendor?

• Does your tool connect through eBay's own consent screen?
• Which kinds of access does it request, and why does it need each one?
• Which eBay interfaces does it use, and can it manage listings created in Seller Hub or by another tool?
• How does it stay within eBay's call limits at my listing count?
• Which updates get priority when the allowance is tight?
• How does it show me updates that eBay refused, and why?
• What happens to its access if I cancel my plan?
• How will you tell me if the connection to eBay stops working?

Keep the answers. They tell you a lot about how carefully the tool is built. A vendor who answers these clearly, in writing, has usually thought about the problems you will meet at scale; a vendor who cannot answer them may not have. For the security side of connecting tools, read our guide to dropshipping software security, and for the jobs worth automating once a tool is connected, our guide to eBay automation tools.