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

# Create a customer contact

> Creates a new contact for a customer.



## OpenAPI

````yaml https://api.salesbricks.com/api/v2/openapi.yaml post /customers/{customer_id}/persons
openapi: 3.0.3
info:
  title: Salesbricks REST API
  version: 2.0.0
  description: API reference for external integrations
servers:
  - url: https://api.salesbricks.com/api/v2
    description: Production
  - url: https://api.staging.salesbricks.com/api/v2
    description: Staging
security:
  - ApiKeyAuth: []
tags:
  - name: Subscriptions
    description: >-
      Operations related to subscription management, including creation,
      updates, and retrieving subscription details. Subscriptions can be
      upgraded to add / remove add-ons by using the POST
      /subscriptions/{subscription_id}/upgrade endpoint and can be recasted for
      replacing the current agreement using the POST
      /subscriptions/{subscription_id}/recast endpoint
  - name: Customers
    description: >-
      Operations related to customer management, including creation, updates,
      and managing customer person objects.
  - name: Invoices
    description: Operations related to subscription's invoicing details.
  - name: Plans
    description: >-
      Operations related to listing and getting plan details including bricks in
      the plan.
  - name: Payment Methods
    description: Operations related to subscription's payment method.
paths:
  /customers/{customer_id}/persons:
    post:
      tags:
        - Customer Contacts
      summary: Create a customer contact
      description: Creates a new contact for a customer.
      operationId: createCustomerContact
      parameters:
        - in: path
          name: customer_id
          schema:
            type: string
            pattern: ^([a-zA-Z\d\-]+)$
          required: true
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PersonInput'
          application/x-www-form-urlencoded:
            schema:
              $ref: '#/components/schemas/PersonInput'
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/PersonInput'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PersonOutput'
          description: ''
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                BadRequestResponse:
                  value:
                    error:
                      code: ERR_BAD_REQUEST
                      message: >-
                        Bad request — the input payload is malformed, missing
                        required fields, or contains invalid data.
                  summary: Bad Request Response
          description: ''
        '404':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                NotFoundResponse:
                  value:
                    error:
                      code: ERR_NOT_FOUND
                      message: >-
                        Not found — the resource you are looking for does not
                        exist.
                  summary: Not Found Response
          description: ''
components:
  schemas:
    PersonInput:
      type: object
      description: Person input serializer for creating a new person.
      properties:
        first_name:
          type: string
          description: The first name of the person
        last_name:
          type: string
          description: The last name of the person
        preferred_name:
          type: string
          description: Optional preferred name for the person
        email:
          type: string
          format: email
          description: The email of the person
        role:
          type: string
          description: The role of the person
      required:
        - email
        - first_name
        - last_name
        - role
    PersonOutput:
      type: object
      description: Person output serializer for creating a new person.
      properties:
        person_id:
          type: string
          format: uuid
          description: The ID of the person
        first_name:
          type: string
          description: The first name of the person
        last_name:
          type: string
          description: The last name of the person
        email:
          type: string
          format: email
          description: The email of the person
        preferred_name:
          type: string
          nullable: true
          maxLength: 255
        role:
          type: string
          readOnly: true
          description: The role of the person
      required:
        - email
        - first_name
        - last_name
        - person_id
        - role
    ErrorResponse:
      type: object
      description: >-
        Standardizes API error responses with a consistent structure containing
        error code and message.
      properties:
        error:
          $ref: '#/components/schemas/Error'
      required:
        - error
    Error:
      type: object
      description: >-
        Represents individual error details with a standardized code and
        descriptive message.
      properties:
        code:
          enum:
            - ERR_NOT_FOUND
            - ERR_BAD_REQUEST
            - ERR_SERVER_ERROR
          type: string
          x-spec-enum-id: dc5a5d6feae1b697
          description: >-
            Error code indicating the type of error: NOT_FOUND for missing
            resources, BAD_REQUEST for invalid input, SERVER_ERROR for internal
            server issues


            * `ERR_NOT_FOUND` - ERR_NOT_FOUND

            * `ERR_BAD_REQUEST` - ERR_BAD_REQUEST

            * `ERR_SERVER_ERROR` - ERR_SERVER_ERROR
        message:
          type: string
        error_id:
          type: string
          format: uuid
          description: >-
            Correlation handle for SERVER_ERROR responses — quote this when
            contacting support; it joins to the structured server log line for
            the failure. Not present on 4xx responses.
      required:
        - code
        - message
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-SALESBRICKS-KEY
      description: API key for authentication

````

## Related topics

- [One-Off Invoices](/documentation/one-off-invoices.md)
- [Role-based access control (RBAC)](/settings/team/rbac.md)
- [BrIQ AI Assistant](/documentation/briq.md)