compliance API1.4.1

suppressViolation

POST
/suppress_listing_violation
This call suppresses a listing violation for a specific listing. Only listing violations in the AT_RISK state (returned in the violations.complianceState field of the getListingViolations call) can be suppressed.

Note: At this time, the suppressViolation call only supports the suppressing of ASPECTS_ADOPTION listing violations in the AT_RISK state. In the future, it is possible that this method can be used to suppress other listing violation types.

A successful call returns a http status code of 204 Success. There is no response payload. If the call is not successful, an error code will be returned stating the issue.

Input

Resource URI (production)

POST https://api.ebay.com/sell/compliance/v1/suppress_listing_violation

URI parameters

HTTP request headers

All requests made to eBay REST operations require you to provide the Authorization HTTP header for authentication authorization.

OAuth scope

This request requires an access token created with the authorization code grant flow, using one or more scopes from the following list (please check your Application Keys page for a list of OAuth scopes available to your application):

https://api.ebay.com/oauth/api_scope/sell.inventory

See OAuth access tokens for more information.

Input container/fieldTypeDescription
complianceTypeComplianceTypeEnumThe compliance type of the listing violation to suppress is specified in this field. The compliance type for each listing violation is found in the complianceType field under the listingViolations array in a getListingViolations response.

Note: At this time, the suppressViolation method is only used to suppress aspect adoption listing violations in the 'at-risk' state, so ASPECTS_ADOPTION is currently the only supported value for this field.

Occurrence:

listingIdstringThe unique identifier of the listing with the violation(s) is specified in this field. The unique identifier of the listing with the listing violation(s) is found in the listingId field under the listingViolations array in a getListingViolations response.

Note: At this time, the suppressViolation method is only used to suppress aspect adoption listing violations in the 'at-risk' state, so the listing specified in this field should be a listing with an ASPECTS_ADOPTION violation in the 'at-risk' state.

Occurrence:

Output

HTTP response headers

HTTP status codes

This call can return one of the following HTTP status codes. For an overview of the status codes, see HTTP status codes in Using eBay RESTful APIs.

StatusMeaning
204Success
400Bad Request
409Business error
500Internal Server Error

Error codes

For more on errors, plus the codes of other common errors, see Handling errors.

CodeDomainCategoryMeaning
850001API_COMPLIANCEAPPLICATIONAny System error
850110API_COMPLIANCEREQUESTCompliance type is invalid
850111API_COMPLIANCEREQUESTCompliance type is missing
850112API_COMPLIANCEREQUESTInvalid listing_id specified
850113API_COMPLIANCEREQUESTlisting_id not specified
850120API_COMPLIANCEREQUESTListing is already compliant. You can not suppress compliant listing
850121API_COMPLIANCEREQUESTListing has required aspects not filled. You can not suppress the violation when required aspects are missing
850122API_COMPLIANCEREQUESTViolation is already suppressed on this listing

Warnings

Samples

New to making API calls? Please see Making a Call.

Note: Identifiers, such as order IDs or user IDs, and personal data in these samples might be anonymized or may no longer be active on eBay. If necessary, substitute current, relevant eBay data in your requests.

Sample 1: Suppress violation for a listing

This call suppresses a ASPECTS_ADOPTION listing violation (in the AT_RISK state) for a specific listing.

Input

In the request payload, the user passes in ASPECTS_ADOPTION as the complianceType, and identifies the listing through the listingId field.
POST
https://api.ebay.com/sell/compliance/v1/suppress_listing_violation

Output

A successful call returns a http status code of 204 Success. There is no response payload.