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

# Block a contact

> Blocks a contact from receiving SMS.

The contact **must have a valid mobile number** — otherwise the request fails with `"We cannot locate a valid mobile for this contact"`.

Blocking also sets `unsubscribed_sms` to `true` on the contact and adds the blocked tag.

Requires the **`contacts`** permission on the service account that owns your API key. A key whose service account lacks it fails with `"Lacking necessary permission contacts"`.



## OpenAPI

````yaml /api-reference/specs/contacts.json post /api/contacts/block
openapi: 3.1.0
info:
  title: ConveYour API — Contacts
  description: >-
    Contacts are the core data object in ConveYour. Every person in your system
    — a learner, rep, or prospect — is a contact.
  version: 1.0.0
servers:
  - url: https://{subdomain}.conveyour.com
    description: Your organization's ConveYour instance
    variables:
      subdomain:
        default: acme
        description: >-
          Your organization's slug — the subdomain you sign in on. Replace
          `acme` with yours: if you sign in at `bigco.conveyour.com`, enter
          `bigco`.
security:
  - conveyourToken: []
tags:
  - name: Contacts
    description: >-
      Contacts are the core data object in ConveYour. Every person in your
      system — a learner, rep, or prospect — is a contact.
paths:
  /api/contacts/block:
    post:
      tags:
        - Contacts
      summary: Block a contact
      description: >-
        Blocks a contact from receiving SMS.


        The contact **must have a valid mobile number** — otherwise the request
        fails with `"We cannot locate a valid mobile for this contact"`.


        Blocking also sets `unsubscribed_sms` to `true` on the contact and adds
        the blocked tag.


        Requires the **`contacts`** permission on the service account that owns
        your API key. A key whose service account lacks it fails with `"Lacking
        necessary permission contacts"`.
      operationId: blockContact
      parameters:
        - $ref: '#/components/parameters/teams'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - contact_id
              properties:
                contact_id:
                  type: string
                  description: The contact to block.
            example:
              contact_id: 64a1b2c3d4e5f6a7b8c9d0e1
      responses:
        '200':
          description: The contact was blocked.
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/Envelope'
                  - type: object
                    properties:
                      data:
                        $ref: '#/components/schemas/BlockedNumber'
              example:
                status: ok
                message: Contact blocked
                data:
                  contact_id: 64a1b2c3d4e5f6a7b8c9d0e1
                  org_id: '1234'
        '403':
          $ref: '#/components/responses/Forbidden'
components:
  parameters:
    teams:
      name: teams[]
      in: query
      description: >-
        Team scope for the request, as one or more team ObjectIds. The brackets
        are required: PHP keeps only the last value for a repeated plain key, so
        `teams=A&teams=B` silently resolves to B alone. On requests with a JSON
        body you may send `teams` (no brackets) in the body instead.


        **Values that are not valid ObjectIds are silently ignored** — a
        mistyped team ID behaves as if no team was sent. See the [teams section
        of the API conventions guide](/guides/api-conventions#team-scoping).
      style: form
      explode: true
      schema:
        type: array
        items:
          type: string
      example:
        - 64a1b2c3d4e5f6a7b8c9d0ff
  schemas:
    Envelope:
      type: object
      description: The common response envelope shared by all ConveYour endpoints.
      properties:
        status:
          type: string
          enum:
            - ok
            - failed
          description: '`ok` on success, `failed` on error.'
        message:
          type: string
          description: Human-readable description of the result.
        data:
          description: >-
            The response payload — an object or an array depending on the
            endpoint.
    BlockedNumber:
      type: object
      description: >-
        The block record created for the mobile number, with the contact id
        attached. It is not a contact record.
      properties:
        contact_id:
          type: string
          description: ID of the contact that was blocked.
      additionalProperties:
        description: Remaining keys come from the block record.
  responses:
    Forbidden:
      description: >-
        The token is missing or invalid, or the service account behind it lacks
        the permission this endpoint requires.
      content:
        application/json:
          example:
            status: failed
            message: Lacking necessary permission add_contacts
            data:
              permission: add_contacts
  securitySchemes:
    conveyourToken:
      type: apiKey
      in: header
      name: x-conveyour-token
      description: >-
        Your API key token. Contacts endpoints require a **Server-only — Full
        API** key — see [Authentication](/quickstart).

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.