Two collections
A meeting recorded by the bot and a call captured from VoIP are different
resources, so they live at different paths: /v1/meetings and /v1/calls.
Same shape, own identifiers.
Two collections
A meeting recorded by the bot and a call captured from VoIP are different
resources, so they live at different paths: /v1/meetings and /v1/calls.
Same shape, own identifiers.
Scoped to one company
A credential belongs to a company, never to a user. Every read is filtered by that company — there is no parameter that widens it.
Stable identifiers
Resources are addressed by opaque, prefixed ids (mtg_, call_, usr_).
Internal sequential ids are never exposed.
Built for agents
Every page is available as plain Markdown, plus llms.txt and
llms-full.txt for tools that read documentation
directly.
Exchange your credential for an access token, then read a page of meetings.
# 1. Get an access token (valid for 1 hour)curl -X POST https://api.salesbud.com.br/oauth/token \ -d 'grant_type=client_credentials' \ -d "client_id=$SALESBUD_CLIENT_ID" \ -d "client_secret=$SALESBUD_CLIENT_SECRET"
# 2. Read completed meetings from a periodcurl "https://api.salesbud.com.br/v1/meetings?meeting_after=2026-01-01T00:00:00Z&limit=50" \ -H "Authorization: Bearer $SALESBUD_ACCESS_TOKEN"The response is a page of meetings plus a cursor:
{ "data": [ { "id": "mtg_H9_chV2YG6UGE0n31AqvDQ", "object": "meeting", "title": "Discovery — Acme", "status": "completed", "type": "video", "audience": "external", "meeting_at": "2026-01-14T13:00:00.000Z", "duration_seconds": 2840, "participants": [{ "email": "buyer@acme.com", "kind": "external" }], "owner": { "id": "usr_CKAyHd20jJb6GGJqhNF9vA", "email": "rep@yourcompany.com" }, "transcript": { "available": true, "status": "completed" } } ], "pagination": { "limit": 50, "has_more": true, "next_cursor": "cur_..." }}| If you want to… | Read |
|---|---|
| Make your first call end to end | Quickstart |
| Understand credentials, tokens and scopes | Authentication |
Know when a record is a meeting and when it is a call | Meetings and calls |
| Walk a full history safely | Pagination |
| Handle failures correctly | Errors |
| See every endpoint, field and status | API reference |