# Verification Request Event This callback event is a POST request to the specified verification callback URL and is triggered when a new verification request is made from the SDK client or the Verification Request API. This callback event is only triggered when a verification callback URL is specified in your dashboard. Endpoint: POST VerificationRequestEvent Version: 2.0.1 Security: , ## Request fields (application/json): - `id` (string, required) The ID of the verification request. Example: "1234567890" - `event` (string, required) The type of the event. Enum: "VerificationRequestEvent", "VerificationResultEvent", "VerificationSmsDeliveredEvent" - `method` (string, required) The type of the verification. Enum: "sms", "flashcall", "callout" - `identity` (object, required) Specifies the type of endpoint that will be verified and the particular endpoint. is currently the only supported endpoint type. - `identity.type` (string, required) Currently only type is supported. Enum: "number" - `identity.endpoint` (string, required) For type use an [E.164](https://community.sinch.com/t5/Glossary/E-164/ta-p/7537)-compatible phone number. Example: "+11235551234" - `reference` (string) Used to pass your own reference in the request for tracking purposes. Must be a unique value for each started verification request. The value must be encodable in the URL path segment. This value is passed to all events and returned from the status and report endpoints. The reference can be used to check the [status of verifications](https://developers.sinch.com/docs/verification/api-reference/verification/verification-status/verificationstatusbyreference), like with ID or identity. - `custom` (string) Can be used to pass custom data in the request. Will be passed to all events. Max length 4096 characters, can be arbitrary text data. - `price` (object) - `price.currencyId` (string) ISO 4217 currency code Example: "USD" - `price.amount` (number) Example: 0.0127 - `acceptLanguage` (array) Allows you to set or override if provided in the API request, the SMS verification content language. Only used with the SMS verification method. The content language specified in the API request or in the callback can be overridden by carrier provider specific templates, due to compliance and legal requirements, such as [US shortcode requirements (pdf)](https://community.sinch.com/t5/SMS/Sinch-US-Short-Code-Onboarding-Overview/ta-p/7085). Example: ["es-ES"]