canonical: https://jentic.com/apis/ebay.com/sell-feed

# Ebay Sell Feed API

The eBay Sell Feed API is a bulk-processing surface for sellers - upload large input files (orders, inventory, listings) and download large output reports (LMS reports, customer-service metric tasks, fulfillment exports). It supports three modes: ad-hoc tasks (POST /task or /order_task or /inventory_task), recurring schedules tied to a schedule template (POST /schedule), and on-demand customer-service metric tasks (/customer_service_metric_task). Sellers operating thousands of SKUs use it instead of per-row Sell Inventory and Sell Fulfillment calls - one feed replaces a long sequence of API roundtrips.

## For AI agents

Run bulk seller jobs on eBay - upload listing/order/inventory feed files, schedule recurring exports, and download report files. 23 endpoints across tasks, schedules, and templates.

## Scope

Does not handle real-time per-item operations, payment processing, or buyer-side catalogue search - use for asynchronous bulk seller feed jobs and recurring report exports only.

## Capabilities

- Submit ad-hoc bulk listing, inventory, or order feed jobs via POST /task with an LMS-format payload
- Schedule recurring feed jobs against a schedule template, e.g., daily order export
- Download a feed job's input file (the seller-uploaded payload) for audit and replay
- Download a feed job's result file containing eBay's response or the generated report
- Upload a payload file directly to a created task with POST /task/{task_id}/upload_file
- Run customer-service metric tasks to export benchmark data for offline analysis
- List available schedule templates and inspect their cadence and supported feed types

## Use cases

### Nightly order export to an ERP

ERP integrations create a recurring schedule via POST /schedule against the LMS_ORDER_REPORT template, with cadence WEEKLY or DAILY. Each cycle eBay generates the report and the integration calls /schedule/{schedule_id}/download_result_file to pull it into the ERP overnight, replacing what would otherwise be tens of thousands of /sell/fulfillment/v1/order calls.

Example prompt: POST /schedule with feedType=LMS_ORDER_REPORT and frequency=DAILY, then nightly call /schedule/{schedule_id}/download_result_file

### Bulk inventory refresh after a supplier update

When a supplier sends a stock and price update for tens of thousands of SKUs, the seller's tool POSTs an inventory task via /inventory_task with the LMS_REVISE_INVENTORY_STATUS feedType, then POSTs the data file to /task/{task_id}/upload_file. eBay processes the batch asynchronously and the integration polls /task/{task_id} until status is COMPLETED, then downloads the result file with per-row success or error.

Example prompt: POST /inventory_task with feedType=LMS_REVISE_INVENTORY_STATUS, upload the CSV via /task/{task_id}/upload_file, poll /task/{task_id} until COMPLETED, then download the result

### Customer-service metric task for offline analysis

Sellers running cohort analyses pull customer-service metrics into their warehouse by creating /customer_service_metric_task entries per metric type. Each task generates a downloadable file containing the seller's metric values plus the peer-group benchmark for the requested period, ready for ingestion into a BI tool.

Example prompt: POST /customer_service_metric_task with metricType=ITEM_NOT_RECEIVED_RATE and date range, poll until COMPLETED, then download the result file

### AI agent integration via Jentic

An AI agent that runs nightly batch operations searches Jentic for 'submit eBay bulk feed task'. Jentic returns the POST /task operation with its required schema (feedType, schemaVersion). The agent loads the schema, executes the call with a User access token issued through Jentic's vault, then orchestrates the upload-poll-download cycle without writing eBay-specific feed code.

Example prompt: Use Jentic to search 'submit eBay bulk feed task', load POST /task, and execute it with feedType=LMS_REVISE_INVENTORY_STATUS

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /task | Create a generic ad-hoc feed task |
| POST | /task/{task_id}/upload_file | Upload the payload file for a created task |
| GET | /task/{task_id}/download_result_file | Download a completed task's result file |
| POST | /order_task | Create an order-specific feed task |
| POST | /inventory_task | Create an inventory-specific feed task |
| POST | /schedule | Create a recurring feed schedule |
| GET | /schedule_template | List available schedule templates |
| POST | /customer_service_metric_task | Create a customer-service metric export task |

## Key resources

