Delete Requisitions

Deletes a requisition (and its related stock movements) identified by its id.

This is a UI-oriented action and does not return a JSON body. To actually delete through the API you must pass force=1 as a query parameter — without it the request returns the HTML delete-confirmation page and nothing is deleted.

On success the request is redirected (HTTP 302) to the requisitions list. Pre-delete guards (closed accounting period, another branch, a pending order, a locked item, insufficient stock, tracking, or a linked manufacturing order) also surface as redirects with a flash message rather than a structured JSON error.

To delete a requisition and receive a machine-readable result, prefer the v2 entity API for the requisition entity.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Responses

🔵302Found

application/json

The requisition was deleted (when force=1). The response is a redirect to the requisitions list with no body. Pre-delete validation failures also redirect, with the reason shown as a flash message.

Headers

Bodyapplication/json

🟢200OK

🟠401Unauthorized

curl --location --globoff --request DELETE 'https://.daftra.com/api2/requisitions/1234?force=1' \ --header 'Accept: application/json' \ --header 'apikey: ' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json'

Request

Responses