Get Payment Dispute Activity in eBay Fulfillment
A documented eBay Fulfillment operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get Payment Dispute Activity
- GETReads data · paymentdispute
api.ebay.com{basepath}/payment_dispute/{payment_dispute_id}/activity
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which eBay Fulfillment operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other eBay Fulfillment operations
- Issue RefundPOST · changes data
- When you group an order's line items into one or more packagesPOST · changes data
- Add an Evidence FilePOST · changes data
- Upload an Evidence FilePOST · changes data
- Accept Payment DisputePOST · changes data
- Contest Payment DisputePOST · changes data
- Update evidencePOST · changes data
- Use this call to search for and retrieve oneGET · reads data
Questions
- Can HumDay get payment dispute activity in eBay Fulfillment?
- Yes. This operation is published in eBay Fulfillment's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my eBay Fulfillment account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in eBay Fulfillment.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your eBay Fulfillment account.
Where this came from
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. The description above is the provider’s own wording, not ours. Last published 2023-03-05.