Requisition Created

Event Type

requisition_created

Summary

Company-only event sent when a requisition is created.

Access

Company webhooks only. Agency webhooks cannot subscribe to this event.

Delivery

Requidex sends a signed POST request with Content-Type: application/json to the configured webhook URL. Return a 2xx response after accepting the event for processing. Duplicate or out-of-order deliveries are possible; deduplicate by event ID.

See delivery headers, signature verification and retry handling for the shared contract. The webhook signing secret is separate from an API key used to fetch the record.

Payload Fields

Field	Type	Required	Description
id	string	Yes	Stable event identifier, reused for delivery retries
type	string	Yes	requisition_created
createdAt	string	Yes	Event creation time in ISO 8601 UTC format
data	object	Yes	Affected resource reference; not a snapshot of the changed record Show child attributes requisition object — Affected requisition reference Show child attributes id string — Identifier used by the corresponding detail endpoint
test	boolean	No	Present and true for test deliveries; the resource ID is test

Payload Example

{
  "id": "evt_01HYZ4KQJ4A9H2J7QZ8A4R7X9M",
  "type": "requisition_created",
  "createdAt": "2026-02-24T15:05:43.455Z",
  "data": {
    "requisition": {
      "id": "507f1f77bcf86cd799439011"
    }
  }
}

Read the Affected Record

The webhook payload contains the requisition's full object ID in data.requisition.id. Use that id as the {id} path parameter on GET /requisitions/{id} to fetch the full requisition object after receiving this event.

The follow-up API request uses your API key and the endpoint’s scope and access rules. A webhook subscription does not grant additional API access. Test deliveries include test: true and use the resource ID test; do not fetch a business record for those deliveries.