POST /Assets

Adds an asset to the system

Servers

https://api.xero.com/assets.xro/1.0

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"
`xero-tenant-id`	String	Yes	Xero identifier for Tenant
`Idempotency-Key`	String	No	This allows you to safely retry requests without the risk of duplicate processing. 128 character max.

Request body fields

Name	Type	Required	Description
`bookDepreciationSetting`		No
`assetNumber`	String	No	Must be unique.
`canRollback`	Boolean	No	Boolean to indicate whether depreciation can be rolled back for this asset individually. This is true if it doesn't have 'legacy' journal entries and if there is no lock period that would prevent this asset from rolling back.
`isDeleteEnabledForDate`	Boolean	No	Boolean to indicate whether delete is enabled
`bookDepreciationDetail`		No
`assetStatus`	String	No	See Asset Status Codes. Valid values: `"Draft"` `"Registered"` `"Disposed"`
`purchaseDate`	String	No	The date the asset was purchased YYYY-MM-DD
`disposalPrice`	Number	No	The price the asset was disposed at
`serialNumber`	String	No	The asset's serial number
`accountingBookValue`	Number	No	The accounting value of the asset
`assetName`	String	Yes	The name of the asset
`disposalDate`	String	No	The date the asset was disposed
`warrantyExpiryDate`	String	No	The date the asset’s warranty expires (if needed) YYYY-MM-DD
`assetTypeId`	String	No	The Xero-generated Id for the asset type
`assetId`	String	No	The Xero-generated Id for the asset
`purchasePrice`	Number	No	The purchase price of the asset

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.