---
title: "List Customer Buyer Personas"
method: GET
path: "/copilot/v1/customer-buyer-personas"
tags: ["Customer Buyer Persona"]
---

# List Customer Buyer Personas

`GET /copilot/v1/customer-buyer-personas`

## Request

- Base URL: `https://api.zoominfo.com/gtm`
- URL: `https://api.zoominfo.com/gtm/copilot/v1/customer-buyer-personas`
- Auth: OAuth 2
  - Authorization code: `https://login.zoominfo.com`
  - Token URL: `https://okta-login.zoominfo.com/oauth2/default/v1/token` scopes: `api:gtm-config:read`

Returns the list of Customer Buyer Personas configured for the authenticated customer.

A Buyer Persona represents a profile of a key decision-maker or influencer that a company's sales and marketing teams target.
Personas capture attributes such as the buyer's role, objectives, priorities, and the motivations that influence purchasing decisions.
Personas help organizations align their go-to-market strategy by defining who the ideal buyers are, what problems they care about, and how they should be engaged.
Buyer Personas can be connected to products or services with the people most likely to purchase them.

If you do not know the ID of the record you need, call
[List Customer Buyer Personas](ref:customerbuyerpersonainterface_listcustomerbuyerpersonas) to browse the full set.

Common use cases
- Retrieve all configured buyer personas
- Discover persona IDs for use in other API operations
- Load persona data for downstream integrations or automation

## Response `200`

Success

- CustomerBuyerPersonaListResponse: API model for a list of customer buyer personas.
  - `data` CustomerBuyerPersona[], required: The primary data of the document
    - `id` string, required: The unique identifier for the resource
    - `type` string, required: The type of the resource
    - `attributes` CustomerBuyerPersonaAttributes, required: Attributes that define a customer buyer persona — a profile representing a type of buyer that the customer's sales team targets. Buyer personas capture who the ideal buyers are, what motivates them, and how to engage them effectively.
      - `name` string: Name of the buyer persona. Required when creating a new record. When provided (for create or update), must be between 1 and 1024 characters.
      - `description` string: Detailed description of this buyer persona, including their role, responsibilities, and relevance to the sales process. Maximum 10,000 characters.
      - `personalObjectives` string: Personal objectives for this persona such as career goals, KPIs, and success metrics that drive their purchasing decisions. Maximum 10,000 characters.
      - `whatDoesThisPersonaCareAbout` string: Messaging angle explaining what this persona cares about in the customer's offering. Maximum 10,000 characters.
      - `titlesFunctionsSeniority` string: Typical job titles, functional areas, and seniority levels associated with this persona. Maximum 10,000 characters.
      - `relevantOfferings` string: Relevant offerings from the customer's portfolio that this persona would be interested in. Maximum 10,000 characters.
      - `source` 'manual' | 'import' | 'system' | 'mcp': Source type indicating how a GTM configuration record was created or last modified. Used across all customer-level entities for audit provenance tracking. When source is explicitly set in a request, the corresponding created_by/updated_by must also be provided. Defaults to 'manual' when not specified.
      - `customFields` CustomFieldItem[]: Flexible key-value store for customer-specific custom fields and extended metadata. The backend validates schema and value types. Use this to capture additional persona attributes beyond the standard fields.
        - `title` string, required: The display title of the custom field.
        - `description` string: An optional description of the field. Defaults to an empty string in the backend.
        - `value` string, required: The string value associated with this custom field.
    - `meta` GtmConfigAuditFields: Common audit fields present on all customer-level GTM configuration entities. These fields track the full lifecycle of a record including creation, modification, archival (temporary hiding), and soft deletion (permanent hiding for compliance). A record can be active, deleted only, or both.
      - `createdAt` string, date-time: ISO 8601 timestamp when the record was originally created. Auto-populated by backend.
      - `updatedAt` string, date-time: ISO 8601 timestamp of the most recent modification to the record. Auto-populated by backend.
      - `createdBy` string: User ID of the person who created the record. Extracted from the JWT token on creation.
      - `updatedBy` string: User ID of the person who last modified the record. Extracted from the JWT token on update.
      - `archivedAt` string, date-time: ISO 8601 timestamp when the record was archived. Archived records are identified by archivedAt and archivedBy
      - `archivedBy` string: User ID of the person who archived the record

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `429`: Too Many Requests

---

[API](https://skmtc.dev/zoominfo/apis/copilot-api-v1.md) - [All operations](https://skmtc.dev/zoominfo/apis/copilot-api-v1/llms.txt) - [OpenAPI document](https://skmtc.dev/zoominfo/apis/copilot-api-v1/revisions/f737ab239c2a?raw)