--- title: "Full Auto webhook | Veriff.com" slug: "full-auto-webhook" description: "Set up the Full Auto webhook in the Veriff Customer Portal to receive verification data, insights, and decision scores for efficient end-user verification." updated: 2025-09-05T18:04:07Z published: 2025-09-05T18:04:07Z --- > ## Documentation Index > Fetch the complete documentation index at: https://devdocs.veriff.com/llms.txt > Use this file to discover all available pages before exploring further. # Full Auto webhook > [!WARNING] > The Full Auto webhook is required only for the [Essential Plan: Full Auto solution](/v1/docs/essential-plan-full-auto) which returns insights, extractions data and decision score. This webhook is used to return the verification data once the **Full Auto** verification has been processed. The payload is sent to `Webhook Full Auto URL`, which you need to set up the webhook in the Veriff Customer Portal. →*See Webhooks Guide > [Set up webhooks](https://veriff-dev-documentation.document360.io/docs/webhooks-guide#set-up-webhooks) sub-section for detailed overview of the setup process* --- ## Prerequisites 1. Make sure you **have access to the Veriff Customer Portal** 1. If you do not, see the Getting Started → [Sign up](https://devdocs.veriff.com/docs/signing-up) and [Log in](https://devdocs.veriff.com/docs/logging-in) articles 2. Set up webhook URL(s) **on your side**and have them at hand 1. Make sure they **match** the [Webhook URL](https://devdocs.veriff.com/docs/webhooks-guide#webhook-url-requirements) requirements 2. Make sure your system is **able to handle** [Webhooks receipt, delivery and resending](https://devdocs.veriff.com/docs/webhooks-guide#webhook-delivery-receipt-and-resending) requirements 3. Check the [Webhooks headers and payload](https://devdocs.veriff.com/docs/webhooks-guide#webhooks-headers-and-payload) section for info 3. Secure your communication, check the [HMAC Authentication and Endpoint Security](https://devdocs.veriff.com/docs/hmac-authentication-and-endpoint-security) article 4. Make sure your system is **able to handle** the [Backwards compatible changes](https://devdocs.veriff.com/docs/backwards-compatible-changes) 5.Proceed to [Full Auto webhook setup](/v1/docs/full-auto-webhook#full-auto-webhook-setup) below --- ## Full Auto webhook setup 1. Log in to the **Veriff Customer Portal** 2. Navigate to the **Integrations** page via the top menu and open the integration used for Full Auto 3. On the integration's page, select the **Settings** tab 4. Under the title **Integration settings** you see a list of webhooks 5. Fill in the `Webhook Full Auto URL` field 1. Note that because all the data is returned via specific Full Auto webhook, **the decision webhook is not used**, therefore the `Webhook decisions URL` input field is not available. →*See Webhooks Guide > [Set up webhooks](https://veriff-dev-documentation.document360.io/docs/webhooks-guide#set-up-webhooks) sub-section for detailed overview of the setup process* --- ## Additional notes > [!NOTE] > These Full Auto sessions **do not return** session reason or decision **codes**. > [!NOTE] > `data.verification.decisionScore` parameter > > This is a numerical value representing how **confident** the system is that the **session is genuine**, higher number means that the session is more likely to be genuine. > > In the **API and webhooks payloads**, it is shown as a **float** in the **range of 0–1** > > In the **Veriff Customer Portal,** the range is shown as **1–100** --- ## Sample request The example below is a light-weight version of the payload. To see the more details, log in to you Veriff account and see the [detailed sample payload article](https://help.veriff.com/en/articles/8529223-full-auto-webhook-sample)[↗] in Veriff Knowledge Base. ```json {  "status": "success",  "eventType": "fullauto",  "sessionId": "1234567d-1ab2-34c5-bba7-a23gh58908er",  "attemptId": "12e3d456-9ea2-4821-a2bb-aabb4113b61f",  "vendorData": null,  "version": "1.0.0",  "acceptanceTime": "2023-10-05T17:34:06.882846Z",  "time": "2023-10-05T17:33:22.449Z",  "data": {      "verification": {          "decisionScore": 0.96,          "decision": "approved",          "person": {              "firstName": {                  "confidenceCategory": "medium",                  "value": "ASHOK",                  "sources": [                      "MRZ",                      "VIZ"                  ]              },              ...          },          "document":{              "type": {                  "value": "id_card"              },              "country": {                  "value": "IN"              },              "number": {                  "confidenceCategory": "high",                  "value": "123abc456",                  "sources": [                      "MRZ",                      "VIZ"                  ]              },              ...          },          "insights":[              {                  "label": "xwz",                  "result": "yes",                  "category": "abc"              },              {                  ...              },          ]      },  }, } ``` --- ## Request properties explained *Required field - `status`: `string`* Status of the request, one of `success`, `fail` - `eventType`: `string`* Full Auto event name, returns `fullauto` - `sessionId`: `UUID`* UUID v4 which identifies the verification session - `attemptId`: `UUID`* UUID v4 which identifies an attempt inside the verification session - `vendorData`: `string | null`* The unique identifier that you created for your end-user, returned unmodified in webhooks and API calls. `null` if not specified - `endUserId`: `string | null`* The `UUID` that you created for your end-user, returned unmodified in webhooks and API calls. `null` if not specified - `version`: `string`* Webhook version - `acceptanceTime`: `string`* Timestamp of when the session was generated. Combined ISO 8601 date and time in UTC (YYYY-MM-DDTHH:MM:SS.SSS+Timezone Offset|Z, i.e., 2018-04-18T11:02:05.261Z) - `time`: `string`* Timestamp of when the event was generated. Combined ISO 8601 date and time in UTC (YYYY-MM-DDTHH:MM:SS.SSS+Timezone Offset|Z, i.e., 2018-04-18T11:02:05.261Z) - `data`: `object`* Verification data objects - `verification`*: `object` - `decisionScore`: `number` | `null`* A float number, shows how confident the system is that the session is genuine. Higher number indicates higher confidence. The number is rounded up to two decimal places. - `decision`: `string`* Shows system’s suggestion of what to do with the session, one of `approved`, `declined`, `resubmission_requested`, `expired`,` abandoned` - **`person`: `object`* Data extracted from the document about the person. Contains additional objects with specific data that has been extracted** - `...`: `object` | `null`*` `Extraction activity name. Log in to Veriff Customer Portal and find the possible extraction activity names in the [detailed request properties explanation article](https://help.veriff.com/en/articles/8523724-full-auto-webhook-properties)[↗] or check the [detailed sample payload article](https://help.veriff.com/en/articles/8529223-full-auto-webhook-sample)[↗] for more info - `confidenceCategory`: `string` | `null `Shows the confidence value, one of `high`, `medium`, `low` - `value`: `string` | `null` Data extracted from the document - `sources`: `array` | `empty` Shows the document data field where the data was extracted from, one of `VIZ`, `MRZ`, `NFC`, `BARCODE` - **`document`: `object`* Data extracted from the document about the document. Contains additional objects with specific data that has been extracted** - `type`: `object `| `null` - `value`: `string` | `null` Document type, one of `PASSPORT`, `ID_CARD`, `RESIDENCE_PERMIT`, `DRIVERS_LICENSE`, `VISA` - `country: object` | `null` - `value`:` string | null` ISO-2 country code of the document country - `...`: `object` | `null`* Extraction activity name. Log in to Veriff Customer Portal and find the possible extraction activity names in the [detailed request properties explanation article](https://help.veriff.com/en/articles/8523724-full-auto-webhook-properties)[↗] or check the [detailed sample payload article](https://help.veriff.com/en/articles/8529223-full-auto-webhook-sample)[↗] for more info - `confidenceCategory`: `string` | `null `Shows the confidence value, one of `high`, `medium`, `low` - `value`: `string` | `null `Data extracted from the document - `sources`: `array` | `empty` Shows the document data field where the data was extracted from, one of `VIZ`, `MRZ`, `NFC`, `BARCODE` - **`insights`: `array | null`* Array of pieces of metadata that help explain the decision. Note that the actual list of insights visible in the webhook payload depends on your integration** - `label`: `string` Name of the insight. Log in to Veriff Customer Portal and find the possible extraction activity names in the [detailed request properties explanation article](https://help.veriff.com/en/articles/8523724-full-auto-webhook-properties)[↗] or check the [detailed sample payload article](https://help.veriff.com/en/articles/8529223-full-auto-webhook-sample)[↗] for more info - `result`: `string` Result of the insight, one of `yes`, `likelyYes`, `no`, `notApplicable` - `category`: `string` Name of the category the insight belongs to. Log in to Veriff Customer Portal and find the possible extraction activity names in the [detailed request properties explanation article](https://help.veriff.com/en/articles/8523724-full-auto-webhook-properties)[↗] or check the [detailed sample payload article](https://help.veriff.com/en/articles/8529223-full-auto-webhook-sample)[↗] for more info