Accela
Accela is a San Ramon, California govtech company whose cloud Civic Platform runs permitting, planning, licensing, code enforcement, inspections, asset management and citizen service requests for state and local government agencies worldwide. Its public developer surface is the Accela Construct API (V4) — a 417-operation REST API served from apis.accela.com and documented as fifteen Swagger 2.0 documents on the Accela Developer Portal, covering records, inspections, contacts and professionals, addresses/parcels/owners, assets and assessments, documents, payments and shopping carts, reports, search, citizens, CivicID and platform settings. Access is OAuth 2.0 against auth.accela.com with agency- and environment-scoped tokens, and every request is bound to a specific government tenant through the x-accela-agency and x-accela-environment headers.
Accela publishes 109 APIs on the APIs.io network, including AA Version API, Addresses API, Agencies API, and 106 more. Tagged areas include GovTech, Government, Permitting, Licensing, and Code Enforcement.
Accela’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, changelog, and 28 more developer resources.
30 APIs
Individual APIs this provider publishes, each with its own machine-readable definition.
CivicData.com is Accela's free open-data platform for government agencies, described on its own site as "a free open data platform built by Accela" and "Built on open source usi...
This is to return the version number of the AA server that is running, which allows the mobile app to make decisions as to what API's they have available.
An address provides details about the physical location of a parcel, building, contact, and so forth. An address is part of a property's APO (address, parcel, owner) information...
The Agencies API from Accela — 5 operation(s) for agencies.
The **announcements** API endpoints allow apps to get agency and public announcements, and mark them as read announcements.
App settings are defined when a developer registers the app on [Accela Developer Portal](https://developer.accela.com). These settings include app name, ID, and so forth.
In Civic Platform, an assessment is synonymous to an asset condition assessment. An asset condition assessment is a scheduled maintenance review and/or a quality review of a gro...
An agency can define custom attributes for each type of assessment.
Inspectors can attach documents and photos as needed to the asset condition assessment record, and record the assignments and costs that occur on the assessment.
During an assessment, an inspector may make observations about the condition of the asset. For example, he may go to a certain area to look at the condition of the sidewalk and ...
Asset assessments often alert agencies to problems that need attention. A work order is the starting point in the repair process. Associating a work order with an assessment hel...
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...
Condition assessments apply to assets that change or deteriorate over time. These assets may require a visual condition assessment to effectively manage their life cycle. Transa...
In addition to these asset properties, assets can also have custom attributes which are customized characteristics of assets, structures, and establishments. Asset custom attrib...
Document collaterals can be attached to assets.
Assets can be associated to transactional records when an asset assessment necessitates a service work order or if an application pertains to an agency asset.
API for batch API requests.
A citizen user designates a delegate by first sending them an invitation. The invited citizen users can accept or reject invitations. When the invited citizen users accept the i...
The **citizenaccess** API endpoints allow a logged-in Citizen Access user to register and manage his or her own account profile, status, and contacts.
The CivicId API from Accela — 3 operation(s) for civicid.
**Conditions** The system provides standard conditions for different record types(permits, licenses, inspections, and so forth). Depending on the condition, condition violations...
The Contacts/Addresses API from Accela — 2 operation(s) for contacts/addresses.
A reference contact captures information about people or organizations involved in a business process. Contacts include licensed professionals, such as contractors, architects, ...
The Contacts/Conditions API from Accela — 2 operation(s) for contacts/conditions.
The Contacts/Custom Forms API from Accela — 3 operation(s) for contacts/custom forms.
The Contacts/Custom Tables API from Accela — 3 operation(s) for contacts/custom tables.
The Contacts/Records API from Accela — 1 operation(s) for contacts/records.
The Documents API enables apps to upload and download documents, and attach a document to a record or inspection.
Filters are user queries that are stored in Civic Platform and enable users to find information easily. Filters are configured in Civic Platform's Data Filter Portlet to display...
The Geocoding API provides geo-coded address information based on map services configured on [Construct Admin Portal](https://admin.accela.com) > Agencies > {Agency} > Agency Se...
The Gis API from Accela — 1 operation(s) for gis.
The Inspections API from Accela — 15 operation(s) for inspections.
The Inspections/Checklists API from Accela — 2 operation(s) for inspections/checklists.
The Inspections/Checklists/Checklist Items API from Accela — 6 operation(s) for inspections/checklists/checklist items.
The Inspections/Checklists/Checklist Items/Custom Forms API from Accela — 3 operation(s) for inspections/checklists/checklist items/custom forms.
The Inspections/Checklists/Checklist Items/Custom Tables API from Accela — 4 operation(s) for inspections/checklists/checklist items/custom tables.
The Inspections/Condition Approvals API from Accela — 3 operation(s) for inspections/condition approvals.
The Inspections/Conditions API from Accela — 4 operation(s) for inspections/conditions.
The Inspections/Documents API from Accela — 2 operation(s) for inspections/documents.
The Inspections/Time Accounting API from Accela — 3 operation(s) for inspections/time accounting.
The Inspectors API from Accela — 2 operation(s) for inspectors.
An invoice fee can either be generated manually in the Civic Platform's Payment Processing portlet or automatically if configured in Civic Platform Administration. The Invoice A...
API for tracking vehicle mileage associated with inspections.
An owner defines an individual or entity related to a parcel so that the owner becomes the responsible party and point of contact for the parcel. The parcel owner must initiate ...
A parcel defines a piece of land with a specific location and legally defined boundaries. The county assessor's office typically maintains information about all land parcels wit...
Payments represent the acceptance of monetary funds submitted to the agency in relation to a transactional record. The system uses payments to invoice for services rendered and ...
A professional is a contractor, architect, engineer, developer, or associated organization. The system requires that all professionals be licensed. Similar to reference contacts...
The Professionals/Conditions API from Accela — 1 operation(s) for professionals/conditions.
The Professionals/Records API from Accela — 1 operation(s) for professionals/records.
Activities related to a record can be assigned to a staff member when the activities require further action, such as a follow-up inspection or service maintenance.
A record can have at least one associated address, such as the address of the application contact or the location of a permit application, service request, or work order.
The Records/Addresses/Custom Forms API from Accela — 2 operation(s) for records/addresses/custom forms.
A record is a fundamental Civic Platform object that captures an agency's daily process tranactions, such as applications, permits, cases, licenses, service requests, and work o...
A work order record is linked to assets that require inspection, repair service, or any kind of task that needs to be performed and tracked in the system.
A staff user can add comments regarding the record, or can choose from standard comments that have been configured for the agency.
The Records/Condition Approvals API from Accela — 3 operation(s) for records/condition approvals.
A condition is a requirement that you can apply to an application (or component of an application), that the application must fulfill to qualify for approval. Although condition...
One or more reference contacts can be associated to an application or service request.
The Records/Contacts/Custom Forms API from Accela — 3 operation(s) for records/contacts/custom forms.
The Records/Contacts/Custom Tables API from Accela — 3 operation(s) for records/contacts/custom tables.
The Records/Costs API from Accela — 2 operation(s) for records/costs.
The Records/Custom Forms API from Accela — 3 operation(s) for records/custom forms.
The Records/Custom Tables API from Accela — 4 operation(s) for records/custom tables.
The Records/Documents API from Accela — 3 operation(s) for records/documents.
The Records/Fees API from Accela — 2 operation(s) for records/fees.
The Records/Inspections API from Accela — 2 operation(s) for records/inspections.
The Records/Invoices API from Accela — 1 operation(s) for records/invoices.
The Records/Owners API from Accela — 3 operation(s) for records/owners.
The Records/Parcels API from Accela — 3 operation(s) for records/parcels.
The Records/Part Transactions API from Accela — 2 operation(s) for records/part transactions.
The Records/Payments API from Accela — 2 operation(s) for records/payments.
The Records/Professionals API from Accela — 3 operation(s) for records/professionals.
The Records/Trust Accounts API from Accela — 1 operation(s) for records/trust accounts.
The Records/Votes API from Accela — 2 operation(s) for records/votes.
The Records/Workflows API from Accela — 7 operation(s) for records/workflows.
Civic Platform provides a set of standard reports, developed with reporting tools such as Crystal Reports, Microsoft Reporting Services. The Reports API sends requests to the re...
The Search API from Accela — 13 operation(s) for search.
The Settings/Activities API from Accela — 3 operation(s) for settings/activities.
The Settings/Addresses API from Accela — 7 operation(s) for settings/addresses.
The Settings/Assessments API from Accela — 1 operation(s) for settings/assessments.
The Settings/Asset Types API from Accela — 5 operation(s) for settings/asset types.
The Settings/Assets API from Accela — 3 operation(s) for settings/assets.
The Settings/Comments API from Accela — 2 operation(s) for settings/comments.
The Settings/Conditions API from Accela — 4 operation(s) for settings/conditions.
The Settings/Contacts API from Accela — 7 operation(s) for settings/contacts.
The Settings/Costs API from Accela — 6 operation(s) for settings/costs.
The Settings/Departments API from Accela — 2 operation(s) for settings/departments.
The Settings/Documents API from Accela — 6 operation(s) for settings/documents.
The Settings/Drilldowns API from Accela — 1 operation(s) for settings/drilldowns.
The Settings/Inspections API from Accela — 12 operation(s) for settings/inspections.
The Settings/Modules API from Accela — 1 operation(s) for settings/modules.
The Settings/Owners API from Accela — 1 operation(s) for settings/owners.
The Settings/Parcels API from Accela — 1 operation(s) for settings/parcels.
The Settings/Parts API from Accela — 2 operation(s) for settings/parts.
The Settings/Pick Lists API from Accela — 2 operation(s) for settings/pick lists.
The Settings/Priorities API from Accela — 1 operation(s) for settings/priorities.
The Settings/Professsionals API from Accela — 3 operation(s) for settings/professsionals.
The Settings/Records API from Accela — 8 operation(s) for settings/records.
The Settings/Reports API from Accela — 3 operation(s) for settings/reports.
The Settings/Time Accounting API from Accela — 2 operation(s) for settings/time accounting.
Shopping carts allow public users to add and manage multiple record payment transactions.A shopping cart contains attributes indicating the payment processing type and whether t...
For general time accounting, Civic Platform provides the ability for employees to record the amount of time spent in performing their daily tasks, the descriptions and costs of ...
Agency customers can deposit money into a trust account that the customer can drawn from when they need to pay fees for an application. This is helpful for customers that have a...
**Agency Users** Although "users" is a broad and general term, the Accela API's User object (user API resource) represents the agency user. An agency user is a staff member of t...
**Workflow Tasks** A workflow is a sequence of tasks that agency users follow to process a record. When a user submits a new application, the system creates a record of a certai...
The Oauth2 API from Accela — 3 operation(s) for oauth2.
The Document Review API supports integration of the Civic Platform's Electronic Document Review ("EDR") feature with third-party document review tools.
Published pricing tiers and plan structures.
Documented rate limits and quota policies.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
OAuth scopes governing access to this provider's APIs.
aid: accela
name: Accela
description: Accela is a San Ramon, California govtech company whose cloud Civic Platform runs permitting, planning, licensing,
code enforcement, inspections, asset management and citizen service requests for state and local government agencies worldwide.
Its public developer surface is the Accela Construct API (V4) — a 417-operation REST API served from apis.accela.com and
documented as fifteen Swagger 2.0 documents on the Accela Developer Portal, covering records, inspections, contacts and
professionals, addresses/parcels/owners, assets and assessments, documents, payments and shopping carts, reports, search,
citizens, CivicID and platform settings. Access is OAuth 2.0 against auth.accela.com with agency- and environment-scoped
tokens, and every request is bound to a specific government tenant through the x-accela-agency and x-accela-environment
headers.
url: https://raw.githubusercontent.com/api-evangelist/accela/refs/heads/main/apis.yml
image: https://www.accela.com/wp-content/uploads/2026/07/AccelaLogo-website.webp
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-09-06'
modified: '2026-09-06'
position: Producing
tags:
- GovTech
- Government
- Permitting
- Licensing
- Code Enforcement
- Inspection
- Asset Management
- Citizen Engagement
- Land Management
- Civic Platform
- Public Sector
- Software-as-a-Service
tags_raw:
- govtech
- government
- permitting
- licensing
- code-enforcement
- inspections
- asset-management
- citizen-engagement
- land-management
- civic-platform
- public-sector
- saas
apis:
- name: CivicData Open Data API (CKAN) — END OF LIFE
description: 'CivicData.com is Accela''s free open-data platform for government agencies, described on its own site as "a
free open data platform built by Accela" and "Built on open source using CKAN". It exposes a live CKAN 2.9.9 Action API
— package_list, package_search, status_show, datastore and the spatial extensions — publishing agency datasets such as
building permits, inspections, food-facility records and air-quality permits. IT IS BEING SWITCHED OFF: the site states
CivicData reached end of life on 30 June 2026 and will be removed after 31 December 2026. Recorded here because it is
a real, callable, first-party API today and because CKAN is a named standard in the government regulatory regime — but
do not build on it.'
humanURL: https://www.civicdata.com/
baseURL: https://www.civicdata.com/api/3
tags:
- Open Data
- CKAN
- Government
- Public Sector
tags_raw:
- open-data
- ckan
- government
- public-sector
properties:
- type: Documentation
url: https://www.civicdata.com/
- type: Conformance
url: conformance/accela-conformance.yml
- aid: accela:accela-aa-version-api
name: Accela AA Version API
description: This is to return the version number of the AA server that is running, which allows the mobile app to make
decisions as to what API's they have available.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- AA Version
properties:
- type: OpenAPI
url: openapi/accela-aa-version-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-addresses-api
name: Accela Addresses API
description: An address provides details about the physical location of a parcel, building, contact, and so forth. An address
is part of a property's APO (address, parcel, owner) information that is typically associated to a record. Addresses are
stored as reference data that can be attached to transaction objects.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Addresses
properties:
- type: OpenAPI
url: openapi/accela-addresses-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-agencies-api
name: Accela Agencies API
description: The Agencies API from Accela — 5 operation(s) for agencies.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Agencies
properties:
- type: OpenAPI
url: openapi/accela-agencies-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-announcements-api
name: Accela Announcements API
description: The **announcements** API endpoints allow apps to get agency and public announcements, and mark them as read
announcements.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Announcements
properties:
- type: OpenAPI
url: openapi/accela-announcements-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-app-settings-api
name: Accela App Settings API
description: App settings are defined when a developer registers the app on [Accela Developer Portal](https://developer.accela.com).
These settings include app name, ID, and so forth.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- App Settings
properties:
- type: OpenAPI
url: openapi/accela-app-settings-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assessments-api
name: Accela Assessments API
description: 'In Civic Platform, an assessment is synonymous to an asset condition assessment. An asset condition assessment
is a scheduled maintenance review and/or a quality review of a group of assets. Agencies may require such assessments
for many different asset types such as vehicles, buildings, and water lines. Agencies may set different intervals for
different asset types as well. For example, agency vehicles might require safety and emissions inspections yearly, while
water lines might require an assessment every three months.
In Civic Platform, an assessment is created based on its assessment type. An assessment type defines the assessment''s
custom attributes, rating types, and observation attributes.'
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assessment
tags_raw:
- Assessments
properties:
- type: OpenAPI
url: openapi/accela-assessments-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assessments-attributes-api
name: Accela Assessments/Attributes API
description: An agency can define custom attributes for each type of assessment.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assessments/Attributes
properties:
- type: OpenAPI
url: openapi/accela-assessments-attributes-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assessments-documents-api
name: Accela Assessments/Documents API
description: Inspectors can attach documents and photos as needed to the asset condition assessment record, and record the
assignments and costs that occur on the assessment.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assessments/Documents
properties:
- type: OpenAPI
url: openapi/accela-assessments-documents-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assessments-observations-api
name: Accela Assessments/Observations API
description: During an assessment, an inspector may make observations about the condition of the asset. For example, he
may go to a certain area to look at the condition of the sidewalk and determine if there any cracks or whether the sidewalk
is level. The inspector also looks at the area around the section sidewalk to determine whether trees or brushes block
the walking path. After the inspector completes the assessment, the inspector can log his findings assessment observation,
which he can modify later as more information becomes available.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assessments/Observations
properties:
- type: OpenAPI
url: openapi/accela-assessments-observations-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assessments-work-orders-api
name: Accela Assessments/Work Orders API
description: Asset assessments often alert agencies to problems that need attention. A work order is the starting point
in the repair process. Associating a work order with an assessment helps track the work order's progress.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assessments/Work Orders
properties:
- type: OpenAPI
url: openapi/accela-assessments-work-orders-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assets-api
name: Accela Assets API
description: '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:
<br/>- **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.<br/>- **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.''<br/>-
**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.<br/>- **Polygon** - The polygon class type includes assets such as water drainage
area, a storm drainage area, or a catch basin.'
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assets
properties:
- type: OpenAPI
url: openapi/accela-assets-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assets-assessments-api
name: Accela Assets/Assessments API
description: Condition assessments apply to assets that change or deteriorate over time. These assets may require a visual
condition assessment to effectively manage their life cycle. Transaction records and documents can also be attached to
assets. In Civic Platform, an asset is created based on its asset type. An asset type can be associated to specific work
order types ("record types"), rating types, and usage types.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assets/Assessments
properties:
- type: OpenAPI
url: openapi/accela-assets-assessments-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assets-attributes-api
name: Accela Assets/Attributes API
description: In addition to these asset properties, assets can also have custom attributes which are customized characteristics
of assets, structures, and establishments. Asset custom attributes can be grouped into a template, which can be used to
create an asset. In addition to custom attributes, asset attribute data can be collected into an attribute table.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assets/Attributes
properties:
- type: OpenAPI
url: openapi/accela-assets-attributes-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assets-documents-api
name: Accela Assets/Documents API
description: Document collaterals can be attached to assets.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assets/Documents
properties:
- type: OpenAPI
url: openapi/accela-assets-documents-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-assets-records-api
name: Accela Assets/Records API
description: Assets can be associated to transactional records when an asset assessment necessitates a service work order
or if an application pertains to an agency asset.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Assets/Records
properties:
- type: OpenAPI
url: openapi/accela-assets-records-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-batch-api
name: Accela Batch API
description: API for batch API requests.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Batch
properties:
- type: OpenAPI
url: openapi/accela-batch-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-citizen-access-delegate-invitations-api
name: Accela Citizen Access Delegate Invitations API
description: A citizen user designates a delegate by first sending them an invitation. The invited citizen users can accept
or reject invitations. When the invited citizen users accept the invitation, they officially become the delegate of the
users who invited them. A delegate can work on another citizen user�s data based on the granted permissions.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Citizen Access Delegate Invitations
properties:
- type: OpenAPI
url: openapi/accela-citizen-access-delegate-invitations-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-citizen-access-delegate-management-api
name: Accela Citizen Access Delegate Management API
description: description here
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Citizen Access Delegate Management
properties:
- type: OpenAPI
url: openapi/accela-citizen-access-delegate-management-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-citizen-access-self-registration-api
name: Accela Citizen Access Self-Registration API
description: The **citizenaccess** API endpoints allow a logged-in Citizen Access user to register and manage his or her
own account profile, status, and contacts.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Citizen Access Self-Registration
properties:
- type: OpenAPI
url: openapi/accela-citizen-access-self-registration-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-citizen-access-user-management-api
name: Accela Citizen Access User Management API
description: description here
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Citizen Access User Management
properties:
- type: OpenAPI
url: openapi/accela-citizen-access-user-management-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-civicid-api
name: Accela Civic ID API
description: The CivicId API from Accela — 3 operation(s) for civicid.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- CivicId
properties:
- type: OpenAPI
url: openapi/accela-civicid-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-conditions-api
name: Accela Conditions API
description: "**Conditions**\n\n\n\t\tThe system provides standard conditions\n\t\tfor different record types(permits, licenses,\
\ inspections, and so forth). Depending on the condition,\n\t\tcondition violations result in one of the following automatic\
\ settings to be applied to the inspections: <br/>- **Lock** : Prevents almost any operation,\n\t\texcept operations that\
\ result in removal of the lock,\n\t\tfrom occurring.\n\t\t<br/>- **Hold** : Restricts the addition of an activity and\
\ editing of components.\n\t\t<br/>- **Notice** : Indicates special instructions to the person that completes the application.\
\ The system displays a message when you open the application or any component associated with the application. This condition\
\ does not impede record processing.\n\t\t<br/>- **Required** : Indicates that you must complete a specified activity\
\ or field before proceeding to the next step in a workflow.\n\t\t\n\n **Example Use Case** \n\n\n\t\tA drainage study\
\ must occur prior to approval of a building permit\n\t\tfor new development. In this example,\n\t\tthe drainage study\
\ requirement comprises the standard condition.You create the standard condition,\n\t\tname it D01 Drainage Study,\n\t\
\tand associate it with the Building/Building Permit/Drainage/Grading record type. When a user creates a new permit application\
\ of the Building/Building Permit/Drainage/Grading record type,\n\t\tthe D01 Drainage Study condition applies to the new\
\ application record.\n\n\n\t\tThe system uses conditions at the record level and record component level.Any condition\
\ you place on a component,\n\t\tsuch as a record address,\n\t\tparcel,\n\t\towner,\n\t\tlicensed professional,\n\t\t\
contact,\n\t\tstructure,\n\t\testablishment,\n\t\tor asset,\n\t\taffects any record that references the component.\n\n\
\ **Conditions of Approval** \n\nConditions of approval consist of a list of predefined requirements that must be met\
\ in order to receive approval\n\t\tfor an inspection."
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Conditions
properties:
- type: OpenAPI
url: openapi/accela-conditions-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-contacts-addresses-api
name: Accela Contacts/Addresses API
description: The Contacts/Addresses API from Accela — 2 operation(s) for contacts/addresses.
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Contacts/Addresses
properties:
- type: OpenAPI
url: openapi/accela-contacts-addresses-api-openapi.yml
- type: Documentation
url: https://developer.accela.com/docs/
- type: APIReference
url: https://developer.accela.com/docs/api_reference/api-index.html
- type: Conventions
url: conventions/accela-conventions.yml
- type: ErrorCatalog
url: errors/accela-problem-types.yml
- type: DataModel
url: data-model/accela-data-model.yml
- type: Documentation
url: https://developer.accela.com/docs/construct-apiAuth.html
- type: Authentication
url: authentication/accela-authentication.yml
- type: OAuthScopes
url: scopes/accela-scopes.yml
- aid: accela:accela-contacts-api
name: Accela Contacts API
description: "A reference contact captures information about people or organizations involved in a business process. Contacts\
\ include licensed professionals, such as contractors, architects, engineers, and developers for which your agency maintains\
\ saved data. Contacts also include individuals related to a specific application or parcel, such as the applicant, billing\
\ contacts, or legal representatives.\n\n You can add new contacts to your system, or update information about existing\
\ contacts. As you manage\napplications and parcels on your system, you can keep track of certain individuals related\
\ to an application or a parcel. For example, you can keep track of the legal counsel for a property owner, or the accountant\
\ responsible for any fees assessed on a certain application."
humanURL: https://developer.accela.com/docs/api_reference/api-index.html
baseURL: https://apis.accela.com
tags:
- Contacts
properties:
- type: OpenAPI
url: openapi/accela-contacts-api-openapi.yml
# --- truncated at 32 KB (124 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/accela/refs/heads/main/apis.yml
Every provider here is available over the APIs.io API and to AI agents over MCP.
Kin Score
How this is scored →