Endpoints
Create Operations:
- When using the
POSTmethod to create a resource, all Required fields must be included. Any Optional fields that are omitted will be set to their default values.
- When using the
PUTmethod to update a resource, all Write fields can be specified. Omitting any of these fields is treated as setting them tonull, where applicable.
Campaign Attributes
(*) Required for create operations
Digital Service Act (DSA)
In compliance with the Digital Services Act (DSA), marketplaces within the European Union will receive information about the company name associated with each advertisement.Create a Campaign
This endpoint creates a Sponsored Products (type: auction) or Onsite Display (type: preferred) campaign.
Retailer budget vs Criteo budget: Including retailerId in the request creates a retailer budget campaign. Omitting retailerId (or setting it to null) creates a standard Criteo budget campaign — retailerId will be null in the response.
Balance mapping at create time: You may optionally include drawableBalanceIds to map the campaign to one or more retailer budget balances at creation. All compatibility rules apply (same retailer, same billing type, same demand account). You can also map balances separately after creation using POST /balances/{balanceId}/campaigns/append.
Sample Request
cURL
Get All Campaigns by Account ID
This endpoint returns all campaigns for an account. Results are paginated usingpageIndex and pageSize query parameters; if omitted, defaults to 0 and 25, respectively. See API Response.
Sample Request
cURL
Get a Specific Campaign
This endpoint retrieves the specified campaign. Sample RequestcURL
Update a Specific Campaign
This endpoint allows you to update a specified campaign. The following example demonstrates how to switch to an uncapped campaign budget and modify the post-view attribution window. Sample RequestcURL
Responses
All validation errors on campaign create use
code: "validation-error".The error type is identified by a bracketed prefix in the title field.