Docs / Guides

Recordings

Phound keeps the calls and meetings you record. The Recordings API lists and searches them, hands you their audio, video and transcripts, and lets you rename, tag, protect, delete and restore them, move them to Dropbox, and publish them as a podcast feed.

See yours first

The dashboard's Recordings page is built on the same API: everything below, with your own recordings.

Scopes

ScopeGrants
recordings:readListing recordings and their files, tags, storage use and the podcast feed.
recordings:writeRenaming, tagging and password-protecting recordings, deleting and restoring them, moving them to Dropbox, and publishing the podcast feed. Never implied: give it to a key only if it needs it.

List recordings

Recordings made by you and by your own personas — not ones other Phound users share with you, whose recordings are theirs. Newest first:

curl "https://api.phound.app/recordings/v1/recordings?limit=10" \
  -H "Authorization: Bearer $PHOUND_KEY"
Parameter
searchName contains this, ignoring case.
tagHas this tag. Repeat it for recordings with all of several.
statusactive (the default), or removed for the bin.
order_by, ordercreated, started, name, duration or size; asc or desc.
limit, cursorUp to 100 a page. Pass next_cursor back as cursor for the next one, while has_more is true.

A recording

{
  "id": "9f447cfb-7eb0-4289-9225-6c42242795a4",
  "object": "recording",
  "name": "Weekly sync",
  "summary": "Planning for the spring release…",
  "status": "active",
  "persona_id": "1f39a86f-3b0b-8bf3-9a2b-5e90c4f4740c",
  "meeting_id": "698e2f33000007bd",
  "started_at": "2026-02-12T19:53:26Z",
  "duration": 28,
  "size": 3149700,
  "tags": ["team"],
  "password": null,
  "in_dropbox": false,
  "media": ["audio", "video"],
  "conversion_status": "Completed",
  "transcript_status": "Completed",
  "created_at": "2026-02-12T19:54:14Z",
  "files": [
    { "id": "…", "object": "recording_file", "type": "recording_audio",
      "url": "https://…cxstatic.com/f/…", "created_at": "2026-02-12T19:54:08Z" }
  ]
}
  • files are what you download: recording_audio, recording_video, recording_preview, transcripts and more. Fetch url directly, no key needed. New file types can appear; skip ones you don't use.
  • conversion_status and transcript_status say how far processing has got. Files appear as it finishes them.
  • persona_id is the persona that recorded it — null if that persona is gone.
  • A recording moved to Dropbox (in_dropbox: true) keeps its preview here; its audio and video are in your Dropbox.

Rename, describe and tag

PATCH /recordings/{id} changes only the fields you send. tags replaces the list; null clears summary or password.

curl -X PATCH https://api.phound.app/recordings/v1/recordings/9f447cfb-7eb0-4289-9225-6c42242795a4 \
  -H "Authorization: Bearer $PHOUND_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "Weekly sync", "tags": ["team", "planning"]}'

A password is asked for when someone opens the recording's share link. GET /recording-tags lists every tag you use.

The bin

DELETE /recordings/{id} moves a recording to the bin: it leaves the list, and status=removed lists it. POST /recordings/{id}/restore brings it back. Recordings in the bin still count against your storage — see GET /storage-quota, which covers everything your account stores.

Dropbox

With Dropbox connected in the Phound app, PUT /recordings/{id}/dropbox moves a recording's files there, and DELETE /recordings/{id}/dropbox brings them back. Without it, both answer 422 dropbox_not_connected.

Podcast feed

Publish your recordings as an RSS feed any podcast app can subscribe to:

curl -X PUT https://api.phound.app/recordings/v1/recordings-feed \
  -H "Authorization: Bearer $PHOUND_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tags": ["podcast"], "password": "listen"}'

The response's url is the feed. persona_ids and tags narrow what it carries — all your recordings if both are empty. PUT again to change it (the URL stays), and DELETE /recordings-feed to unpublish it.

Anyone with the URL can listen

Unless the feed has a password, treat its URL like a secret.