Automate eBay Fulfillment
HumDay reads eBay Fulfillment’s own published API description and derives 15 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 Fulfillment is
Use the Fulfillment API to complete the process of packaging, addressing, handling, and shipping each order on behalf of the seller, in accordance with the payment method and timing specified at checkout.
API host: api.ebay.com{basepath}
What HumDay can do in eBay Fulfillment
7 documented operations change something in eBay Fulfillment.
- POSTIssue Refund
/order/{order_id}/issue_refund - POSTWhen you group an order's line items into one or more packages, each package requires a corresponding plan for handling, addressing, and shipping; this is a shipping fulfillment.
/order/{orderId}/shipping_fulfillment - POSTAdd an Evidence File
/payment_dispute/{payment_dispute_id}/add_evidence - POSTUpload an Evidence File
/payment_dispute/{payment_dispute_id}/upload_evidence_file - POSTAccept Payment Dispute
/payment_dispute/{payment_dispute_id}/accept - POSTContest Payment Dispute
/payment_dispute/{payment_dispute_id}/contest - POSTUpdate evidence
/payment_dispute/{payment_dispute_id}/update_evidence
What HumDay can read from eBay Fulfillment
These are the operations a schedule or a trigger can watch.
- GETUse this call to search for and retrieve one or more orders based on their creation date, last modification date, or fulfillment status using the filter parameter.
/order - GETSearch Payment Dispute by Filters
/payment_dispute_summary - GETUse this call to retrieve the contents of an order based on its unique identifier, orderId.
/order/{orderId} - GETGet Payment Dispute Evidence File
/payment_dispute/{payment_dispute_id}/fetch_evidence_content - GETGet Payment Dispute Details
/payment_dispute/{payment_dispute_id} - GETUse this call to retrieve the contents of all fulfillments currently defined for a specified order based on the order's unique identifier, orderId.
/order/{orderId}/shipping_fulfillment - GETGet Payment Dispute Activity
/payment_dispute/{payment_dispute_id}/activity - GETUse this call to retrieve the contents of a fulfillment based on its unique identifier, fulfillmentId (combined with the associated order's orderId ).
/order/{orderId}/shipping_fulfillment/{fulfillmentId}
How automating eBay Fulfillment 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 Fulfillment account.
- Grant access, then go live. You approve the specific eBay Fulfillment operations it may use — and only those.
Automate eBay Fulfillment with these
Categories
Questions about eBay Fulfillment automation
- Can HumDay connect to eBay Fulfillment?
- Yes. HumDay reads eBay Fulfillment's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 15 operations are documented.
- Do I need to write code to automate eBay Fulfillment?
- 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 Fulfillment account.
- What can HumDay do in eBay Fulfillment?
- 7 of the 15 documented operations change something in eBay Fulfillment, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my eBay Fulfillment 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 Fulfillment is held behind that approval.
Where this came from
The operations above are read from a published API description for eBay Fulfillment at developer.ebay.com/api-docs/master/sell/fulfillment/openapi/3/sell_fulfillment_v1_oas3.jso. Descriptions are the provider’s own words, not ours. Last published 2023-03-05.