Install Jentic One Beta

Connect the eBay Account API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the eBay Account 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.ebay.com%2Febay-account-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.ebay.com%2Febay-account-api" | 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 eBay Account API.

Create, update, and delete fulfillment policies that govern shipping options on a seller's listings

Manage payment policies including immediate-payment requirements and accepted methods

Define and update return policies covering return windows, return shipping, and refund methods

Author seller-defined custom policies (PRODUCT_COMPLIANCE, TAKE_BACK) and attach them to listings

GET STARTED

Start building with eBay Account API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Bulk policy provisioning for new sellers

Onboarding tools for new eBay sellers can create the full set of business policies - payment, fulfillment, and return - in one batch by calling POST /payment_policy, POST /fulfillment_policy/, and POST /return_policy. This produces a consistent listing template across thousands of items and lets the seller go live in minutes rather than configuring each policy manually in Seller Hub.

Call POST /payment_policy, POST /fulfillment_policy/, and POST /return_policy with the seller's standard configuration and store each returned policy_id for use on listings

Marketplace compliance via custom policies

Sellers shipping into regulated EU marketplaces can author seller-defined custom policies of type PRODUCT_COMPLIANCE and TAKE_BACK using POST /custom_policy and attach them to listings. The Account API exposes the create/update/get/delete cycle for custom policies so a compliance pipeline can keep policy text in sync with regulatory updates.

Call POST /custom_policy with policyType TAKE_BACK and the localised policy body, then PUT /custom_policy/{custom_policy_id} when regulatory text changes

Program opt-in for eBay Payments

Sellers migrating to the eBay Payments program can call GET /payments_program/{marketplace_id}/{payments_program_type} to read their current state and POST /program/opt_in to enroll. The onboarding endpoint at /payments_program/{marketplace_id}/{payments_program_type}/onboarding returns the URL the seller must complete to activate payouts. This automates a workflow that otherwise requires manual seller-hub navigation.

Call GET /payments_program/{marketplace_id}/EBAY_PAYMENTS, then POST /program/opt_in if not enrolled, and surface the onboarding URL from /payments_program/{marketplace_id}/EBAY_PAYMENTS/onboarding

Agent-driven policy update via Jentic

An AI agent helping a seller respond to a policy change (e.g., extending the return window) can search Jentic for the eBay return-policy update operation, load its schema, and execute the update across every return policy on the account. Jentic stores the OAuth credentials in the vault, so the agent updates production policies without ever holding the raw access token.

Search Jentic for 'update an ebay return policy', list all return policies via GET /return_policy, then call PUT /return_policy/{return_policy_id} for each with the new return window

Key Endpoints

36 endpoints — jentic publishes the only available openapi specification for ebay account api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/fulfillment_policy/

Create a new fulfillment policy

GET

/fulfillment_policy

List fulfillment policies

POST

/return_policy

Create a return policy

POST

/payment_policy

Create a payment policy

POST

/custom_policy

Create a seller-defined custom policy

POST

/program/opt_in

Opt the seller into a program

GET

/kyc

Retrieve the seller's KYC status

GET

/advertising_eligibility

Check eligibility for promoted listings

POST

/fulfillment_policy/

Create a new fulfillment policy

GET

/fulfillment_policy

List fulfillment policies

POST

/return_policy

Create a return policy

POST

/payment_policy

Create a payment policy

POST

/custom_policy

Create a seller-defined custom policy

POST

/program/opt_in

Opt the seller into a program

GET

/kyc

Retrieve the seller's KYC status

GET

/advertising_eligibility

Check eligibility for promoted listings

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the eBay Account API by hand means running its OAuth2 flow and coding your own calls to the fulfillment, return, and payment policy endpoints. Through Jentic you install once, import the eBay Account API from the API Directory, store the token once, and your agent calls it.

Permission scoping

eBay Account policy targets travel in the request body rather than as ids in the URL path, so limit the agent to the operations it needs, such as reading fulfillment policies or KYC status, and leave policy creation out of the allowed set. Every operation you grant is your explicit choice.

Credential isolation

Your eBay token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a fulfillment policy' or 'check advertising eligibility', and Jentic returns the matching eBay Account operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using eBay Account API through Jentic.

Why is there no official OpenAPI spec for eBay Account API?

eBay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call eBay Account API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the eBay Account API use?

The API uses OAuth 2.0 with the seller-account scope (https://api.ebay.com/oauth/api_scope/sell.account). Tokens are obtained via eBay's user-token flow. Through Jentic, the OAuth client credentials and refresh token live in your Jentic One instance and short-lived access tokens are minted per call.

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

Yes. POST /fulfillment_policy/ accepts a fulfillment policy body (handling time, shipping options, marketplace ID) and returns a fulfillmentPolicyId. You can later attach the policy to listings via the Inventory API or update it via PUT /fulfillment_policy/{fulfillmentPolicyId}.

How do I look up a payment policy by name through Jentic?

Install the SDK with `pip install jentic`, then search Jentic for `find an ebay payment policy by name`. Load the schema for GET /payment_policy/get_by_policy_name, populate marketplace_id and name, and execute. Jentic returns the matching policy object with its policy_id.

What are the rate limits for the eBay Account API?

Account API calls fall under eBay's standard application call limits - typically 5,000 calls per day per application key for production traffic, with per-second burst limits. Check your eBay Developer Program dashboard for the exact ceiling on your keyset.

Can I opt a seller into the eBay Payments program via the API?

Yes. Call POST /program/opt_in with the relevant program type, then read GET /payments_program/{marketplace_id}/{payments_program_type} to confirm enrollment state. The onboarding URL returned by /payments_program/{marketplace_id}/{payments_program_type}/onboarding completes any seller-side steps (e.g., bank verification) that require human action.

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

Yes. Because you self-host Jentic One, your own rules decide which eBay Account operations the agent may call, so you can grant read-only access to endpoints like GET /fulfillment_policy or GET /kyc while leaving policy creation such as POST /fulfillment_policy/ and POST /custom_policy out of the allowed set. This matters here because eBay carries policy targets in the request body rather than as ids in the URL path, so scoping is enforced at the operation level rather than by path pattern. Your stored eBay credentials are injected only for the operations you have explicitly granted, and every operation the agent can reach is your deliberate choice.

eBay Account API

Browse all Ebay APIs

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticE CommerceStorefrontoauth236 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Configure eBay seller policies (fulfillment, payment, return, custom) and program opt-ins, plus read advertising eligibility and KYC status, all from one structured surface.

Use for: I want to create a new fulfillment policy with free shipping, Update the return window on my standard return policy, List all payment policies on my eBay seller account, Opt my account into the eBay Payments program

Not supported: Does not handle order processing, listing creation, or financial settlement - use for configuring eBay seller policies, programs, and account settings only.

Jentic publishes the only available OpenAPI specification for eBay Account API, keeping it validated and agent-ready. The Account API lets eBay sellers configure the operational policies that drive every listing - fulfillment policies, payment policies, return policies, and seller-defined custom policies. It also exposes endpoints for opting into and out of programs (such as the eBay Payments program), retrieving sales tax tables and rate tables, checking advertising eligibility, and reading KYC status. Authentication is OAuth 2.0 with the seller-account scope.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

85%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the eBay Account API to your agent

Capabilities

Start building with eBay Account API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

eBay Account API

Jentic AI Readiness Score

Account API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness