Authenticate with an OAuth user token scoped for `sell.inventory` and `sell.fulfillment`.
Call `POST https://api.ebay.com/sell/feed/v1/task` (createTask) with the appropriate `feedType` (e.g., an LMS feed type for bulk listing upload) and set `schemaVersion` to `1.0` for Seller Hub feed types.
Upload your feed file to the task via `POST /sell/feed/v1/task/{taskId}/upload_file`; maximum feed file size is 25 MB — split larger catalogs into multiple tasks.
Poll `GET /sell/feed/v1/task/{taskId}` until `feedStatus` reaches `COMPLETED` or `COMPLETED_WITH_ERROR`.
Download the result file via `GET /sell/feed/v1/task/{taskId}/download_result_file` and parse it for per-listing status codes and error messages.
For any listings with errors, correct the data and re-submit only the failed records in a new task to avoid re-processing successful records.
Known gotchas
LMS feed types submit Trading API-compatible XML, while Seller Hub feed types use a different format; mixing them with the wrong `schemaVersion` or endpoint causes the entire task to fail.
Result files for large tasks can themselves be multi-megabyte downloads; implement streaming or paginated parsing rather than loading the entire result into memory.
Tasks are not automatically cleaned up; old completed tasks accumulate and can cause confusion when debugging — implement a retention policy to delete tasks after processing.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp