SalesOS

Meeting Briefings

AI-generated pre-meeting briefings

List all meeting briefings for the current user

GET
/v1/meeting-briefings

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

curl -X GET "https://api.salesos.org/v1/meeting-briefings" \
  -H "Authorization: Bearer <token>"

Get upcoming meetings with briefing status

GET
/v1/meeting-briefings/upcoming

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

curl -X GET "https://api.salesos.org/v1/meeting-briefings/upcoming" \
  -H "Authorization: Bearer <token>"

Get meeting briefing configuration for the current user

GET
/v1/meeting-briefings/config

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

curl -X GET "https://api.salesos.org/v1/meeting-briefings/config" \
  -H "Authorization: Bearer <token>"

Partially update meeting briefing configuration

PATCH
/v1/meeting-briefings/config

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

Header Parameters

Idempotency-Keystring

Unique key (a UUID is ideal) that makes this write safe to retry for 24 hours: a retry with the same body replays the original response (Idempotent-Replayed: true); the same key with a different body is a 409.

Maximum length: 255
curl -X PATCH "https://api.salesos.org/v1/meeting-briefings/config" \
  -H "Idempotency-Key: <string>" \
  -H "Authorization: Bearer <token>"

Update meeting briefing configuration

PUT
/v1/meeting-briefings/config

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

curl -X PUT "https://api.salesos.org/v1/meeting-briefings/config" \
  -H "Authorization: Bearer <token>"

Get AI-powered briefing for a meeting

Returns cached AI briefing if available, otherwise generates one on-demand. The briefing includes executive summary, talking points, risk flags, competitor intelligence, and suggested questions.

GET
/v1/meeting-briefings/{meetingId}

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

Path Parameters

meetingIdRequiredstring

The meeting activity ID

curl -X GET "https://api.salesos.org/v1/meeting-briefings/<string>" \
  -H "Authorization: Bearer <token>"

{}

Generate or regenerate an AI briefing for a meeting

Forces generation of a fresh AI briefing regardless of cache state. The briefing gathers CRM context (attendees, deal stage, account health, competitor intelligence, interaction history) and uses AI to produce actionable meeting intelligence.

POST
/v1/meeting-briefings/{meetingId}/generate

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

Path Parameters

meetingIdRequiredstring

The meeting activity ID

Header Parameters

Idempotency-Keystring

Unique key (a UUID is ideal) that makes this write safe to retry for 24 hours: a retry with the same body replays the original response (Idempotent-Replayed: true); the same key with a different body is a 409.

Maximum length: 255
curl -X POST "https://api.salesos.org/v1/meeting-briefings/<string>/generate" \
  -H "Idempotency-Key: <string>" \
  -H "Authorization: Bearer <token>"

Regenerate an AI briefing with fresh data

Clears the cached briefing and generates a completely fresh one using the latest CRM data.

POST
/v1/meeting-briefings/{meetingId}/regenerate

Authorization

AuthorizationRequiredBearer <token>

Session token from the SalesOS web app.

In: header

X-API-Key<token>

API key from Settings → API Keys. Authorization: ApiKey <key> is also accepted. Each operation lists the scope it needs under x-api-key-scopes.

In: header

Path Parameters

meetingIdRequiredstring

The meeting activity ID

Header Parameters

Idempotency-Keystring

Unique key (a UUID is ideal) that makes this write safe to retry for 24 hours: a retry with the same body replays the original response (Idempotent-Replayed: true); the same key with a different body is a 409.

Maximum length: 255
curl -X POST "https://api.salesos.org/v1/meeting-briefings/<string>/regenerate" \
  -H "Idempotency-Key: <string>" \
  -H "Authorization: Bearer <token>"