> ## 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. # Update a custom field > Changes a field's label or its dropdown choices. The key never moves, so nothing that reads `{{key}}` breaks. Removing a choice from a `select` does not rewrite contacts that already hold it; it stops being offered from here on. Cookie-auth callers must send the `x-csrf-token` header. Required API key scope: `contacts:write`. ## OpenAPI ````yaml /openapi.yaml patch /api/native-contacts/fields/{key} 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: Native Calendar description: >- The diary of a sub-account with no CRM: its bookable calendars, the free slots they offer, and the appointments on them. Availability is computed per request against live bookings and is never cached, because a cached slot is one somebody else has already taken. - name: Native Contacts description: >- The people a sub-account with no CRM calls, and the fields it keeps on them. This is the system of record for those contacts: there is nowhere else they exist. A sub-account with a CRM keeps its contacts there and every operation here answers 400 for it. - 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/native-contacts/fields/{key}: patch: tags: - Native Contacts summary: Update a custom field description: >- Changes a field's label or its dropdown choices. The key never moves, so nothing that reads `{{key}}` breaks. Removing a choice from a `select` does not rewrite contacts that already hold it; it stops being offered from here on. Cookie-auth callers must send the `x-csrf-token` header. Required API key scope: `contacts:write`. operationId: update-native-contact-field parameters: - name: key in: path required: true schema: type: string minLength: 1 description: The field key. example: service_needed - name: locationId in: query required: true schema: type: string description: >- The sub-account. It is the only thing that identifies the tenant on these routes, and it is re-checked against your access on every call. A sub-account that keeps its contacts in a CRM answers 400. example: nat_fd9e2a8dd4be4396b604 requestBody: required: true description: What to change. content: application/json: schema: $ref: '#/components/schemas/NativeContactFieldUpdateRequest' examples: default: value: label: Treatment wanted options: - Implants - Whitening - Check-up - Veneers responses: '200': description: The field as it now is. content: application/json: schema: $ref: '#/components/schemas/NativeContactFieldResponse' examples: default: value: success: true data: key: service_needed label: Treatment wanted type: select options: - Implants - Whitening - Check-up - Veneers '400': description: >- The request is malformed, or this sub-account keeps its contacts in a CRM. content: application/json: schema: $ref: '#/components/schemas/NativeContactsErrorResponse' examples: default: value: success: false error: A phone number is required. '401': description: Missing or invalid authentication. content: application/json: schema: $ref: '#/components/schemas/NativeContactsErrorResponse' examples: default: value: success: false error: Unauthorized '403': description: Authenticated, but without access to this sub-account. content: application/json: schema: $ref: '#/components/schemas/NativeContactsErrorResponse' examples: default: value: success: false error: You do not have access to this sub-account. '404': description: No contact with that id in this sub-account. content: application/json: schema: $ref: '#/components/schemas/NativeContactsErrorResponse' examples: default: value: success: false error: Contact not found. '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/NativeContactsErrorResponse' examples: default: value: success: false error: TooManyRequests '500': description: Unexpected server error. content: application/json: schema: $ref: '#/components/schemas/NativeContactsErrorResponse' examples: default: value: success: false error: Contacts request failed. security: - ApiKeyAuth: [] x-codeSamples: - lang: bash label: cURL source: |- curl --request PATCH \ --url https://api.teamfollowup.ai/api/native-contacts/fields/{key} \ --header 'Authorization: Bearer YOUR_API_KEY' \ --header 'Content-Type: application/json' \ --data '{ "label": "Treatment wanted", "options": [ "Implants", "Whitening", "Check-up", "Veneers" ] }' components: schemas: NativeContactFieldUpdateRequest: type: object additionalProperties: {} properties: label: type: string maxLength: 60 options: type: array items: type: string maxItems: 50 NativeContactFieldResponse: type: object additionalProperties: {} required: - success - data properties: success: type: boolean data: $ref: '#/components/schemas/NativeContactFieldDefinition' NativeContactsErrorResponse: type: object additionalProperties: {} required: - success - error properties: success: type: boolean error: type: string example: A phone number is required. errors: type: array description: Every reason the write was refused, when there is more than one. items: type: string failed: type: array description: >- On a refused delete: the bookings that would not cancel, which is why the contact is still here. items: type: object additionalProperties: {} cancelled: type: array description: >- On a refused delete: the bookings that HAD already been cancelled before it stopped. They do not come back. items: type: object additionalProperties: {} contactKept: type: boolean description: True when the contact is still here, whatever else failed. NativeContactFieldDefinition: type: object additionalProperties: {} required: - key - label - type properties: key: type: string description: >- Derived from the label once, and never changed. This is what `{{key}}` reads in a prompt. example: service_needed label: type: string maxLength: 60 example: Service needed type: type: string enum: - text - number - date - select example: select options: type: array items: type: string maxItems: 50 description: A `select`'s choices. Matching is case-insensitive. securitySchemes: ApiKeyAuth: type: http scheme: bearer bearerFormat: API key description: 'Send your API key as `Authorization: Bearer YOUR_API_KEY`.' ````