Skip to main content
POST
List Perplexity models

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.

Body

application/json
api_key
string<password>
required
write-only

Perplexity API key used for this lookup. Supply this or tool_id, not both.

Maximum string length: 512
tool_id
string<uuid>

Existing Perplexity connector whose securely stored key should be used. Supply this or api_key, not both.

Response

Models currently available to the Perplexity account.

data
object
required