Skip to main content
The BuildBetter GraphQL API is being deprecated for customer integrations. Use the REST API for new work and migrate existing GraphQL integrations to REST.
GraphQL examples on this page are legacy migration reference. Move recording and transcript reads to the Recordings API.

Authentication

Legacy GraphQL queries require authentication. Include your API key in the request header:

Endpoint

Query Examples

Fetch a list of recent calls with participants
Use cases:
  • Building dashboards with recent activity
  • Displaying call history
  • Getting participant lists for follow-ups
Retrieve signals (key moments) from a specific call
Variables:
Use cases:
  • Creating call analysis dashboards
  • Extracting key insights
  • Building signal-based reports
Retrieve the full transcript for a call
The GraphQL API is being deprecated for customer integrations, and GraphQL interview.monologues is deprecated as of Wednesday, July 1, 2026. Move transcript reads to the REST transcript endpoint. During migration, use sentence-backed transcript relationships such as sentences or transcript_segments.
Use cases:
  • Building transcript viewers
  • Creating searchable interfaces
  • Generating custom summaries
Retrieve AI-generated documents with source calls
Use cases:
  • Displaying AI summaries
  • Showing document history
  • Tracking document status
Search for calls by various criteria
Use cases:
  • Implementing search functionality
  • Building filtered call lists
  • Creating date-based reports
Retrieve people/contacts from your workspace
Use cases:
  • Building contact directories
  • Tracking participant history
  • Managing customer relationships

Pagination

For large result sets, use pagination with limit and offset:

Filtering

Use the where clause to filter results:

Best Practices

  1. Request only needed fields - GraphQL returns only what you ask for
  2. Use variables - Makes queries reusable and secure
  3. Implement pagination - For large datasets
  4. Handle errors gracefully - Check for errors in responses
  5. Cache results - When appropriate for your use case