Automate eBay Browse
HumDay reads eBay Browse’s own published API description and derives 11 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What eBay Browse is
The Browse API has the following resources: item_summary: Lets shoppers search for specific items by keyword, GTIN, category, charity, product, or item aspects and refine the results by using filters, such as aspects, compatibility, and fields values. (Experimental) search_by_image: Lets shoppers search for specific items by image. You can refine the results by using URI parameters and filte
API host: api.ebay.com
What HumDay can do in eBay Browse
5 documented operations change something in eBay Browse.
- POSTThis method checks if a product is compatible with the specified item.
/item/{item_id}/check_compatibility - POSTThis is an Experimental method.
/shopping_cart/add_item - POSTThis is an experimental method.
/shopping_cart/remove_item - POSTThis is an Experimental method.
/item_summary/search_by_image - POSTThis is an experimental method.
/shopping_cart/update_quantity
What HumDay can read from eBay Browse
These are the operations a schedule or a trigger can watch.
- GETThis method searches for eBay items by various query parameters and retrieves summaries of the items.
/item_summary/search - GETThis method retrieves the details of specific items that the buyer needs to make a purchasing decision.
/item/ - GETThis method retrieves the details of the individual items in an item group.
/item/get_items_by_item_group - GETThis method retrieves the details of a specific item, such as description, price, category, all item aspects, condition, return policies, seller feedback and score, shipping optio…
/item/{item_id} - GETThis is an experimental method.
/shopping_cart/ - GETThis method is a bridge between the eBay legacy APIs, such as Shopping, and Finding and the eBay Buy APIs.
/item/get_item_by_legacy_id
How automating eBay Browse works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live eBay Browse account.
- Grant access, then go live. You approve the specific eBay Browse operations it may use — and only those.
Automate eBay Browse with these
- eBay Account36 operations
- eBay Analytics2 operations
- eBay Buy Marketing1 operations
- eBay Catalog2 operations
- eBay Charity2 operations
- eBay Compliance3 operations
- eBay Deal4 operations
- eBay Feed23 operations
- eBay Finances7 operations
- eBay Fulfillment15 operations
- eBay Identity1 operations
- eBay Item Feed4 operations
Categories
Questions about eBay Browse automation
- Can HumDay connect to eBay Browse?
- Yes. HumDay reads eBay Browse's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 11 operations are documented.
- Do I need to write code to automate eBay Browse?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your eBay Browse account.
- What can HumDay do in eBay Browse?
- 5 of the 11 documented operations change something in eBay Browse, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my eBay Browse account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to eBay Browse is held behind that approval.
Where this came from
The operations above are read from a published API description for eBay Browse at developer.ebay.com/api-docs/master/buy/browse/openapi/2/buy_browse_v1_beta_oas2.json. Descriptions are the provider’s own words, not ours. Last published 2020-11-02.