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

# Add a single contact to a contact list



## OpenAPI

````yaml post /v1/contact-lists/{contact_list_id}/contacts
openapi: 3.1.0
info:
  title: OpenMic v1 External API
  description: >-
    API specification for OpenMic v1 External API, providing endpoints for bot
    management, call handling, and phone number operations.
  version: 1.0.0
servers:
  - url: https://api.openmic.ai
    description: Production Environment
security:
  - api_key: []
tags:
  - name: Calls
    description: Endpoints related to phone call creation and management.
  - name: Bots
    description: Endpoints related to bot management and configuration.
  - name: Phone Numbers
    description: Endpoints related to phone number management and bot linking.
  - name: Knowledge Bases
  - name: FAQs
  - name: Campaigns
  - name: Tools
  - name: Contact Lists
  - name: Contacts
  - name: Voices
    description: >-
      Endpoints for browsing available text-to-speech voices. Voices are
      read-only and can be filtered by gender, provider, language, and accent.
  - name: SMS
    description: Endpoints for sending SMS messages.
paths:
  /v1/contact-lists/{contact_list_id}/contacts:
    post:
      tags:
        - Contacts
      summary: Add a single contact to a contact list
      operationId: addContact
      parameters:
        - name: contact_list_id
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateContactRequest'
      responses:
        '201':
          description: Contact created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ContactResponse'
        '400':
          description: Validation error
        '404':
          description: Contact list not found
components:
  schemas:
    CreateContactRequest:
      type: object
      required:
        - name
      properties:
        name:
          type: string
          maxLength: 255
          description: Contact's full name.
        phone_number:
          type: string
          description: Primary phone number (E.164 format recommended, e.g. +14155551234).
        phone_number_2:
          type: string
          description: Secondary phone number.
        phone_number_3:
          type: string
          description: Tertiary phone number.
        contact_info:
          type: object
          description: >-
            Arbitrary JSON metadata for the contact. Use this to store custom
            fields like email, address, company, or any key-value data your bot
            or campaign needs (e.g. `{"email": "john@example.com", "company":
            "Acme", "plan": "enterprise"}`).
    ContactResponse:
      type: object
      properties:
        id:
          type: integer
          description: Unique identifier.
        name:
          type: string
          description: Contact's name.
        phone_number:
          type: string
          description: Primary phone number.
        phone_number_2:
          type: string
          description: Secondary phone number.
        phone_number_3:
          type: string
          description: Tertiary phone number.
        contact_info:
          type: object
          description: Custom metadata JSON.
        contact_list_id:
          type: integer
          description: ID of the parent contact list.
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
  securitySchemes:
    api_key:
      type: http
      scheme: bearer
      bearerFormat: API Key
      description: >-
        API key authentication. Include your API key in the Authorization header
        as: `Authorization: Bearer <your-api-key>`

````