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

Alasco Utility Meters API

A **Utility Meter** measures consumption (electricity, gas, water, heating or cooling) for a **Building**. Meters are created and updated through the API, identified by your `external_id`, and own their **Readings** and consumption data.

Alasco Utility Meters API is one of 40 APIs that Alasco publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Utility Meters. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 5 operations across 5 paths, and defines 36 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.alasco.de/capex/v1.

5 operations 5 paths 36 schemas 1 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.alasco.de/fincon/v1
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Alasco Utility Meters API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-KEY (API_Key). An API key is passed in the header as X-API-TOKEN (API_Token).

  • API_Key — The Alasco API uses a combination of API keys and API tokens to authenticate requests. The API key needs to be sent in a header field called X-API-KEY.
  • API_Token — In addition to an API key, one has to specify an API token. There can be one or more tokens in use for the same API key. The token needs to be sent in a header…

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 1 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Utility Meters 5

A Utility Meter measures consumption (electricity, gas, water, heating or cooling) for a Building. Meters are created and updated through the API, identified by your externalid, a…

GET
/buildings/{building_uuid}/utility-meters/
Get Utility Meters
get_utility_meters_buildings__building_uuid__utility_meters__get 1 param → 200422
POST
/utility-meters/
Add Utility Meter
add_utility_meter_utility_meters__post body → 201422
POST
/utility-meters/bulk-import-partial/
Bulk Add Utility Meter Import Partial
bulk_add_utility_meter_import_partial_utility_meters_bulk_import_partial__post body → 207422
POST
/utility-meters/import/
Add Utility Meter Import
add_utility_meter_import_utility_meters_import__post body → 201422
PATCH
/utility-meters/{meter_external_id}/
Update Utility Meter
update_utility_meter_utility_meters__meter_external_id___patch 1 param body → 200422

Schemas 36

The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are UtilityMeterWrite (15 properties), UtilityMeterAttributes (13 properties), UtilityMeterPatchAttributes (12 properties), UtilityMeterImportWrite-Output (10 properties). Each schema is shown below with its type and property counts.

Units
string
UtilityMeterImportPayload
object
1 property 1 required
BaseDataSchema
object
4 properties 2 required
UtilityMeterAttributes
object
13 properties 12 required
CoolingSystem
string
UtilityMeterPayload
object
1 property 1 required
UtilityMeterPatchAttributes
object
12 properties
UtilityMeterListResponse
object
4 properties 1 required
HTTPValidationError
object
1 property
UtilityMeterResponse
object
4 properties 1 required
UtilityMeterImportStatus
string
UtilityMeterPatchPayload
object
1 property 1 required
UtilityMeterImportBulkPayload
object
1 property 1 required
SubCategory
string
UtilityMeterImportWrite-Input
object
10 properties 5 required
UtilityMeterImportAttributes
object
10 properties 10 required
alasco__ivy__public__api__utilities__utility_meter_imports__ErrorDetail
object
3 properties 3 required
UtilityMeterImportCreateErrorCode
string
ResourceType
string
ValidationError
object
5 properties 3 required
HeatingSystem
string
alasco__ivy__public__api__utilities__utility_meter_imports__BulkError
object
3 properties 3 required
UtilityMeterImportData
object
4 properties 2 required
UtilityMeterPatchPayloadData
object
2 properties 2 required
UtilityMeterData
object
4 properties 2 required
UtilityMeterImportResponse
object
4 properties 1 required
UtilityMeterWrite
object
15 properties 5 required
ProcuredBy
string
Links
object
2 properties 2 required
Utility
string
BulkPartialUtilityMeterImportResponse
object
4 properties 1 required
UtilityMeterImportCreatePayloadData
object
2 properties 2 required
UtilityMeterCreatePayloadData
object
2 properties 2 required
BulkPartialUtilityMeterImportData
object
3 properties 2 required
Error
object
5 properties
UtilityMeterImportWrite-Output
object
10 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alasco-utility-meters-api-openapi.yml Raw ↑

Other APIs Alasco publishes across the network.

Alasco Annual Consumption API
Alasco Asset API
Alasco Audit Log API
Alasco Budget Shift API
Alasco Buildings API
Alasco Cash Outflow Cost Element View API
Alasco Change Order API
Alasco Change Order Document API
Alasco Consumption Intervals API
Alasco Contact API
Alasco Contract API
Alasco Contract Document API
Where this information came from

This is an independent, third-party profile of Alasco Utility Meters 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.