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

A **Project** is the top-level container for a construction or development engagement. It optionally references a **Property** and a **Cost Element Tree Template**, and organises spend through **Contract Units** and **Contracts**. Projects can be created and updated through the API.

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

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

This API exposes 6 operations across 4 paths, and defines 14 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.

6 operations 4 paths 14 schemas 4 GET1 PATCH1 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 Project 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 6

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

Project 6

A Project is the top-level container for a construction or development engagement. It optionally references a Property and a Cost Element Tree Template, and organises spend throug…

GET
/contracting_entities/{contracting_entity_id}/projects/
Get Projects By Contracting Entity
get_projects_by_contracting_entity_contracting_entities__contracting_entity_id__projects__get 1 param → 200422
GET
/projects/
Get Projects
get_projects_projects__get 2 params → 200422
POST
/projects/
Create Project
create_project_projects__post body → 201422
GET
/projects/{id}/
Get Project Details
get_project_details_projects__id___get 1 param → 200422
PATCH
/projects/{id}/
Update Project
update_project_projects__id___patch 1 param body → 200422
GET
/properties/{property_id}/projects/
Get Projects By Property
get_projects_by_property_properties__property_id__projects__get 1 param → 200422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ProjectAttributes (19 properties), ProjectCreateAttributes (18 properties), ProjectUpdateAttributes (15 properties), ValidationError (5 properties). Each schema is shown below with its type and property counts.

Request_ProjectUpdateAttributes_Literal_PROJECT__
object
1 property 1 required
Response_ProjectAttributes_Literal_PROJECT__
object
4 properties
ListResponse_ProjectAttributes_Literal_PROJECT__
object
4 properties 1 required
HTTPValidationError
object
1 property
ProjectAttributes
object
19 properties 6 required
ProjectUsage
string
Data_ProjectAttributes_Literal_PROJECT__
object
4 properties 3 required
Payload_ProjectUpdateAttributes_Literal_PROJECT__
object
2 properties 2 required
Request_ProjectCreateAttributes_Literal_PROJECT__
object
1 property 1 required
ProjectUpdateAttributes
object
15 properties
ValidationError
object
5 properties 3 required
ProjectCreateAttributes
object
18 properties 3 required
Error
object
4 properties
Payload_ProjectCreateAttributes_Literal_PROJECT__
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alasco-project-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 Project 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.