> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Veremark Webhook Setup Guide

> Configure Veremark to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/veremark#getting-started) on the Veremark connector page.

<section data-guide-section data-guide-scopes="">
  <h2>Webhook setup</h2>

  <p>This connector uses <strong>Manual Webhooks</strong>. 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.</p>

  <Steps>
    <Step title="Copy the Native Webhook URL">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>In StackOne, open the <strong>Linked account</strong> for your Veremark connection and copy the <strong>Native Webhook URL</strong>.</p>
      </div>
    </Step>

    <Step title="Set the webhook on each request">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>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.</p>

        <ul>
          <li>Example: `{"url": "<Native Webhook URL>", "method": "post"}`</li>
          <li>Leave `authentication_type` and `credentials` empty. The Native Webhook URL already identifies the account.</li>
          <li>Do not use `get`. Veremark sends no body with GET, so the notification cannot be matched to an event.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>The following Veremark event can be enabled. It is delivered only for requests created with the webhook described above.</p>

  <Steps>
    <Step title="Request events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to background check requests.</p>

        <ul>
          <li><strong>Request Status Changed</strong> (`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.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Delivery format</h2>

  <p>Details of how Veremark delivers events to StackOne.</p>

  <Steps>
    <Step title="One notification per status change">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>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.</p>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.