canonical: https://jentic.com/apis/api.ebay.com/ebay-sell-compliance-api

# eBay Sell Compliance API

Jentic publishes the only available OpenAPI specification for eBay Sell Compliance API, keeping it validated and agent-ready. Sell Compliance is the canonical sell- namespace surface for eBay listing risk - detailed violations, summary counts grouped by compliance type, and a suppression endpoint for clearing remediated violations. Sellers, agencies, and catalogue automation tools rely on it to keep listings free of suppression risk on US, UK, EU, and AU marketplaces. The standard workflow is poll, fix at scale, then suppress.

## For AI agents

Read eBay listing violations, summary counts, and suppress remediated issues so agents can keep large catalogues free of suppression risk.

## Scope

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

## Capabilities

- Retrieve detailed listing violations filtered by listing ID, compliance type, or marketplace
- Pull a summary of violation counts grouped by compliance type to drive triage
- Suppress a specific listing violation once the underlying issue is fixed
- Filter violations by remediation requirement and compliance state to focus urgent cases
- Page through large violation result sets for accounts with thousands of listings

## Use cases

### Daily violation triage

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

Example prompt: Call GET /listing_violation_summary, pick the top compliance_type bucket by count, then call GET /listing_violation filtered by that type

### Bulk remediation and suppression

Once a violation is fixed in the catalogue (e.g., missing GTINs added across hundreds of listings), the seller calls POST /suppress_listing_violation per listing to clear the resolved record. Bulk suppression restores listing visibility quickly - without it, stale violation flags can continue to suppress search rank.

Example prompt: After updating GTINs across affected listings, iterate the 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 face different compliance regimes per region. Calling GET /listing_violation with a marketplace_ids filter isolates issues per region - for example PRODUCT_SAFETY violations only on EBAY_DE - so localisation teams can address them with the right legal copy.

Example prompt: Call GET /listing_violation with marketplace_ids EBAY_DE and compliance_type PRODUCT_SAFETY to surface listings needing GPSR-compliant content

### Agent-driven compliance copilot 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 a bucket exceeds threshold the agent drills into the detail endpoint, drafts remediation, and posts updates back to the catalogue tool. Jentic keeps the credential in the vault.

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

## Key endpoints

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

## Key resources

- **listing_violation** — Detailed records of listings flagged for non-compliance
- **listing_violation_summary** — Counts of violations grouped by compliance type
- **suppress_listing_violation** — Mark a violation as remediated to clear it

## Why Jentic

- **Setup:** Wiring the eBay Sell 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 Sell Compliance API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** eBay Sell 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 handling:** 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.
- **Discovery method:** Agents search Jentic by intent such as 'list listing compliance violations' or 'summarize violations for a seller', and Jentic returns the matching eBay Sell Compliance operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **eBay Compliance API** — Same 3-endpoint surface under the legacy slug
- **eBay Sell Account API** — Sell Account is where the policies that resolve compliance violations are configured
- **eBay Sell Analytics API** — Sell Analytics correlates rising violations with falling traffic and sales
- **eBay Sell Fulfillment API** — Sell Fulfillment processes orders for compliant listings

## FAQ

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

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

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

### How is sell-compliance different from compliance-api?

Sell Compliance is the same 3-endpoint surface under eBay's modern sell- namespace; compliance-api is the legacy slug. New integrations should target sell-compliance.

### Can I suppress a remediated violation through Jentic?

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

### What are the rate limits for the Sell Compliance API?

Sell Compliance inherits eBay's per-application daily limit - typically 5,000 calls per day in production with per-second burst caps. For very large catalogues paginate aggressively and prefer the summary endpoint for monitoring.

### What is the difference between the summary and detail endpoints?

GET /listing_violation_summary returns aggregate counts grouped by compliance type - useful for dashboards and triggers. 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 Sell Compliance API?

Yes. Because you run Jentic One yourself, your own rules decide which of the three operations the agent may call and which credentials it may use. For a read-only compliance monitor, grant only GET /listing_violation and GET /listing_violation_summary and leave the mutating POST /suppress_listing_violation out of the allowed set, so the agent can surface listing violations and their summary counts but cannot clear any record. Every operation the agent can reach is a choice you make explicitly.