POST /rest/v1.0/requisitions

Create a new Requisition (Subcontractor Invoices) for the specified Commitment

Servers

https://api.procore.com

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"
`Procore-Company-Id`	Integer	Yes	Unique company identifier associated with the Procore User Account.

Request body fields

Name	Type	Required	Description
`project_id`	Integer	Yes	Unique identifier for the project.
`attachments[]`	Array	No	Requisition (Subcontractor Invoice) attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files.
`requisition`	Object	No	Requisition (Subcontractor Invoice)
`requisition.requisition_start`	String	No	Requisition (Subcontractor Invoice) start date
`requisition.final`	Boolean	No	true or false value indicating whether or not this is the final invoice
`requisition.payment_date`	String	No	Date requisition was paid
`requisition.status`	String	No	Status; admin can set any status, standard and billing recipient can set to under_review (submit) or draft (save) Possible values: `"approved"` `"under_review"` `"pending_owner_approval"` `"revise_and_resubmit"` `"draft"` `"approved_as_noted"`
`requisition.period_id`	Integer	No	Period ID
`requisition.origin_data`	String	No	Requisition (Subcontractor Invoice) third party data
`requisition.custom_field_%{custom_field_definition_id}`		No	Value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one of the Custom Field Definition's LOV Entries. For a lov_entries data_type the value passed in should be an array of IDs of the Custom Field Definition's LOV Entries.
`requisition.comment`	String	No	Any comment
`requisition.invoice_number`	String	No	Invoice number
`requisition.origin_id`	String	No	Requisition (Subcontractor Invoice) third party ID
`requisition.requisition_end`	String	No	Requisition (Subcontractor Invoice) end date
`requisition.billing_date`	String	No	Billing date
`requisition.submitted_at`	String	No	Date requisition was submitted
`commitment_id`	Integer	Yes	Commitment ID

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.