Skip to main content
Create a collection, attach your voice call transcriptions as a source, and search them with natural language. This quickstart uses the REST API — every step is a copy-paste request.

Prerequisites

  • A Telnyx API key from the portal. Export it so the examples work as-is:
  • Content to search. The voice source indexes your account’s persisted voice call transcriptions — see how to enable persistence. An account with no persisted transcriptions returns empty results, but the API calls below still work.
1

Create a Collection

A collection is a named search index. name is required; everything else has defaults.
Two identifiers come back: the uuid (used by the management API) and the slug, derived from name (used by the search API). Default settings apply — top_k: 5, retrieval_type: vector. The collection has no sources yet, so there is nothing to search.
2

Attach a Source

Add the voice source — your account’s call transcriptions:
The source is ready and its content is indexed for search. More source types are coming soon — see Sources.
3

Search It

Search is a GET on the collection’s documents, addressed by slug:
Each result is a scored chunk that says what it is and where it came from — record_id, record_type, timestamps, and metadata. The match works on meaning, not exact words: “did we promise a refund” finds “the refund has been deposited”.Per-request parameters override the collection defaults for that one request:
See Search for the full parameter and filter reference.
4

Ground Your LLM

The search response is grounding, ready to hand to any LLM as tool output — Search never generates answers itself. Declare the search call as a function tool, run it when the model asks, and feed the chunks back.

Next Steps

How Search Works

The indexing and query pipelines, and what a collection actually is.

Sources

Attach sources and enable the data behind them.

Settings

Configure retrieval mode and result count per collection.

Search

Filters, pagination, document reassembly, and errors.