This method updates an existing custom policy specified by the custom_policy_id path parameter. This method overwrites the policy's Name, Label, and Description fields. Therefore, the complete, current text of all three policy fields must be included in the request payload even when one or two of these fields will not actually be updated.
For example, the value for the Label field is to be updated, but the Name and Description values will remain unchanged. The existing Name and Description values, as they are defined in the current policy, must also be passed in.
A successful policy update call returns an HTTP status code of 204 No Content.
Note: Custom policies are no longer coupled with a specific eBay marketplace, so the EBAY-C-MARKETPLACE-ID request header is no longer needed or relevant for any of the Custom Policy methods.
This method is supported in Sandbox environment. To access the endpoint, just replace the
api.ebay.com root URI with
HTTP request headers
All requests made to eBay REST operations require you to provide the
Authorization HTTP header for authentication authorization.
The table below shows additional HTTP request headers that are either required, conditionally required, or strongly recommended for this method. Other standard HTTP request headers- opens rest request components page (not in this table) can also be used, but they are optional.
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.
Request payloadCopy complete valid JSON to clipboard
Details of the seller's specific policy and terms for this policy.
Customer-facing label shown on View Item pages for items to which the policy applies. This seller-defined string is displayed as a system-generated hyperlink pointing to detailed policy information.
The seller-defined name for the custom policy. Names must be unique for policies assigned to the same seller and policy type.
HTTP response headers
This call has no response headers.
This call has no payload.
This call has no field definitions.
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.
|409||Policy Name already used/ Maximum no of policies per site reached|
|500||Internal Server Error|
For more on errors, plus the codes of other common errors, see Handling errors.
|20418||API_ACCOUNT||REQUEST||This policy name is already used|
This call has no warnings.
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: Update a Custom Policy
This sample demonstrates how to update a take-back custom policy.
With an update method, the existing policy to update is specified with the custom_policy_id path parameter. All fields of the request payload (description, label, and name) must be passed in, even if one or two of them are not changing.
For this particular sample, only the name field is being updated, but the current values of description and label for the existing policy still must be passed in.
A successful call returns an HTTP status code of 204 No Content. There is no response payload.