🔒 Create purchase order line item V3

This endpoint is currently in Beta and available for testing. It may contain bugs, and breaking changes can occur at any time without prior notice. We do not recommend using Beta endpoints in production environments. Should you choose to use it in production, you assume full responsibility for any resulting issues.

This endpoint requires the following scopes: purchaseOrder:update.

Create a new purchase order line item.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Body Params
product
object
required

Product information.

float
required

Quantity of the line item.

string
length ≤ 255

Line item name. If not provided, the product name will be used.

string

Line item description. If not provided, the product description will be used.

string
length ≤ 128

Country of origin for the product. If not provided, the product's country of origin will be used.

string
length ≤ 128

Harmonized System (HS) code for the product. If not provided, the product's HS code will be used.

date

Delivery date of the line item.

boolean
Defaults to false

Whether to show the delivery date as calendar week or explicit.

string

Internal comment for the line item.

string
length ≤ 128

Customer product number for the line item.

string
length ≤ 128

Unit of the line item (e.g., "kg", "pcs"). If not provided, the product's unit will be used.

string
length ≤ 255

Packaging unit (VPE) of the line item — how many units one package contains. On purchase orders a numeric value greater than 1 makes the generated PDF present the line in packages: the price is printed per package, the quantity in packages, and the unit as "VPE". On all other document types the value is stored and carried over on document conversion, but nothing reads it — in particular, the stored quantity, the stored unit price, and the values returned by the API are never derived from it.

project

Project of the line item. If not provided, the product's project will be used. Explicitly pass null to assign no project.

customFields
array of objects

Custom field values for the line item. Accepts the customField1 to customField40 keys as well as any custom field configured for this line item in your Xentral instance. Listed keys are written, keys that are not listed are left untouched.

customFields
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

401

Unauthorized

403

Forbidden

404

Not Found

Language
Credentials
Bearer
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json