# Customer KYC updated

Fires when any KYC requirement changes status (approved, rejected, or
pending correction). Includes the full kyc array with the updated status of
each item. Use it to identify rejected documents and request resubmission from the customer
via PATCH /customers/{id} or POST /customers/{id}/documents.

Endpoint: POST customer.kyc_updated
Version: 2026-03-01
Security: bearerAuth

## Request fields (application/json):

  - `type` (string, required)
    Event type identifier
    Enum: "customer.kyc_updated"

  - `timestamp` (string, required)
    When the event occurred

  - `data` (object, required)

  - `data.id` (string, required)

  - `data.status` (string, required)
    Enum: "pending_kyc", "under_review", "active"

  - `data.external_id` (string,null, required)

  - `data.kyc` (array, required)
    Full current state of all KYC requirements

  - `data.kyc.kind` (string, required)
    document for document submissions, data for data field corrections
    Enum: "document", "data"

  - `data.kyc.type` (string, required)
    Document type key (e.g., ccmei, selfie, identity_card_front)
    Example: "ccmei"

  - `data.kyc.description` (string, required)
    Human-readable label
    Example: "Certificado MEI"

  - `data.kyc.message` (string,null, required)
    Present when rejected — from the review feedback

  - `data.kyc.uploaded_at` (string,null, required)


## Response 200 fields