Webhooks

You can configure webhooks for 1-Click Health: see here in the Setup guide. This allows you to receive 1-Click Health output data asynchronously. (You can alternatively poll the GET /1-click/health endpoint.)

Method	POST
URL	Defined by webhook brand setting
Authentication	Defined by webhook brand setting (None, API Key, or Basic Auth)
Timeout	30 seconds per attempt
Retries	Up to 3 attempts, with exponential backoff (about 1 second, then 2 seconds)
Expected response	Respond with a 2xx status (for example 200) to acknowledge receipt. Any other status, or a timeout, is treated as a failed delivery and retried.
Delivery	At least once (multiple deliveries possible)
Retention	DLQ (dead letter queue) retained for 14 days

Headers

Each webhook request includes the following headers:

Header	Value	Description
Content-Type	application/json	The payload is always sent as JSON.
User-Agent	VerifiedInc-Webhook/1.0	Identifies the request as coming from Verified.

Any authentication headers you configure in your webhook brand setting (API Key or Basic Auth) are also included.

Payload

GET /1-click/health Response Body

{
    "event": "1-click.health.lookup",
    "healthDataUuid": string,
    "sentAt": integer,
    ...1ClickHealthEntity
}

Property	Type	Format	Description	Example
event	string	-	Response from the 1-Click Health lookup	"1-click.health.lookup"
healthDataUuid	string	Version 4 UUID	Unique identifier for the 1ClickHealthEntity that will be returned at the end of the 1-Click Health flow	"9e12fe5b-5bb8-410a-ac6b-6e053e4c7e8d"
sentAt	integer	Unix time (milliseconds)	When the payload was sent	1760053705000
...	1ClickHealthEntity	See 1ClickHealthEntity	1ClickHealthEntity for the 1-Click Health flow	See 1ClickHealthEntity

Webhooks for 1-Click Signup are Coming Soon!

We don't yet support webhooks for 1-Click Signup, but those are coming soon. If you'd like to be notified when they're available, please email us at Support@Verified.inc.