Sally API
Everything Sally captures about a meeting is available through the Sally Public API: the recording and its transcript, the AI summary broken into the sections of your meeting template, the tasks that came out of the conversation, and the people who were there.
This page shows what you can build with it, what every request looks like and which page to read next. If you already have a token, the Quickstart gets you to a first summary in four calls.
Quick navigation
1. What you can build
- Summaries where the work happens. Pull every new summary into your CRM, wiki or ticket system, so nobody has to open Sally to find out what was decided.
- A reaction the moment a meeting is done. A webhook fires when a summary is ready, and your system starts whatever should follow.
- Recordings from other systems. Hand Sally an audio or video file and get the transcript and the summary back.
- Tasks in your own tool. Keep the action items Sally found in sync with the task system your team already uses.
2. What a request looks like
The base URL is https://api.sally.io and every path starts with the version prefix /v1.0. Requests and responses are JSON. Ids are lower-case UUIDs, field names are camelCase, and a field that can be empty comes back as null instead of disappearing.
Almost everything belongs to a directory, the Sally company account that owns the data: /v1.0/directories/{directoryId}/…. That is why your first call usually asks which company accounts your token may address:
curl "https://api.sally.io/v1.0/me/directories/memberships" \
-H "Authorization: Bearer $SALLY_TOKEN"
Everything in this documentation refers to version 1.0. It is still under active development and not frozen yet, see Versioning.
3. Where to go next
Create a token and fetch the summary of a real meeting in four calls.
Personal access tokens, OAuth and what a token is allowed to see.
Step by step for summaries, transcripts, uploads, tasks, webhooks and folders.
How appointments, recordings and summaries relate, plus paging, fields, dates and errors.
Every endpoint with its parameters, fields and request samples.
What changed in the API, newest first, and what you have to do about it.