> ## Documentation Index > Fetch the complete documentation index at: https://docs.teamfollowup.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the public API base URL: https://api.teamfollowup.ai/api. > Authenticate public API requests with Authorization: Bearer YOUR_API_KEY. > Use product-owned terms: agents, campaigns, projects (GoHighLevel sub-accounts), contacts, calls, outcomes, skills, cadences, phone numbers. > Scope requests by locationId rather than projectName. > Read the guide linked from each API reference group before recommending an endpoint. # Search for a voice to add > Search the speech provider's public voice library for a voice to add. Search by name, by description, or by pasting a provider voice id, which matches exactly. Reaches the provider on our credentials, so it needs a write scope even though it changes nothing. Pass a result's `providerVoiceId` to `POST /voices/library`. Required API key scope: `voices:write`. ## OpenAPI ````yaml /openapi.yaml post /api/agent-builder/voices/search openapi: 3.1.0 info: title: TFUAI Server API version: 1.0.0 description: >- API reference for the TFUAI SaaS server. All published endpoints are mounted under `/api`. Responses use a standard envelope: `{ "success": true, ... }` on success and `{ "success": false, "error": "..." }` on failure. Product API modules are being launched module by module. This spec currently exposes only contracted public modules. Authenticate public API requests with an API key in the `Authorization` header: `Authorization: Bearer YOUR_API_KEY`. servers: - url: https://api.teamfollowup.ai description: Production API origin. Public API paths are under /api. security: [] tags: - name: Agents description: Manage voice agents, campaigns, workflows, and outcomes. - name: Analytics description: >- Minimal, non-billing performance summary: volume, conversion, and pickup metrics. - name: Billing description: >- Billing for your own agency: balance, spend, transaction history, invoices and sub-account wallets; auto-recharge, rebilling, Credit Guard and Stripe customers; and, with the billing:charge scope, purchases and charges. - name: Calls description: Review calls, test runs, and execution history. - name: Campaign Workflows description: >- What runs after a call lands: for each outcome (booked, opted out, asked for a callback…), an ordered chain of actions — tag the contact, move a pipeline stage, send an SMS, book an appointment. Stored as a graph: `nodes` are the actions, `edges` say what follows what, and `dispositionEntries` maps each outcome to the node its chain starts at. **Pick the narrowest endpoint that does the job.** | To | Call | | | --- | --- | --- | | See what fires per outcome | `GET .../workflow/digest` | Reads as plain text, no graph walking | | Add steps to an outcome | `POST .../outcomes/{outcome}/nodes` | Server derives node ids, edge ids, handles, layout | | Change a message, tag or setting | `PATCH .../workflow` | Merges; carries no graph, so it cannot damage one | | Remove one step | `DELETE .../nodes/{nodeId}` | Also re-links the chain around it | | Author or replace the whole graph | `PUT .../workflow` | Replaces everything you send | `PUT` is the only one that can re-wire, position nodes, build an `if`, save an unconfigured draft, or copy a whole workflow — and the only one that can overwrite a change someone else made after you read it. Use it when you are genuinely authoring the graph, and send `expectedVersion` when you do. For everything else the narrower endpoints are both easier and safer. - name: Contacts description: Contact list, filters, contact call history, and do-not-call actions. - name: GHL description: CRM variables and contact helpers used by agent and campaign setup flows. - name: Phone Numbers description: >- Caller ID pool, number search, assignment, movement, and release endpoints. - name: Power Dialer description: >- Power Dialer queue, lead cadence, callback, parked lead, and campaign schedule endpoints. - name: Projects description: >- Project management endpoints: list, update, disconnect, configure project campaigns, and validate setup. - name: Skills and Tools description: Manage reusable agent behaviors and in-call tool descriptions. - name: Split Testing description: >- Split live campaign traffic across agent variants and shift the weights between them. - name: Voices description: Voice catalogue endpoints for choosing the voice used by an agent. paths: /api/agent-builder/voices/search: post: tags: - Voices summary: Search for a voice to add description: >- Search the speech provider's public voice library for a voice to add. Search by name, by description, or by pasting a provider voice id, which matches exactly. Reaches the provider on our credentials, so it needs a write scope even though it changes nothing. Pass a result's `providerVoiceId` to `POST /voices/library`. Required API key scope: `voices:write`. operationId: search-voices requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/VoicesSearchRequest' examples: default: value: query: warm british female responses: '200': description: Matching voices. content: application/json: schema: $ref: '#/components/schemas/VoicesSearchResponse' examples: default: value: success: true voices: - providerVoiceId: EXAVITQu4vr4xnSDxMaL name: Sarah description: Warm, conversational, British. '400': description: >- The request is malformed (`BadRequest`), or the library refused it (`VALIDATION`), for example because the voice is already in your library. content: application/json: schema: $ref: '#/components/schemas/VoicesErrorResponse' examples: validation: value: success: false error: VALIDATION message: That voice is already in your library. badRequest: value: success: false error: BadRequest message: voiceId required '401': description: Missing or invalid authentication. content: application/json: schema: $ref: '#/components/schemas/VoicesErrorResponse' examples: default: value: success: false error: Unauthorized message: Authentication required. '403': description: Authenticated but not permitted to use the voice endpoints. content: application/json: schema: $ref: '#/components/schemas/VoicesErrorResponse' examples: default: value: success: false error: Forbidden message: You do not have access to voice catalogue endpoints. '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/VoicesErrorResponse' examples: default: value: success: false error: TooManyRequests message: Too many requests, please try again later. '500': description: Unexpected server error. content: application/json: schema: $ref: '#/components/schemas/VoicesErrorResponse' examples: default: value: success: false error: InternalError message: Unexpected server error. security: - ApiKeyAuth: [] x-codeSamples: - lang: bash label: cURL source: |- curl --request POST \ --url https://api.teamfollowup.ai/api/agent-builder/voices/search \ --header 'Authorization: Bearer YOUR_API_KEY' \ --header 'Content-Type: application/json' \ --data '{ "query": "warm british female" }' components: schemas: VoicesSearchRequest: type: object additionalProperties: false required: - query properties: query: type: string minLength: 1 description: >- A voice name, a description, or a provider voice id. An id matches exactly; a name may return several. example: warm british female VoicesSearchResponse: type: object additionalProperties: false required: - success - voices properties: success: type: boolean voices: type: array items: $ref: '#/components/schemas/VoicesSearchHit' VoicesErrorResponse: type: object additionalProperties: {} required: - success - error - message properties: success: type: boolean error: type: string description: >- Machine-readable error code. The catalogue reads answer `BadRequest` and `NotFound`. The voice library answers `VALIDATION`, `NOT_FOUND`, `FORBIDDEN`, `VOICE_ALLOWANCE` (the plan's voice allowance is used up), `VOICE_CAPACITY` (new voices are temporarily unavailable) and `VOICE_ALREADY_SHARED` (the voice is already on the account; see `references`). example: NotFound message: type: string description: Human-readable explanation safe to show to an operator. example: Voice "custom_voice_missing" not found. references: type: object additionalProperties: false description: >- Sent only with `VOICE_ALREADY_SHARED`: what to use instead of adding. properties: voiceId: type: string description: >- The id of the voice already on the account. Select it on the agent rather than adding the voice again. example: custom_voice_9b1f2a7c4d3e5f6a8b0c1d2e3f VoicesSearchHit: type: object additionalProperties: false required: - providerVoiceId - name - description properties: providerVoiceId: type: string description: Send this to add the voice. example: EXAVITQu4vr4xnSDxMaL name: type: - string - 'null' example: Sarah description: type: - string - 'null' example: Warm, conversational, British. securitySchemes: ApiKeyAuth: type: http scheme: bearer bearerFormat: API key description: 'Send your API key as `Authorization: Bearer YOUR_API_KEY`.' ````