Requisition Received
Event Type
requisition_received
Summary
Agency-only event sent when a requisition is released to the agency. Selecting an agency on a draft or internally pending requisition does not send this event.
Release can happen manually, after final approval, or through a scheduled tier transition.
Access
Agency webhooks only. Sent only to the agency receiving the released requisition.
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_received |
| 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
|
| test | boolean | No | Present and true for test deliveries; the resource ID is test |
Payload Example
{
"id": "evt_01K1RECEIVED7R6Q5P4N3M2L1",
"type": "requisition_received",
"createdAt": "2026-07-28T10:30:00.000Z",
"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.