Skip to main content
Version: 1.0

Audiences API

The Audiences API returns the audience profiles configured for the caller's company. Audiences are used by AutoGenerator and other generation endpoints to tailor content tone, depth, and structure.

Full schemas and try-it-out forms live in the interactive API Reference.

Authentication​

All endpoints require a Bearer token:

Authorization: Bearer YOUR_API_KEY

See Getting Started → Authentication.

Response envelope​

Every endpoint returns the canonical envelope: { "success": true, "data": { ... } } on success or the standard error envelope on error.

Endpoint summary​

MethodPathDescriptionSync/Async
GET/api/v1/audiencesList audience profilesSync
POST/api/v1/audiences/searchSearch audience profilesSync

All endpoints are in the auto_generator rate-limit category. See Developer Guide → Usage quotas and rate limits.


GET /api/v1/audiences — List audiences​

Returns the audiences configured for the caller's company. Supports opt-in cursor pagination — omit limit/cursor to receive the full list unchanged. See Developer Guide → Pagination.

Query parameters​

ParameterTypeRequiredDescription
featurestringnoFilter by feature scope.
idstringnoFilter to a single audience by id.
sortstringnoSort expression (for example name:asc).
limitintegernoItems per page (1–200, default 50). Enables pagination.
cursorstringnoOpaque cursor from the previous response's next_cursor.

Example​

curl "https://api.prezent.ai/api/v1/audiences?sort=name:asc" \
-H "Authorization: Bearer $PREZENT_API_KEY"

Success response (200)​

{
"success": true,
"data": {
"items": [
{ "id": "aud_exec", "name": "Executives" },
{ "id": "aud_sales", "name": "Sales team" }
],
"next_cursor": null
}
}

next_cursor is null on the last page (or when pagination was not requested). Pass it back as the cursor query parameter to fetch the next page.


POST /api/v1/audiences/search — Search audiences​

Free-text and field-filtered search across audience profiles.

Query parameters​

ParameterTypeRequiredDescription
featurestringnoFilter by feature scope.

Request body​

FieldTypeRequiredDescription
querystringnoFree-text search query.
idstringnoFilter to a single audience by id.
sortstringnoSort expression.
filterByobjectnoField-level filter.
filterByCollectionobjectnoCollection-level filter.
fieldsarray of stringnoSubset of fields to return.
extraFieldsarray of stringnoAdditional fields to include beyond defaults.
limitintegernoMaximum number of results (default 15).

Example​

curl -X POST https://api.prezent.ai/api/v1/audiences/search \
-H "Authorization: Bearer $PREZENT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "query": "executive", "limit": 10 }'

Success response (200)​

Search returns the top matches (capped by limit, most relevant first). It is a single ranked result set — there is no cursor to follow.

{
"success": true,
"data": {
"items": [
{ "id": "aud_exec", "name": "Executives" }
]
}
}

Errors​

Common error codes:

  • 400 — INVALID_INPUT.
  • 401 — INVALID_API_KEY, EXPIRED_API_KEY, UNAUTHORIZED.
  • 404 — ENDPOINT_NOT_FOUND.
  • 429 — RATE_LIMIT_EXCEEDED, TOO_MANY_REQUESTS.
  • 500 / 503 / 504 — standard server-side codes.

See the full catalog in Developer Guide → Error codes.