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

# Create a contact group

> Customer API v1 endpoint.

Create a contact group. Authenticate with a Bearer access token unless the endpoint is the authentication token exchange.


## OpenAPI

````yaml POST /v1/contacts/group-create
openapi: 3.1.0
info:
  title: Amplify Customer API
  version: 1.0.0
  description: |-
    Canonical contract for the Amplify customer-facing API. This YAML file is
    the source of truth for Postman and Mintlify. Operations marked with
    x-amplify-validation-status: pending were migrated from the legacy Postman
    collection and must be validated before their contract is considered final.
servers:
  - url: https://api.amplify.xyz
    description: Production
  - url: https://dev-api.amplify.xyz
    description: Development
security: []
tags:
  - name: Authentication
  - name: Fax
  - name: Send Faxes
  - name: Receive Faxes
  - name: Manage Faxes
  - name: Workspace
  - name: Numbers
  - name: Contacts
  - name: Documents
  - name: Templates
paths:
  /v1/contacts/group-create:
    post:
      tags:
        - Contacts
      summary: Create a contact group
      description: Creates a group for organizing contacts in the authenticated workspace.
      operationId: postv1ContactsGroupCreate
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                name:
                  type: string
              required:
                - name
            example:
              name: My customers
      responses:
        '200':
          description: Contact group created.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StatusMessageResponse'
              example:
                status: 1
                message: Contact group created successfully
        '422':
          description: Required name was not supplied.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationMessageResponse'
              example:
                status: 0
                message: The name field is required.
      security:
        - bearerAuth: []
components:
  schemas:
    StatusMessageResponse:
      type: object
      required:
        - status
        - message
      properties:
        status:
          type: integer
          description: Operation result indicator.
        message:
          type: string
          description: Human-readable result message.
    ValidationMessageResponse:
      type: object
      required:
        - status
        - message
      properties:
        status:
          type: integer
          description: Indicates that the request was not accepted.
        message:
          type: string
          description: Human-readable validation message.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````