v1

latestOpenAPI 3.1.02026-08-0420819698.7 KB
Routes
Purchase Orders

New Purchase Order

This request creates a new Purchase Order.

Parameter: locationID, Type: Int, Required?: Required, Description: The ID of the location this PO will be created for. Parameter: vendorID, Type: Int, Required?: Required, Description: The ID of the vendor that this PO will be associated with. Parameter: userID, Type: Int, Required?: Required, Description: The ID of the user that this PO will be assigned to. Parameter: taskID, Type: Int, Required?: Optional, Description: The ID of the task that this PO will be associated with. Parameter: budgetID, Type: Int, Required?: Optional, Description: The ID of the budget that this PO will be associated with. If not provided, this will be the location's default budget. Parameter: date, Type: Int, Required?: Optional, Description: The start time of the PO -- this can be in the past or the future and will still show up in the UI. Must be a unix timestamp. If not provided, this will default to the current time. Parameter: expectedDate, Type: Int, Required?: Optional, Description: The expected delivery date of this PO. Must be a unix timestamp. Parameter: requestDescription, Type: String, Required?: Optional, Description: A description of the "request" for this PO. Parameter: customField1, Type: String, Required?: Optional, Description: PO custom field, the customer chooses which custom fields are available on all POs. Parameter: customField2, Type: String, Required?: Optional, Description: PO custom field, the customer chooses which custom fields are available on all POs. Parameter: customField3, Type: String, Required?: Optional, Description: PO custom field, the customer chooses which custom fields are available on all POs. Parameter: customField4, Type: String, Required?: Optional, Description: PO custom field, the customer chooses which custom fields are available on all POs. Parameter: customField5, Type: String, Required?: Optional, Description: PO custom field, the customer chooses which custom fields are available on all POs. Parameter: customField6, Type: String, Required?: Optional, Description: PO custom field, the customer chooses which custom fields are available on all POs.

post/v2/po

Request body

locationIDinteger
vendorIDinteger
userIDinteger
requestDescriptionstring
dateinteger
expectedDateinteger
budgetIDinteger
customField1string
customField2string
customField3string

Response

New Purchase Order

poIDinteger