Account v1 API

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

✓ Official Vendor SpecE CommerceStorefrontoauth236 EndpointsREST

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.

Quickstart

Get started with Account v1 API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an eBay fulfillment policy"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Account v1 API 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

Define custom seller policies for product compliance, take-back, and regional disclosures

GET STARTED

Start building with Account v1 API API

Explore with Jentic

View OpenAPI Spec

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. Most write endpoints require a User access token issued through the OAuth Authorization Code grant; the API is designed to be the configuration layer that listing flows depend on, so policy IDs returned here are referenced from the Sell Inventory and Sell Marketing APIs.

Use Cases

Patterns agents use Account v1 API 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 though 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 sell.account scope only — the refresh token, client secret, and seller's OAuth consent never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create eBay fulfillment policy') and Jentic returns the matching policy operation with its required schema, so the agent calls the right endpoint without parsing eBay's seller documentation.

Time to first call

Direct integration: 5-10 days for OAuth Authorization Code flow, refresh handling, and the policy-and-tax data model. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

eBay Sell Fulfillment API

Sell Account creates the policies; Sell Fulfillment uses them when processing real orders.

Use Sell Account to set up policies once during onboarding, then use Sell Fulfillment for the day-to-day order and shipping operations.

Complementary

eBay Sell Compliance API

Sell Compliance flags listings violating policies; Sell Account fixes the underlying policy.

When Sell Compliance reports a policy-related violation, use Sell Account to update or replace the offending policy.

Complementary

eBay Sell Feed API

Sell Feed bulk-loads listings that reference Sell Account policy IDs.

Use Sell Account to obtain policy IDs, then use Sell Feed to bulk-create listings that reference them.

FAQs

Specific to using Account v1 API 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 the MAXsystem vault 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. Sign up at https://app.jentic.com/sign-up.

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.