- **task** — Generic ad-hoc feed tasks - upload payload, poll status, download result
- **order_task** — Order-specific feed jobs (bulk order processing and exports)
- **inventory_task** — Inventory-specific feed jobs (bulk listing and inventory updates)
- **schedule** — Recurring feed schedules tied to a schedule template
- **schedule_template** — Templates that describe a feedType, cadence, and accepted format
- **customer_service_metric_task** — On-demand exports of customer-service metrics with peer benchmarks

## Why Jentic

- **Setup:** Wiring the eBay Sell Feed API by hand means implementing eBay's OAuth 2.0 authorization-code flow for a seller user token, managing asynchronous task upload and download steps, and pointing requests at the api.ebay.com sell/feed host. Through Jentic you install once, import the Sell Feed API from the API Directory, store the eBay OAuth credentials once, and your agent calls it.
- **Permission scoping:** Feed operations put the task id in the URL path, such as /task/{task_id}/upload_file and /task/{task_id}/download_result_file, so a rule can pin your agent to one feed task. You choose the operations it may call, so you can allow creating tasks and downloading results while leaving recurring schedule creation out unless you add it.
- **Credential handling:** Your eBay OAuth seller credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'submit an eBay bulk feed task' or 'schedule an eBay order export', and Jentic returns the matching task or schedule operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **eBay Sell Fulfillment API** — Sell Fulfillment is the per-row order surface; Sell Feed is the bulk-export equivalent.
- **eBay Sell Account API** — Sell Account creates the policies that listings in a Sell Feed payload reference.
- **eBay Item Feed Service** — Item Feed Service is the buyer-side bulk catalogue download; Sell Feed is the seller-side bulk operations surface.

## FAQ

### What authentication does the Sell Feed API use?

The Sell Feed API uses OAuth 2.0 with the Authorization Code grant - every endpoint operates in the seller's context, so a User access token is required. Through Jentic, the seller's refresh token sits in your Jentic One instance and the agent receives a scoped access token for the relevant sell.feed scope only.

### Can I bulk-update inventory with the Sell Feed API?

Yes. POST /inventory_task with feedType=LMS_REVISE_INVENTORY_STATUS (or another supported inventory feed type), then upload the payload via POST /task/{task_id}/upload_file. eBay processes asynchronously - poll GET /task/{task_id} until status is COMPLETED, then download the per-row result via /task/{task_id}/download_result_file.

### What are the rate limits for the Sell Feed API?

Sell Feed falls under the Sell APIs user-context daily quota issued per application-and-user pair. Call /user_rate_limit on the Developer Analytics API and inspect the sell.feed entry to read the live remaining count for the authenticated seller.

### How do I schedule a recurring order export through Jentic?

Search Jentic for 'schedule recurring eBay order export', load POST /schedule, and execute it with the feedType (e.g., LMS_ORDER_REPORT) and cadence. Use GET /schedule_template first to see the supported template IDs. Install with pip install jentic. Get started with Jentic One, the self-hosted execution layer.

### What feed types does the Sell Feed API support?

The supported types are documented as the feedType enum on each task creation endpoint and include LMS_ORDER_REPORT, LMS_REVISE_INVENTORY_STATUS, LMS_ACTIVE_INVENTORY_REPORT, and several others for listing management, store category management, and customer-service metric tasks. Use GET /schedule_template to see which feed types pair with which scheduling cadences.

### Are feed jobs processed synchronously?

No. Feed jobs are asynchronous. The POST creates a task and returns a task_id, after which the seller's integration polls /task/{task_id} until status is COMPLETED or COMPLETED_WITH_ERROR before downloading the result file. Allow several minutes to several hours depending on payload size.

### Can I limit what my agent is allowed to do with the eBay Sell Feed API?

Yes. Jentic One is self-hosted, so your own rules decide which Sell Feed operations and credentials the agent may use. You can allow it to create feed tasks and download results with POST /task and GET /task/{task_id}/download_result_file while leaving recurring schedule creation via POST /schedule out unless you add it. Because operations like /task/{task_id}/upload_file and /task/{task_id}/download_result_file carry the task id in the path, a rule can pin the agent to a single feed task.