Getting StartedLearn more about campaign management with our API here
Endpoints
Balance Parameters
| Attribute | Data Type | Description |
|---|---|---|
id | string | Balance IDAccepted values: string of int64 Writeable? N / Nullable? N |
name* | string | Balance nameAccepted values: up to 255-char strings Writeable? Y / Nullable? N |
poNumber | string | Purchase order numberAccepted values: up to 32-char strings Writeable? Y / Nullable? Y |
deposited | decimal | Amount of funds deposited; uncapped if nullAccepted values: deposited ≥ 0.0Writeable? Y / Nullable? Y |
spent | decimal | Amount of funds already spentAccepted values: 0 ≤ spent ≤ depositedWriteable? N / Nullable? N |
remaining | decimal | Amount of funds already spentAccepted values: 0 ≤ remaining ≤ deposited (or null, if deposited not set)Writeable? N / Nullable? Y |
startDate* | timestamp | Balance start date; if time zone is not set, will consider Account’s time zone as defaultAccepted values: yyyy-mm-ddThh:mm:ss±hh:mm(in ISO-8601 )Writeable? Y / Nullable? N |
endDate | timestamp | Balance end date; if time zone is not set, will consider Account’s time zone as defaultAccepted values: yyyy-mm-ddThh:mm:ss±hh:mm(in ISO-8601 )Default: if null or absent, balance will be available indefinitelyWriteable? Y / Nullable? Y |
status | enum | Balance current statusAccepted values: active, scheduled, endedWriteable? N / Nullable? N |
createdAt | timestamp | Timestamp of balance creation, in UTCAccepted values: yyyy-mm-ddThh:mm:ss±hh:mm (in ISO-8601)Writeable? N / Nullable? N |
updatedAt | timestamp | Timestamp of last balance update, in UTCAccepted values: yyyy-mm-ddThh:mm:ss±hh:mm (in ISO-8601)Writeable? N / Nullable? N |
memo | string | An optional memo note that can be set in the balanceAccepted values: up to 250-char strings Writeable? Y / Nullable? Y |
balanceType | enum | The balance type is computed based on the deposited amount:Accepted values: capped, uncappedWriteable? N / Nullable? N
|
spendType | enum | The type of balance that will be used based on the campaign typeAccepted values: Onsite, Offsite, OffsiteAwarenessWriteable? N / Nullable? N |
privateMarketBillingType | enum | Billing type of the balance (for Private Market)Accepted values: notApplicable, billByRetailer, billByCriteoWriteable? N / Nullable? N |
Balance History Parameters
| Attribute | Data Type | Description |
|---|---|---|
dateOfModification | timestamp | Timestamp of balance updateAccepted values: yyyy-mm-ddThh:mm:ss±hh:mm (in ISO-8601)Writeable? N / Nullable? N |
modifiedByUser | string | Username who modified the insertion orderAccepted values: strings in format “j.doe” Writeable? N / Nullable? N |
changeType | enum | Definition of the type of change in a balanceAccepted values:
|
changeDetails | object | Structure with the change details (from Balance History endpoint)Parameters:
|
Get all Balances
This endpoint lists all balances in an account. The results are provided in a paginated format. Sample RequestCreate a Balance
This endpoint creates a new balance in the specified account. Sample RequestModify Balance metadata
This endpoint modifies the metadata of a specified balance, likename, poNumber, startDate or endDate.
To modify deposited funds, check the following endpoint /accounts/{accountId}/balances/{balanceId}/add-funds
Sample Request
Add or remove Balance funds
This endpoint allows to add or remove funds deposited in a specific balance Request Body Parameters
*Required
Sample Request
Get all Campaigns on a specific Balance
This endpoint lists all campaigns on the specified balance. The results are provided in a paginated format. Response Body Parameters
Sample Request
Add Campaigns to a specific Balance
This endpoint adds one or more campaigns to the specified balance. The results are provided in a single page. In this example, a campaign had already existed on the balance before two new additions. Request Body Parameters
Sample Request
Remove Campaigns from a specific Balance
This endpoint removes one or more campaigns from the specified balance. The resulting state of the balance is returned as a single page. Request Body Parameters
Sample Request
Get Balance History
This endpoint lists all changes made to a specific balance. The results are provided in a paginated format (using query parametersoffset and limit) and can be filtered by a comma-separated list of changeType values.
Modified Users
modifiedByUser - When a balance is updated via Criteo’s Retail Media UI, the user login name will be provided. For instance, if “Kip Heaney” updated the balance on 2023-11-07, it indicates that Kip made the change through the Criteo Retail Media UI.If a balance is updated through the Criteo API, the name of the API application responsible for the change will be shown. For example, on 2024-03-20, the balance was updated by the API application Retail Media API Application.