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

# Report contact

> Reports a contact to WhatsApp and, optionally, blocks it (report_contact). Response in data: { report: { status, report_id?, error? }, block?: { status, blocklist?, error? } }. success=true in the envelope means the bridge handled the request — not that both sub-steps succeeded. report.status='ok' with an empty report_id is a legitimate server-side discard (synthetic evidence) and is not an error. block is evaluated independently of report: it can fail (LID resolution miss) even when report is ok. Errors that fail the envelope (success=false): session not connected, invalid JID, empty recipient, warmup/rate-limit.



## OpenAPI

````yaml /api-reference/openapi.en.json post /api/v1/contacts/report
openapi: 3.1.0
info:
  title: D-API - Complete WhatsApp Infrastructure
  description: >-
    A scalable, robust solution for automation managers, SaaS products and end
    users who need a reliable WhatsApp integration. It offers multiple
    simultaneous instances, real-time webhooks, an intuitive dashboard and a
    documented REST API with 99.9% uptime and latency under 30ms.
  version: 1.2.1
  contact:
    name: Suporte D-API
    email: suporte@d-api.cloud
    url: https://d-api.cloud
servers:
  - url: https://api.d-api.cloud
    description: Production
security:
  - ApiKeyAuth: []
tags:
  - name: Home
    description: Base endpoints
  - name: Sessions
    description: Endpoints for managing sessions
  - name: Messages
    description: Endpoints for sending messages
  - name: Cloud API
    description: >-
      WhatsApp Official API (Meta Cloud API): manual connection, template
      management (list/create/delete) and template sending.
  - name: IVR Calls
    description: 'Voice call dispatch (IVR): single or bulk, with audio or an IVR flow.'
  - name: SMS
    description: 'SMS sending: single or bulk.'
  - name: Commands
    description: >-
      Look up asynchronous commands (async: true) by the commandId returned when
      enqueued.
paths:
  /api/v1/contacts/report:
    post:
      tags:
        - Contacts
      summary: Report contact
      description: >-
        Reports a contact to WhatsApp and, optionally, blocks it
        (report_contact). Response in data: { report: { status, report_id?,
        error? }, block?: { status, blocklist?, error? } }. success=true in the
        envelope means the bridge handled the request — not that both sub-steps
        succeeded. report.status='ok' with an empty report_id is a legitimate
        server-side discard (synthetic evidence) and is not an error. block is
        evaluated independently of report: it can fail (LID resolution miss)
        even when report is ok. Errors that fail the envelope (success=false):
        session not connected, invalid JID, empty recipient, warmup/rate-limit.
      operationId: postApiV1ContactsReport
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                sessionId:
                  minLength: 1
                  type: string
                phone:
                  minLength: 1
                  type: string
                identifier:
                  minLength: 1
                  type: string
                block:
                  type: boolean
                async:
                  anyOf:
                    - type: boolean
                    - type: string
              required:
                - sessionId
          multipart/form-data:
            schema:
              type: object
              properties:
                sessionId:
                  minLength: 1
                  type: string
                phone:
                  minLength: 1
                  type: string
                identifier:
                  minLength: 1
                  type: string
                block:
                  type: boolean
                async:
                  anyOf:
                    - type: boolean
                    - type: string
              required:
                - sessionId
          text/plain:
            schema:
              type: object
              properties:
                sessionId:
                  minLength: 1
                  type: string
                phone:
                  minLength: 1
                  type: string
                identifier:
                  minLength: 1
                  type: string
                block:
                  type: boolean
                async:
                  anyOf:
                    - type: boolean
                    - type: string
              required:
                - sessionId
      responses:
        '200':
          description: Successful response
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: 'API Key for authentication. Format: <API_KEY>'

````

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