Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Veremark connector page.Webhook setup
This connector uses Manual Webhooks. Veremark has no webhook subscription API or portal setting. Instead, each background check request carries its own callback in the webhook field of the Create Request call, and Veremark calls that URL every time the request changes status.
Copy the Native Webhook URL
In StackOne, open the Linked account for your Veremark connection and copy the Native Webhook URL.
Set the webhook on each request
When creating a request with the Create Request action, set webhook.url to the Native Webhook URL and webhook.method to post, put or patch. Only requests created with this webhook are delivered to StackOne.
- Example:
{"url": "<Native Webhook URL>", "method": "post"} - Leave
authentication_typeandcredentialsempty. The Native Webhook URL already identifies the account. - Do not use
get. Veremark sends no body with GET, so the notification cannot be matched to an event.
Available webhook events
The following Veremark event can be enabled. It is delivered only for requests created with the webhook described above.
Request events
Events related to background check requests.
- Request Status Changed (
requestStatus) — Fired when a request or one of its checks moves to a new status (requested, in progress, paused, review, closed, criteria met or expired). Creating a request does not fire it. The payload includes the request GUID, your external ID and the retrieve URL, but not the new status.
Delivery format
Details of how Veremark delivers events to StackOne.
One notification per status change
Veremark sends one call per status change of the request or any of its checks, and retries any response other than 2xx. The payload has no status or timestamp, so the event date is the time StackOne received it. Use the Get Request action with the request GUID to read the current status.