Edit Requisitions
Production
https://{{subdomain}}.daftra.com/api2
Production
https://{{subdomain}}.daftra.com/api2
PUT
https://{{subdomain}}.daftra.com/api2
Requisition object plus a RequisitionItem array, exactly like the create endpoint. On update no header field is strictly required — omitted fields such as store_id, branch_id and number keep / default from the existing record. Each line item still needs a product_id and a positive quantity.number is generated automatically when left empty.{ "status": true, "id": <id> } at HTTP 200 (add extended to also receive the saved record under data). A failure to save returns { "status": false, "message": "Couldn't update Requisition" }, also at HTTP 200.403 for POS / stocktaking requisitions, for a requisition that has expense distribution attached, or for a requisition belonging to another branch.Request
Path Params
Query Params
Header Params
Body Params application/json
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --globoff --request PUT 'https://.daftra.com/api2/requisitions/1234?extended=1' \
--header 'Accept: application/json' \
--header 'apikey: ' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{"Requisition":{"type":1,"notes":"Updated note"},"RequisitionItem":[{"product_id":123,"quantity":12,"unit_price":50}]}'Response Response Example
200 - Example 1
{
"status": true,
"id": 1234,
"data": {
"Requisition": {},
"RequisitionItem": [
{}
]
}
}