---
title: "/2026-01/advertisers/me"
method: GET
path: "/2026-01/advertisers/me"
tags: ["Advertiser"]
---

# /2026-01/advertisers/me

`GET /2026-01/advertisers/me`

Fetch the portfolio of Advertisers for this account

## Response `200`

Success

- GetPortfolioResponse — Portfolio fetch Response
  - `data` EntityOfPortfolioMessage[], nullable — The response�s primary data
    - `attributes` PortfolioMessage, nullable — Class with elementary info about advertiser
      - `advertiserName` string, nullable
    - `id` string, nullable — A opaque string containing the unique Id of the entity
    - `meta` object, nullable — A meta object that contains application-specific metadata
    - `type` 'campaign' | 'adset' | 'ad' | 'advertiser' | 'agency' | 'publisher' | 'address' | 'client' | 'contact' | 'industry', nullable — A string containing the entity type
  - `errors` CriteoApiError[], nullable — Error list returned by the Criteo API For successful requests it is empty
    - `code` 'internal-error' | 'deprecated-field' | 'endpoint-deprecated' | 'required-field' | 'invalid-date-format' | 'invalid' | 'invalid-ranged' | 'invalid-timespan', nullable — A machine-readable error code string in kabab-case. Unique across Criteo
    - `detail` string, nullable — A human-readable explanation specific to this occurrence of the problem.
    - `instance` string, nullable — A URI reference that identifies the specific occurrence of the problem
    - `source` object, nullable — A machine-readable structure to reference to the exact location(s) causing the error(s).
    - `title` string, nullable — A short, human-readable remarks of the problem type.
    - `traceId` string, nullable — The correlation ID provided by the gateway
    - `type` 'access_control' | 'authentication' | 'authorization' | 'availability' | 'deprecation' | 'quota' | 'validation', nullable — A machine-readable code specifying error category
  - `warnings` CriteoApiWarning[], nullable — 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.
    - `code` 'internal-error' | 'deprecated-field' | 'endpoint-deprecated' | 'required-field' | 'invalid-date-format' | 'invalid' | 'invalid-ranged' | 'invalid-timespan', nullable — A machine-readable error code string in kabab-case. Unique across Criteo
    - `detail` string, nullable — A human-readable explanation specific to this occurrence of the problem.
    - `instance` string, nullable — A URI reference that identifies the specific occurrence of the problem
    - `title` string, nullable — A short, human-readable remarks of the problem type.
    - `traceId` string, nullable — The correlation ID provided by the gateway
    - `type` 'access_control' | 'authentication' | 'authorization' | 'availability' | 'deprecation' | 'quota' | 'validation', nullable — A machine-readable code specifying error category

---

[API](https://skmtc.net/criteo/apis/criteo-api.md) · [All operations](https://skmtc.net/criteo/apis/criteo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/criteo/criteo-api/revisions/c1721589426a/schema)