> For the complete documentation index, see [llms.txt](https://detected.gitbook.io/detected-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://detected.gitbook.io/detected-docs/api-overview/webhooks/profile-webhook-spec/verify-events.md).

# Verify Events

Used for specific integrations that rely on realtime updates from KYC flows.

## Triggers

| **Trigger**              | **Description**                                                                             |
| ------------------------ | ------------------------------------------------------------------------------------------- |
| Verify flow is completed | This webhook fires whenever an individual completes their steps in the verification portal. |

### Webhook Payload

The payload of the webhook provides the following information in JSON format:

| Attribute                 | Description                                                                                                                                                                                               |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| event                     | Will always be event.completed                                                                                                                                                                            |
| profile\_reference        | the unique reference of the profile                                                                                                                                                                       |
| customer\_reference       | the unique customer assigned reference for the profile                                                                                                                                                    |
| representative\_id        | the unique reference for that representative in the platform                                                                                                                                              |
| completed\_at             | The date/time the verification was completed                                                                                                                                                              |
| flow\_id                  | The unique reference of the flow for this KYC Journey                                                                                                                                                     |
| users\_email              | The email address of the user who completed the verification                                                                                                                                              |
| verification\_information | The detailed information of the verifications performed by the user                                                                                                                                       |
| result                    | This will provide core information on the verifications that have been performed, see this API for more information:[Retrieves a list of verifications for a representative](docId:kFIBYsZkNZKRZKIps3bEF) |

```json
{
  "event": "verify.completed",
  "timestamp": "2026-06-19T15:18:30.430126Z",
  "data": {
    "representative_id": "a20fae1b-01c5-4fc6-b436-afd7964aeef9",
    "profile_reference": "536a8313-9e06-4b55-9237-c73fb1e81cb7",
    "customer_reference": "api-verify-individual-personal-and-form",
    "flow_id": "e9619aeb-7a03-49d7-9c7d-de4b9cf323fe",
    "completed_at": "2026-06-19T15:18:29.000000Z",
    "users_email": "individual@detected.co",
    "result": []
  }
}
```

```mermaid
---
config:
  theme: redux-dark
  look: classic
---
sequenceDiagram
    participant Customer as Customer
    participant Verify as Verify Portal
    participant Detected as Detected
    participant Hook as Your webhook endpoint
    participant App as Client's app
    Customer->>Verify: Open verify link
    Note over Customer,Verify: Mid-flow — forms, IDV / ID3, personal info
    Customer->>Verify: Complete mid-flow steps
    Note over Detected,Hook: Optional — not KYC complete
    Detected-->>Hook: profile.updated (optional)
    Customer->>Verify: Final Submit
    Note over Detected,Hook: KYC completion
    Detected->>Hook: verify.completed
    Detected->>Hook: profile.updated (usually same second)
    Note over App,Detected: Pull KYC detail
    App->>Detected: GET /representatives/{uuid}/verifications
    Detected-->>App: Verification results
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://detected.gitbook.io/detected-docs/api-overview/webhooks/profile-webhook-spec/verify-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.