Skip to main content
The App API is for organizations that use the Parlay app. Use it to pipe your calls, transcripts, scores and coaching into your own data warehouse, CRM or internal tools. It needs no browser sign-in after setup: an organization owner or admin creates a key once, and your server uses it from then on.

Get your API key

Sign in to Parlay with your normal account and open Settings → API Keys. Organization owners and admins can create keys.

Quickstart

Create a key and pull your first calls in five minutes.

Sync calls daily

The recommended pattern for keeping your database current.

Connect an AI assistant

Ask Claude, ChatGPT or Cursor about your calls with the Parlay MCP server.

API reference

Every endpoint, field and error, with try-it panels.

See it in 30 seconds

What you can read

Calls

Every completed call with scores, summary, action plan and pillar feedback.

Transcripts

Full text, timed segments and keyword search.

Reps and teams

Your roster, teams and team members.

Analytics

Overview, leaderboard, trends, pillars, outcomes and daily activity.

Deals and CRM

Call outcomes, deals, accounts, contacts and pipeline stages.

Playbook and training

Playbook versions, scorecard, courses, enrollments and certificates.

Coming next

The API is read-only today. Signed webhooks, bulk export jobs and a small set of writes (call outcomes, comments, playlists, training assignments) are on the way. Until then, the change feed tells you exactly what is new or changed.

How access works

1

An owner or admin creates a key

In the Parlay web app, go to Settings → API Keys. You sign in with your normal Parlay account, so there is no separate developer account. Pick a name, the permissions it needs and how long it lasts. The key is shown once.
2

Your server sends it on every request

Authorization: Bearer pk_org_live_…. Keys belong to the organization, not a browser session, so nothing expires when someone signs out.
3

Parlay checks it on every read

Each request is checked against the key’s organization and permissions at the moment the data is read. A revoked key stops working on its next request.

Base URL

Every response includes an X-Request-Id header and a Parlay-Version header. Include the request id when you contact support.