Accela Assets API
Assets can be any object that an agency owns or maintains. Assets have standard properties such as date of service, start value, current value, depreciation value, salvage value, size, etc.To manage and organize assets and asset types, Civic Platform supports several levels of asset classifications. Each asset is classified with an asset type, and each asset type can be organized within a group or by class type.In general, assets are classified by the following standard class types:- **Linear** - The linear class type indicates a relationship between two assets. For example, a section of street, sidewalk, or runway at the city municipal airport.- **Node** - Node-link linear combines assets to indicate an explicit relationship between the assets. Node-link linear requires the user to define the asset ID by identifying the assets on each end of the linear asset. For example, define a sewer main by identifying its end points such as Manholes. Manhole 'MH-01' flows to manhole 'MH-02' which flows to manhole 'MH-03.' The node-link linear allows for the creation of the Sewer Main asset by naming the beginning and end point assets of each pipe. In this example, the agency can create two Sewer Main assets such as class type of node-link linear defined as 'MH-01 - MH-02' and 'MH-02 - MH-03.'- **Component** - The component class specifies assets that are independent and do not connect assets as a building or tools. A component is free of lines and nodes.- **Polygon** - The polygon class type includes assets such as water drainage area, a storm drainage area, or a catch basin.
Accela Assets API is one of 109 APIs that Accela publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Assets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 6 operations across 5 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version v4.
Requests are made against a single base URL, https://apis.accela.com/.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 6
Across 5 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Assets can be any object that an agency owns or maintains.
Schemas 20
The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are simpleRecordModel (68 properties), assetRelatedModel (29 properties), assetWithAttributesModel (27 properties), assetExtModel (26 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Accela 12
Other APIs Accela publishes across the network.
This is an independent, third-party profile of Accela Assets 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.