How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Xero Asset API

The Asset API from Xero — 4 operation(s) for asset.

Xero Asset API is one of 10 APIs that Xero publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Asset. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 6 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 11.1.0.

Requests are made against a single base URL, https://api.xero.com/api.xro/2.0.

6 operations 4 paths 9 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
11.1.0
Base URL
https://api.xero.com/api.xro/2.0
Authentication
OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 1

Xero Asset API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 16 scopes.

  • OAuth2 — For more information

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Asset 6
GET
/Assets
Xero searches fixed asset
getAssets 7 params → 200400
POST
/Assets
Xero adds a fixed asset
createAsset 2 params body → 200400
GET
/Assets/{id}
Xero Retrieves fixed asset by id
getAssetById 2 params → 200400
GET
/AssetTypes
Xero searches fixed asset types
getAssetTypes 1 param → 200400
POST
/AssetTypes
Xero adds a fixed asset type
createAssetType 2 params body → 200400409
GET
/Settings
Xero searches fixed asset settings
getAssetSettings 1 param → 200400

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Asset (16 properties), BookDepreciationDetail (12 properties), Setting (8 properties), BookDepreciationSetting (8 properties). Each schema is shown below with its type and property counts.

BookDepreciationSetting
object
8 properties
Asset
object
16 properties 1 required
BookDepreciationDetail
object
12 properties
Pagination
object
4 properties
AssetType
object
7 properties 2 required
AssetStatus
string
See Asset Status Codes.
AssetStatusQueryParam
string
See Asset Status Codes.
Setting
object
8 properties 1 required
Assets
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xero-asset-api-openapi.yml Raw ↑

Other APIs Xero publishes across the network.

Xero Accounting API
Xero BankFeeds API
Xero Files API
Xero Finance API
Xero Identity API
Xero PayrollAu API
Xero PayrollNz API
Xero PayrollUk API
Xero Project API
Where this information came from

This is an independent, third-party profile of Xero Asset API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.