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 Invoice Tag API

An **Invoice Tag** is a coloured label (with a name unique per account) you assign to **Invoices** for organisation and filtering. Tags can be created, updated and deleted, and assigned to or removed from invoices.

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

Tagged areas include Invoice Tag. 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 26 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 26 schemas 1 DELETE2 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 Invoice Tag 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, 2 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Invoice Tag 7

An Invoice Tag is a coloured label (with a name unique per account) you assign to Invoices for organisation and filtering. Tags can be created, updated and deleted, and assigned t…

GET
/invoices/{invoice_id}/tags/
Get Tags By Invoice
get_tags_by_invoice_invoices__invoice_id__tags__get 1 param → 200422
POST
/invoices/{invoice_id}/tags/assign/
Assign Tag
assign_tag_invoices__invoice_id__tags_assign__post 1 param body → 200422
POST
/invoices/{invoice_id}/tags/unassign/
Unassign Tag
unassign_tag_invoices__invoice_id__tags_unassign__post 1 param body → 200422
GET
/tags/
Get Tags
get_tags_tags__get → 200
POST
/tags/
Create Tag
create_tag_tags__post body → 201422
DELETE
/tags/{id}/
Delete Tag
delete_tag_tags__id___delete 1 param → 204422
PATCH
/tags/{id}/
Update Tag
update_tag_tags__id___patch 1 param body → 200422

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are InvoiceAttributes (22 properties), ValidationError (5 properties), Response_TagAttributes_Literal_TAG__ (4 properties), Data_TagAttributes_Literal_TAG__ (4 properties). Each schema is shown below with its type and property counts.

InvoiceAttributes
object
22 properties 3 required
Request_TagAssignAttributes_Literal_TAG__
object
1 property 1 required
TagUpdateAttributes
object
2 properties
BaseDataSchema
object
4 properties 2 required
InvoiceCreatedData
object
4 properties 2 required
TagColorTokenOut
string
Request_TagUpdateAttributes_Literal_TAG__
object
1 property 1 required
Response_TagAttributes_Literal_TAG__
object
4 properties
TagAssignAttributes
object
1 property 1 required
HTTPValidationError
object
1 property
InvoiceType
string
The invoice type.
Data_TagAttributes_Literal_TAG__
object
4 properties 3 required
TagCreateAttributes
object
2 properties 1 required
InvoiceBasicAttributes
object
3 properties 2 required
InvoiceData
object
4 properties 2 required
Payload_TagCreateAttributes_Literal_TAG__
object
2 properties 2 required
ValidationError
object
5 properties 3 required
TagColorTokenIn
string
ListResponse_TagAttributes_Literal_TAG__
object
4 properties 1 required
InvoiceProcessState
string
The invoice process state represents the state of the invoice in its workflow. A NEW invoice has not been processed by any user. An invoice in state DETAILSENT…
InvoiceResponse
object
4 properties
TagAttributes
object
2 properties 2 required
Payload_TagUpdateAttributes_Literal_TAG__
object
2 properties 2 required
Payload_TagAssignAttributes_Literal_TAG__
object
2 properties 2 required
Error
object
4 properties
Request_TagCreateAttributes_Literal_TAG__
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alasco-invoice-tag-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 Invoice Tag 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.