Skip to main content
POST
Create Persona
name, filters and mode are all required. The name must be unique within your team — a duplicate answers 409. Only the leads mode is accepted today; companies answers 400 with the code PEOPLE_DATABASE_PERSONA_MODE_NOT_SUPPORTED.Filters carry no type property — it is derived from filterId server-side. Use Get Database Filters to discover which filterId values you can use. Filters that require a plan your team does not have are dropped silently.
The response contains only the created id. The stored name and filters are sanitized and plan-gated server-side, so echoing the request payload back would misreport what was persisted — call List personas to read the stored persona.
This endpoint is in closed beta. It answers 403 with the code BETA_NOT_ENABLED unless the personas beta is enabled for your team.

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Body

application/json
name
string
required

Display name. Non-empty, and unique within your team.

Minimum string length: 1
Example:

"SaaS founders"

filters
object[]
required

People Database filters defining the persona

mode
enum<string>
required

Search mode the filters target. Only leads is accepted today.

Available options:
leads,
companies
Example:

"leads"

Response

Persona created

data
object