Transcripts require the separate transcripts:read scope. The scope is off by
default because raw conversation text can contain prospect PII and because
transcript reads have a separate organization quota.
Quota behavior
- 2,000 successful transcript reads per organization per UTC day
- Shared across all keys in the organization
- Charged only after Hobbes confirms the session belongs to the organization
- Resets at 00:00 UTC
- Returns
429 with Retry-After when exhausted
Malformed session ids and 404 responses do not consume quota.
Prefer derived fields
Session detail already includes summaries, qualification, topics, objections,
timeline milestones, and next steps. Use those fields for routing and analytics.
Fetch raw transcripts only when the integration needs the original conversation.
Security checklist
- Use a dedicated key with the minimum required scopes.
- Keep transcript processing server-side.
- Encrypt transcript data in transit and at rest.
- Apply the same access and retention rules used for call recordings and CRM notes.
- Avoid bulk transcript backfills unless the use case requires them.
- Never send transcripts to another processor without confirming your data policy.
The API reference shows copyable examples only. It intentionally does not
execute requests in the documentation browser or proxy API keys through the
docs provider.
