Ebay Sell Feed API
Browse all Ebay APIs✓ Official Vendor SpecE CommerceOrder Managementoauth223 EndpointsREST
For 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.
Use for: Create a task to bulk upload 5000 inventory updates, Schedule a daily export of completed orders for the last 24 hours, Download the result file for task ID 12345, List all schedules running on the seller's account
Not supported: 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.
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.
Install Jentic One Beta
Connect the Sell Feed API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sell Feed API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Sell Feed API.
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
Patterns agents use Sell Feed API for, with concrete tasks.
★ 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.
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.
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.
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.
Use Jentic to search 'submit eBay bulk feed task', load POST /task, and execute it with feedType=LMS_REVISE_INVENTORY_STATUS
Key Endpoints
23 endpoints — 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).
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
eBay OAuth 2.0 User refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped access token for the relevant sell.feed scope only — the refresh token, client secret, and seller OAuth consent never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'submit eBay bulk feed task' or 'schedule eBay order export') and Jentic returns the matching task or schedule operation with its parameter schema, so the agent calls the right endpoint without parsing eBay's feed documentation.
Time to first call
Direct integration: 5-10 days for OAuth Authorization Code flow plus the upload-poll-download lifecycle and feedType payload format handling. Through Jentic: 1-2 hours — search, load schema, execute task creation and result download.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Sell Feed API through Jentic.
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 the MAXsystem vault 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. Sign up at https://app.jentic.com/sign-up.
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.
GET STARTED