Skip to main content
GET
/
2025-10
/
advertisers
/
me
/2025-10/advertisers/me
curl --request GET \
  --url https://api.criteo.com/2025-10/advertisers/me \
  --header 'Authorization: Bearer <token>'
{
  "data": [
    {
      "type": "advertiser",
      "id": "13",
      "attributes": {
        "advertiserName": "ClientName1"
      }
    },
    {
      "type": "advertiser",
      "id": "1352",
      "attributes": {
        "advertiserName": "ClientName2"
      }
    },
    {
      "type": "advertiser",
      "id": "73550",
      "attributes": {
        "advertiserName": "ClientName3"
      }
    }
  ],
  "errors": [],
  "warnings": []
}

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Response

200 - application/json

Success

Portfolio fetch Response

​
data
object[] | null

The response�s primary data

​
errors
object[] | null

Error list returned by the Criteo API For successful requests it is empty

​
warnings
object[] | null

Warnings list returned by the Criteo API In some situations the operations are successful but it may be useful to issue warnings to the API consumer. For example the endpoint, entity or field is deprecated. Warnings are like compiler warnings, they indicate that problems may occur in the future.