AT_RISKstate (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_ADOPTIONlisting violations in the
AT_RISKstate. 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.
Resource URI (production)
HTTP request headers
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):
See OAuth access tokens for more information.
|complianceType||ComplianceTypeEnum||The 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
|listingId||string||The 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
For more on errors, plus the codes of other common errors, see Handling errors.
|850001||API_COMPLIANCE||APPLICATION||Any System error|
|850110||API_COMPLIANCE||REQUEST||Compliance type is invalid|
|850111||API_COMPLIANCE||REQUEST||Compliance type is missing|
|850112||API_COMPLIANCE||REQUEST||Invalid listing_id specified|
|850113||API_COMPLIANCE||REQUEST||listing_id not specified|
|850120||API_COMPLIANCE||REQUEST||Listing is already compliant. You can not suppress compliant listing|
|850121||API_COMPLIANCE||REQUEST||Listing has required aspects not filled. You can not suppress the violation when required aspects are missing|
|850122||API_COMPLIANCE||REQUEST||Violation is already suppressed on this listing|
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
ASPECTS_ADOPTIONlisting violation (in the
AT_RISKstate) for a specific listing.
ASPECTS_ADOPTIONas the complianceType, and identifies the listing through the listingId field.
204 Success. There is no response payload.