Skip to main content

Delete Requisition

DELETE /px/requisitions/:id_item

Delete a Requisition from the system.

Required abilities

This operation requires either the Access - Scheduled Project Management ability, or Authority - Administrator.

Request

Responses

The object was successfully deleted. The response body is empty.

A 400 Bad Request is returned when the client request was malformed, invalid, or otherwise could not be processed as-is. Usually, the cause for the error is included in the error.message field of the response, and the client should correct the request and try again.

See also Core Concepts#Error Responses.

A 403 Forbidden response means that you are not authorized to perform this action or access this object, or the object does not exist at all.

The client request may have been valid but the client does not have permission to access the requested resource or perform the requested action.

:::tip 403 Forbidden also used when objects don't exist

In most cases, the system will not return a 404 Not Found error response; it returns 403 Forbidden both when the object doesn't exist at all, and also when it exists but the client does not have permission to access it. This is a security measure to prevent unauthorized users from determining whether an object exists or not.

:::

See also Core Concepts#Error Responses.

Not found - the requested resource could not be found or does not exist. This may also include cases where the resource does exist, but the client does not have permission to access that resource.

:::tip 403 Forbidden also used when objects don't exist

In most cases, the system will not return a 404 Not Found error response; it returns 403 Forbidden both when the object doesn't exist at all, and also when it exists but the client does not have permission to access it. This is a security measure to prevent unauthorized users from determining whether an object exists or not.

:::

See also Core Concepts#Error Responses.