Ebay Account v1 API

Name: Account v1 API
Brand: Account v1 API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontoauth236 EndpointsREST

Install Jentic One Beta

Connect the Account v1 API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Account v1 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.

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 | sh

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 instance

Jentic 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 Account v1 API.

Create and update fulfillment policies that define handling time and shipping options

Create and update payment policies that control how a seller accepts payment on listings

Create and update return policies covering return windows, restocking fees, and refund methods

GET STARTED

Start building with Account v1 API

Explore with Jentic

View OpenAPI Document

For Agents

Configure an eBay seller account programmatically - create and manage fulfillment, payment, and return policies, custom policies, sales tax tables, and seller programme opt-ins.

Use for: Create a fulfillment policy with 1-day handling time and free Standard Shipping, Update the return policy to a 30-day buyer-paid return window, List all payment policies on the seller's account, Retrieve a fulfillment policy by name 'Domestic_Free_Shipping'

Not supported: Does not handle listing creation, order processing, or financial reporting - use for seller account configuration (policies, tax, programmes) only.

Use Cases

Patterns agents use Account v1 API for, with concrete tasks.

★ Onboarding wizard for a multi-channel SaaS

A multi-channel seller tool walks new users through eBay setup: create a fulfillment policy via POST /fulfillment_policy, a payment policy via POST /payment_policy, and a return policy via POST /return_policy, each tied to the user's marketplace_id. The returned policy IDs are stored in the SaaS profile and re-used on every listing the tool publishes through the Inventory API.

POST a fulfillment_policy with marketplaceId=EBAY_US, name='Standard 1-day', handlingTime PT1D, then store the returned fulfillmentPolicyId on the tenant

Bulk policy migration during a marketplace expansion

A seller expanding from EBAY_US to EBAY_GB uses the Sell Account API to read every existing US policy via GET /fulfillment_policy, /payment_policy, /return_policy, then POST equivalent policies for the GB marketplace with adjusted shipping options and currency. The integration runs once per expansion and produces an audit log of created policy IDs.

List all fulfillment policies for EBAY_US, then for each one POST an EBAY_GB equivalent with currency GBP and a Royal Mail shipping service

Sales-tax table sync from an accounting system

Sellers operating in multiple US states use PUT /sales_tax/{countryCode}/{jurisdictionId} to push current state-level sales-tax rates from their accounting tool onto eBay listings. Running the sync nightly keeps eBay's automatically applied tax in step with rate changes from the seller's books of record.

For each US state in the local tax table, PUT /sales_tax/US/{state-code} with the current rate and shippingAndHandlingTaxed flag

Seller programme self-service

A seller dashboard lets users toggle eBay programme participation - eBay for Charity, Out of Stock Control, Promoted Listings - by calling POST /program/opt_in or POST /program/opt_out. GET /program/get_opted_in_programs reads the current state to drive the toggle UI, and GET /advertising_eligibility surfaces which advertising programmes the seller currently qualifies for.

Read /program/get_opted_in_programs, then for each toggle the user changes call /program/opt_in or /program/opt_out

AI agent integration via Jentic

An AI agent configuring a new seller's account searches Jentic for 'create eBay fulfillment policy'. Jentic returns the POST /fulfillment_policy operation with its required schema (marketplaceId, name, handlingTime, shippingOptions). The agent loads the schema, executes the call with a User access token issued through Jentic's vault, and stores the returned policy ID for downstream listing creation.

Use Jentic to search 'create eBay fulfillment policy', load POST /fulfillment_policy, and execute it with marketplaceId=EBAY_US and name='Standard 1-day'

Key Endpoints

36 endpoints — the ebay sell account api gives sellers programmatic control over their account configuration - ebay business policies (fulfillment, payment, return), custom seller-defined policies, sales-tax tables, opt-in to ebay seller programmes, kyc status, advertising eligibility, and rate-table lookups.

METHOD

PATH

DESCRIPTION

POST

/fulfillment_policy/

Create a fulfillment policy

GET

/fulfillment_policy

List fulfillment policies for a marketplace

POST

/payment_policy

Create a payment policy

POST

/return_policy

Create a return policy

POST

/program/opt_in

Opt the seller into an eBay programme

GET

/program/get_opted_in_programs

List programmes the seller is currently opted into

PUT

/sales_tax/{countryCode}/{jurisdictionId}

Set the sales-tax rate for a jurisdiction

GET

/kyc

Get seller KYC verification status

POST

/fulfillment_policy/

Create a fulfillment policy

GET

/fulfillment_policy

List fulfillment policies for a marketplace

POST

/payment_policy

Create a payment policy

POST

/return_policy

Create a return policy

POST

/program/opt_in

Opt the seller into an eBay programme

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

Agents search Jentic by intent such as 'create an eBay fulfillment policy' or 'set eBay sales tax', and Jentic returns the matching policy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Account v1 API through Jentic.

What authentication does the Sell Account API use?

The Sell Account API uses OAuth 2.0 with the Authorization Code grant - every endpoint operates in the authenticated 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 sell.account scope only.

Can I create a fulfillment policy with the Sell Account API?

Yes. POST /fulfillment_policy with marketplaceId, name, handlingTime, and shippingOptions creates a policy and returns its fulfillmentPolicyId. That ID is then attached to listings via the Sell Inventory API. PUT /fulfillment_policy/{fulfillmentPolicyId} updates an existing policy.

What are the rate limits for the Sell Account API?

Sell Account falls under eBay's Sell API user-context daily quota, issued per application-and-user pair. Use /user_rate_limit on the Developer Analytics API, looking at the sell.account entry, to read the live remaining count for the authenticated seller.

How do I opt a seller into the eBay for Charity programme through Jentic?

Search Jentic for 'opt in to an eBay seller program', load POST /program/opt_in, and execute it with the program code for the eBay for Charity programme. Use GET /program/get_opted_in_programs afterwards to confirm the change. Install with pip install jentic. Get started with Jentic One, the self-hosted execution layer.

Does the Sell Account API support custom seller policies?

Yes. POST /custom_policy/ creates a custom policy (e.g., a regional take-back disclosure) and PUT /custom_policy/{custom_policy_id} updates it. Custom policies are referenced from listings the same way as built-in fulfillment, payment, and return policies.

Can I read a seller's KYC status with the Sell Account API?

Yes. GET /kyc returns the authenticated seller's KYC verification status, useful for gating advanced features in a third-party tool until verification is complete. The endpoint requires the standard sell.account scope.

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

Yes. Jentic One is self-hosted, so your own rules decide which Sell Account operations and credentials the agent may use. You can allow it to read and create fulfillment or payment policies while leaving programme opt-in out unless you explicitly add it, and because operations like sales tax carry the resource id in the path (/sales_tax/{countryCode}/{jurisdictionId}), a rule can pin the agent to a single tax jurisdiction. Your eBay OAuth seller credentials are injected only at execution time and never reach the agent's prompt or context.

Ebay Account v1 API

Connect the Account v1 API to your agent

Capabilities

Start building with Account v1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs