eBay Compliance API

Name: eBay Compliance API
Brand: eBay Compliance API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontapiKey3 EndpointsREST

Install Jentic One Beta

Connect the eBay Compliance API to your agent

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

Retrieve detailed listing violations filtered by listing ID, compliance type, or marketplace

Pull a summary of violation counts grouped by compliance type to prioritise remediation

Suppress a specific listing violation once the seller has fixed the underlying issue

GET STARTED

Start building with eBay Compliance API

Explore with Jentic One

View OpenAPI Document

For Agents

Pull eBay listing violations and summary counts so agents can detect non-compliant listings, drive remediation, and suppress resolved violations.

Use for: I want to find every listing flagged for a missing GTIN, Get a summary of compliance violations on my eBay account, List all listings currently at risk of removal, Suppress a violation I have just remediated

Not supported: Does not handle listing creation, order processing, or financial settlement - use for reading and suppressing eBay listing compliance violations only.

Use Cases

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

★ Daily violation triage

Operations teams managing large eBay catalogues can call GET /listing_violation_summary every morning to see violation counts grouped by compliance type, then drill into GET /listing_violation for the highest-priority bucket. This pattern surfaces the few violation categories that block the most listings, so engineering effort lands where it removes the most risk.

Call GET /listing_violation_summary, sort buckets by count, then call GET /listing_violation filtered by the top compliance_type and return the affected listing IDs

Bulk remediation and suppression

Once a violation is fixed in the source catalogue (e.g., a GTIN is added across hundreds of listings), the seller can call POST /suppress_listing_violation per listing to tell eBay the issue is resolved. Bulk suppression is the only way to clear stale violation records at scale and restore search visibility quickly.

After updating GTINs on a batch of listings, iterate the affected listing IDs and call POST /suppress_listing_violation for each to clear the resolved violations

Marketplace-specific compliance monitoring

Sellers operating across multiple eBay marketplaces (US, UK, DE, AU) face different compliance regimes. Calling GET /listing_violation with a marketplace_ids filter isolates issues per region - for example EU GPSR violations only on EU sites - so localisation teams can address them with the right legal copy.

Call GET /listing_violation with marketplace_ids set to EBAY_DE and compliance_type PRODUCT_SAFETY, then return listings that need GPSR-compliant content

Agent-driven compliance check via Jentic

An AI agent acting as a compliance copilot can search Jentic for the eBay listing-violation summary operation and execute it daily. When the count crosses a threshold, the agent drills into the detailed endpoint, drafts remediation, and posts updates back to the seller's catalogue tool. Jentic stores the API-key credential in the vault so the agent never holds the raw key.

Search Jentic for 'check ebay listing violations', execute GET /listing_violation_summary, and if any compliance_type bucket exceeds 50 violations, fetch detailed listings and produce a remediation list

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/listing_violation

Retrieve detailed listing violations

GET

/listing_violation_summary

Pull violation counts grouped by type

POST

/suppress_listing_violation

Suppress a remediated violation

GET

/listing_violation

Retrieve detailed listing violations

GET

/listing_violation_summary

Pull violation counts grouped by type

POST

/suppress_listing_violation

Suppress a remediated violation

Why Jentic?

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

Setup

Wiring the eBay Compliance API by hand means setting up its API key auth and coding your own reads and suppressions of listing violations. Through Jentic you install once, import the eBay Compliance API from the API Directory, store the key once, and your agent calls it.

Permission scoping

eBay Compliance violation 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 listing violations and their summary, and leave suppress_listing_violation out of the allowed set. Every operation you grant is your explicit choice.

Credential isolation

Your eBay API key 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 'list listing compliance violations' or 'summarize violations for a seller', and Jentic returns the matching eBay Compliance operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using eBay Compliance API through Jentic.

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

eBay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call eBay Compliance 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 Compliance API use?

The Compliance API spec declares an `api_auth` API-key scheme passed via the `api_auth` header. In practice eBay seller APIs accept an OAuth 2.0 user token in this header position with the relevant sell.account / sell.inventory scopes. Through Jentic, the credential is stored encrypted in your Jentic One instance and injected at execution time.

Can I list every listing flagged for a missing GTIN?

Yes. Call GET /listing_violation with compliance_type set to PRODUCT_ADOPTION (or the relevant GTIN-specific type for your marketplace) to retrieve every listing flagged. The response includes the listingId, the violation reason, and the remediation guidance for the seller to act on.

How do I suppress a remediated violation through Jentic?

Install the SDK with `pip install jentic`, then search Jentic for `suppress an ebay listing violation`. Load the schema for POST /suppress_listing_violation, populate the listingId and complianceType, and execute. The violation is removed from the listing's risk record.

What are the rate limits for the eBay Compliance API?

Compliance endpoints fall under eBay's per-application daily call limit, typically 5,000 calls per day on production keys with per-second burst caps. For accounts with very large catalogues, paginate aggressively and prefer the summary endpoint for monitoring.

How is the summary endpoint different from the detail endpoint?

GET /listing_violation_summary returns aggregate counts grouped by compliance type - useful for dashboards and trigger logic. GET /listing_violation returns the per-listing records with full reason text and remediation guidance - use this once you know which compliance type to triage.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the eBay Compliance API operations and credentials the agent can use. You can grant read-only access to GET /listing_violation and GET /listing_violation_summary while leaving POST /suppress_listing_violation out of the allowed set, so the agent can monitor and triage violations without clearing any of them. Every operation the agent can call is your explicit choice.