> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tetherai.ca/llms.txt
> Use this file to discover all available pages before exploring further.

# Execute custom fields across contact, conversations and applications (disabled)

> Disabled. The companion `/execute-custom-fields` route is what callers should use; this aggregate variant is commented out in the API router to avoid double-running with hook-driven rule execution. Documented as `deprecated` + `410 Gone` until it is re-enabled. See `ExecuteAllCustomFieldsResponse` for the shape it would return when restored.



## OpenAPI

````yaml /api-reference/openapi.yaml post /api/contacts/{id}/execute-custom-fields/all
openapi: 3.0.3
info:
  title: Tether Relay and Tether API
  version: 1.0.0
  description: >-
    Route-derived OpenAPI contract generated from tether-relay backend sources.
    Regenerate with scripts/sync-openapi-from-backend.mjs.
servers:
  - url: https://your-instance.example.com
    description: Production
  - url: http://localhost:2212
    description: Local API service
security: []
tags:
  - name: AI
  - name: Applications
  - name: Approval
  - name: Auth
  - name: Automations
  - name: Calls
  - name: Campaigns
  - name: Contact Analytics
  - name: Contact Metrics
  - name: Contact Notes
  - name: Contacts
  - name: Conversation Monitor
  - name: Conversations
  - name: Departments
  - name: Email
  - name: Escalation Dashboard
  - name: Event Logs
  - name: Google Sheets
  - name: Marketplace
  - name: Messages
  - name: Notification Sounds
  - name: Notifications
  - name: Org Snapshots
  - name: Organizations
  - name: Outreach
  - name: Outreach Metrics
  - name: Outreach Sources
  - name: Pipelines
  - name: Processes
  - name: Prompts
  - name: Reminders
  - name: Sms
  - name: Templates
  - name: Traces
  - name: Training
  - name: Upload
  - name: User Snapshots
  - name: Users
  - name: Vertical
  - name: Webchats
  - name: Webhook
paths:
  /api/contacts/{id}/execute-custom-fields/all:
    post:
      tags:
        - Contacts
      summary: >-
        Execute custom fields across contact, conversations and applications
        (disabled)
      description: >-
        Disabled. The companion `/execute-custom-fields` route is what callers
        should use; this aggregate variant is commented out in the API router to
        avoid double-running with hook-driven rule execution. Documented as
        `deprecated` + `410 Gone` until it is re-enabled. See
        `ExecuteAllCustomFieldsResponse` for the shape it would return when
        restored.
      operationId: post_contact_execute_custom_fields_all
      parameters:
        - in: path
          name: id
          required: true
          schema:
            type: string
      responses:
        '410':
          description: Endpoint is currently disabled
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/LegacyErrorResponse'
      deprecated: true
      security:
        - bearerAuth: []
components:
  schemas:
    LegacyErrorResponse:
      type: object
      properties:
        error:
          type: string
        message:
          type: string
        data: {}
      additionalProperties: true
      example:
        error: Attachment not found
        message: Attachment not found
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````