openapi: 3.1.0 info: description: ' ## Introduction The **CAPEX API** enables you to integrate your application with the CAPEX system. The CAPEX API is REST-based and follows JSON:API principles for structuring responses. Starting from version 1.0, the API is stable. We are continuously improving our API, and new endpoints will be added. Any updates or changes within this major version will be backward-compatible and can be found in this documentation. For getting access to the CAPEX API, please reach out to us at: `kontakt@alasco.de`. The base URL for all endpoints is: `https://api.alasco.de/capex/v1` The CAPEX API supports compressed payloads. If you would like to make use of this, you have to specify the `Accept-Encoding` header. Supported encodings are `gzip` and `br`. ### Domain model Objects relate as follows (each `→` is a navigable sub-resource): - **Assets** and **Measures** are the CapEx-specific top-level objects; a **Measure** → **Contracts**, and invoices are submitted against an **Asset**. - **Contractor** and **Contracting Entity** → **Contracts**. - **Contract** → **Change Orders**, **Invoices**, contract terms, **Documents** and **Custom Fields**. - **Invoice** → **Documents** and **Tags** (Change Orders also carry **Documents**). ### CAPEX API Overview The CAPEX API provides endpoints to: - Retrieve and manage invoices, invoice tags, and invoice documents - Retrieve assets, contracts, contractors, and measures The CAPEX API uses pagination. The page size is 100, and additional pages can be accessed using a `next` link. ' title: CAPEX Annual Consumption Measure API version: '1.0' x-logo: url: https://assets-global.website-files.com/656ef2eb27ad41897248f866/659eebec190ae7aaf4162f09_Logotype_Alasco_white_RGB%202.png servers: - url: https://api.alasco.de/capex/v1 tags: - description: A **Measure** is a planned package of capital work on an **Asset** (for example a renovation or a fit-out), carrying a status, category and priority. Measures are read-only here and group the **Contracts** through which the work is executed (`GET /measures/{id}/contracts/`). name: Measure paths: /measures/: get: operationId: get_measures_measures__get parameters: - description: ' List endpoint responses are paginated in the Alasco API. By calling the endpoint without the pagination parameter you will receive the first page. If not all elements fit on one page there will be a `next` link provided in the response''s `links` object. By calling this link you will receive the next page. ' in: query name: cursor[position] required: false schema: anyOf: - type: string - type: 'null' description: ' List endpoint responses are paginated in the Alasco API. By calling the endpoint without the pagination parameter you will receive the first page. If not all elements fit on one page there will be a `next` link provided in the response''s `links` object. By calling this link you will receive the next page. ' title: Cursor[Position] - description: ' You can filter on certain attributes by specifying them as a GET parameter along with an operation, e.g. `filter[name.exact]=abc`. Currently supported operations are: * `exact`: Expects one value * `contains`: Expects one value * `less_than_equal`: Expects one value * `greater_than_equal`: Expects one value * `range`: Expects two values * `in`: Expects one or multiple values * `not_in`: Expects one or multiple values The following attributes support filtering: | **Attribute** | `exact` | `contains` | `less_than_equal` | `greater_than_equal` | `range` | `in` | `not_in` | | :--- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | | `id` | | | | | | x | x | | `name` | x | x | | | | | | | `identifier` | x | x | | | | | | | `description` | x | x | | | | | | | `date_created` | | | x | x | x | | | | `status` | | | | | | x | x | | `asset` | | | | | | x | x | ' in: query name: filter[attribute.operation] required: false schema: anyOf: - type: string - type: 'null' description: ' You can filter on certain attributes by specifying them as a GET parameter along with an operation, e.g. `filter[name.exact]=abc`. Currently supported operations are: * `exact`: Expects one value * `contains`: Expects one value * `less_than_equal`: Expects one value * `greater_than_equal`: Expects one value * `range`: Expects two values * `in`: Expects one or multiple values * `not_in`: Expects one or multiple values The following attributes support filtering: | **Attribute** | `exact` | `contains` | `less_than_equal` | `greater_than_equal` | `range` | `in` | `not_in` | | :--- | :---: | :---: | :---: | :---: | :---: | :---: | :---: | | `id` | | | | | | x | x | | `name` | x | x | | | | | | | `identifier` | x | x | | | | | | | `description` | x | x | | | | | | | `date_created` | | | x | x | x | | | | `status` | | | | | | x | x | | `asset` | | | | | | x | x | ' title: Filter[Attribute.Operation] responses: '200': content: application/json: schema: $ref: '#/components/schemas/ListResponse' description: Successful Response '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error security: - API Key: [] - API Token: [] summary: Get Measures tags: - Measure /measures/{id}/: get: operationId: get_measure_measures__id___get parameters: - in: path name: id required: true schema: format: uuid title: Id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/MeasureDetailResponse' description: Successful Response '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error security: - API Key: [] - API Token: [] summary: Get Measure tags: - Measure components: schemas: HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object Attributes: properties: asset: description: '**Asset** · **Asset**' format: uuid title: Asset type: string date_created: description: '**Date created** · **Erstellt am**' format: date-time title: Date Created type: string description: anyOf: - type: string - type: 'null' description: '**Description** · **Beschreibung**' title: Description identifier: description: '**Identifier** · **Kennung**' title: Identifier type: string name: description: '**Name** · **Name**' maxLength: 250 title: Name type: string status: $ref: '#/components/schemas/MeasureStatus' description: '**Status** · **Status** Available values / Verfügbare Werte: | Value | English | Deutsch | | --- | --- | --- | | `BUDGETED` | Budgeted | Budgetiert | | `IN_PROGRESS` | In progress | In Umsetzung | | `COMPLETED` | Completed | Abgeschlossen |' examples: - BUDGETED required: - name - identifier - description - date_created - status - asset title: Attributes type: object MeasureData: properties: attributes: $ref: '#/components/schemas/Attributes' id: format: uuid title: Id type: string relationships: anyOf: - additionalProperties: true type: object - type: 'null' description: ' Contains links to related objects. ' examples: - asset: data: id: 9e77da78-ee18-4cac-b643-8bbd092a5bae type: ASSET title: Relationships type: default: MEASURE title: Type type: string required: - id - attributes title: MeasureData type: object BaseDataSchema: properties: attributes: anyOf: - {} - type: 'null' title: Attributes id: format: uuid title: Id type: string relationships: anyOf: - additionalProperties: true type: object - type: 'null' title: Relationships type: title: Type type: string required: - id - type title: BaseDataSchema type: object Error: properties: detail: anyOf: - type: string - type: 'null' title: Detail source: anyOf: - additionalProperties: type: string type: object - type: 'null' title: Source status: anyOf: - type: string - type: 'null' title: Status title: anyOf: - type: string - type: 'null' title: Title title: Error type: object ValidationError: properties: ctx: title: Context type: object input: title: Input loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object MeasureDetailResponse: properties: data: $ref: '#/components/schemas/MeasureData' errors: anyOf: - items: $ref: '#/components/schemas/Error' type: array - type: 'null' title: Errors included: anyOf: - items: $ref: '#/components/schemas/BaseDataSchema' type: array - type: 'null' title: Included links: anyOf: - additionalProperties: anyOf: - type: string - type: 'null' type: object - type: 'null' title: Links required: - data title: MeasureDetailResponse type: object MeasureStatus: enum: - BUDGETED - IN_PROGRESS - COMPLETED title: MeasureStatus type: string ListResponse: properties: data: items: $ref: '#/components/schemas/MeasureData' title: Data type: array errors: anyOf: - items: $ref: '#/components/schemas/Error' type: array - type: 'null' title: Errors included: anyOf: - items: $ref: '#/components/schemas/BaseDataSchema' type: array - type: 'null' title: Included links: anyOf: - additionalProperties: anyOf: - type: string - type: 'null' type: object - type: 'null' description: ' Contains the pagination''s next link if results don''t fit on one page. ' title: Links required: - data title: ListResponse type: object securitySchemes: API Key: description: ' 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`. ' in: header name: X-API-KEY type: apiKey API Token: description: ' 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 field called `X-API-TOKEN`. Right now, it''s not possible to create API keys and API tokens from within Alasco. If you are interested in using the Alasco API, please reach out to the [support team](mailto:support@alasco.de). They will assist you in generating a key and token pair. ' in: header name: X-API-TOKEN type: apiKey