Skip to main content


This method launches a priority strategy campaign created using the setupQuickCampaign method that is in DRAFT status. This changes the campaign status to RUNNING or SCHEDULED, based on its specified start date. Specify the campaign you wish to launch by supplying its campaign_id as a path parameter in the call URI.

Use the getCampaigns method to retrieve the campaign_id and the campaign status for all the seller's campaigns.


Resource URI


This method is supported in Sandbox environment. To access the endpoint, just replace the root URI with

URI parameters

campaign_idstringThis path parameter specifies the unique eBay-assigned identifier of the ad campaign being launched.

For priority strategy campaigns created with the setupQuickCampaign method, the getCampaign URI for that campaign is returned in the Location response header. That URI will include the campaign_id value, which you will pass in as a path parameter in the launchCampaign method.

Note: The campaign ID value used here must be for a priority strategy campaign in DRAFT status.

Occurrence: Required

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

See OAuth access tokens for more information.

Request payload

This call has no payload.

Request fields

This call has no field definitions.


HTTP response headers

This call has no response headers.

Response payload

This call has no payload.

Response fields

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.

204No Content
400Bad Request
409Business error
500Internal Server error

Error codes

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

35001API_MARKETINGAPPLICATIONThere was a problem with an eBay internal system or process. Contact eBay Developer Technical Support for assistance.
35002API_MARKETINGAPPLICATIONInternal error. Please wait a few minutes and try the call again.
35021API_MARKETINGREQUESTA campaign with the name of {campaignName} already exists. Please provide a different name.
35043API_MARKETINGREQUESTThe campaign status of {campaignStatus} is either invalid or not supported for this operation.
35045API_MARKETINGREQUESTNo campaign found for campaign id {campaign_id}.
35067API_MARKETINGBUSINESSThe seller must accept the Promoted Listings terms and conditions. Please accept Promoted Listings terms and conditions by visiting this link {userAgreementLink} .


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: Launch a Draft Campaign

This method launches a campaign that is in DRAFT status. Check the status of a campaign using the getCampaign call.


This call does not have a request payload. Specify the campaign to launch using the campaign_id URI parameter.



A successful call returns the HTTP status code 204 No content. This method has no response payload.

Got thoughts? Click the feedback button – your insights help us improve!