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 Documents API

A **Document** is a file attached to one or more **Buildings** (certificates, leases and similar). Documents can be uploaded, downloaded, given an external id, have their metadata read and updated, and be deleted; a `file-events` feed reports document changes over a time range. Metadata edits and deletion apply to API-sourced documents.

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

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

This API exposes 7 operations across 5 paths, and defines 31 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.

7 operations 5 paths 31 schemas 1 DELETE3 GET1 PATCH2 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 Documents 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 7

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

Documents 7

A Document is a file attached to one or more Buildings (certificates, leases and similar). Documents can be uploaded, downloaded, given an external id, have their metadata read an…

GET
/file-events/
Get File Events
get_file_events_file_events__get 2 params → 200422
DELETE
/files/
Delete File
delete_file_files__delete 1 param → 204422
POST
/files/
Upload File
upload_file_files__post body → 201422
GET
/files/metadata/
Get File Metadata
get_file_metadata_files_metadata__get 1 param → 200422
PATCH
/files/metadata/
Patch File Metadata
patch_file_metadata_files_metadata__patch 1 param body → 200422
GET
/files/{file_id}/
Get File
get_file_files__file_id___get 1 param → 200422
POST
/files/{file_id}/external-id/
Create File External Id
create_file_external_id_files__file_id__external_id__post 1 param body → 200422

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are FileGetAttributes (9 properties), FileMetadataAttributes (8 properties), DocumentEventRecord (7 properties), Error (5 properties). Each schema is shown below with its type and property counts.

DocumentEventType
string
FileMetadataUpdateRequest
object
1 property 1 required
BaseDataSchema
object
4 properties 2 required
ExternalIdAttributes
object
2 properties 2 required
FileUploadResponse
object
4 properties 1 required
ExternalIdRequest
object
1 property 1 required
ExternalIdRequestAttributes
object
1 property 1 required
DocumentEventData
object
4 properties 2 required
FileGetResponse
object
4 properties 1 required
FileGetData
object
4 properties 2 required
HTTPValidationError
object
1 property
DocumentEventRecord
object
7 properties 7 required
FileMetadataData
object
4 properties 2 required
ResourceType
string
FileMetadataAttributes
object
8 properties 8 required
DocumentType
string
ValidationError
object
5 properties 3 required
FileUploadData
object
4 properties 1 required
DocumentSource
string
Body_upload_file_files__post
object
1 property 1 required
ExternalIdResponse
object
4 properties 1 required
ExternalIdData
object
4 properties 2 required
FileGetAttributes
object
9 properties 9 required
DocumentEventsResponse
object
4 properties 1 required
FileMetadataUpdateAttributes
object
3 properties
FileMetadataResponse
object
4 properties 1 required
ExternalIdRequestData
object
2 properties 1 required
Links
object
2 properties 2 required
DocumentEventAttributes
object
4 properties 4 required
Error
object
5 properties
FileMetadataUpdateData
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alasco-documents-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 Documents 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.