## 1. Invitation - Completed
The *ticket.verification.completed* event is triggered when a *Verification* has completed all of its subprocesses, or an error has been raised and there are no more retries to attempt. Notification payload specifies a set of properties as shown on following JSON. It will contain its ticket, so it can be tracked by your processes. Also, it holds its **event**. The **flow\_status** specified ticket's current state, which can be either `ACCEPTED` or `REJECTED` , this value depends on **confidence\_score** property. The value of the **disposition** property can be either `PASSED` or `FAILED` which determines last executed subprocess' state. It also gives final results of entire flow, such as **risk\_code** and **confidence\_score**.
```json
{
"id": "YOUR-INVITATION-ID",
"invitation_state": "COMPLETED",
"cifcod": "YOUR-USER-CIFCODE",
"full_name": "Jon Doe",
"ticket": "YOUR-USER-IDV-TICKET",
"transaction_status": "ACCEPTED",
"attempts": 1
}
```
#### Completed Invitation state
* `COMPLETED`: indicates that **invitation's** ticket has been **completed**, so this is set to a **completed state**.
#### IDV ticket's transaction\_status statuses
* `ACCEPTED:` all IDV Ticket flow's subprocesses were executed correctly and their results have been considered as OK, so ticket is set to COMPLETED state.
* `REJECTED:` this status is set when an exception has been raised, or any IDV ticketsubprocess' result has been considered as unacceptable and no more retries can be atempted, ***eg.*** ***liveness detection*** process.
Here you find a further description of the response values below:
| Key | Data type | Description |
| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id` | `string` | The UUID of the *Invitation* which triggered this webhook. This will help you query our backend API for the details of the *Invitation*. |
| `invitation_state` | `string` | Invitation's current state. |
| `cifcod` | `string` | User's unique identifier. |
| `full_name` | `string` | User's name read from its IDV ticket process. |
| `ticket` | `string` | Invitation's IDV ticket's UUID. |
| `transaction_status` | `string` |
This holds the result of the processed ticket and its confidence\_score threshold matching.
As noted above, its value may be one of these 2 posibilities: - ACCEPTED - REJECTED
|
| `attempts` | `number` | Specifies the number of attempts made by the user to complete its IDV ticket process. |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.preventor.com/server/webhooks/invitations-link.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.