UpCloud Tag API
User can define a set of free-form tags to group and identify a subsetof their servers. Tags can be for example _webserver_, _database_, _PROD_, _QA_, _DEV_ etc.A server can have several tags. API can be used to return only serversmatching specified tags. Note that all operations changing server'sstate or attributes must still be done individually for each serverUUID, tags can be used only to return a list of servers.__Warning! Consider using labels instead of tags:__ Tags are an access control feature and only available for a limited set of resources. Use labels to describe and filter your resources. Documentation for labels can be found on the resource specific documentation pages.Creating and modifying tags is allowed **only by main account**. Subaccountshave access only to listing tags and tagged servers they are grantedaccess to.
UpCloud Tag API is one of 29 APIs that UpCloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Tag. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 5 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.3.
Requests are made against a single base URL, https://api.upcloud.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
UpCloud Tag API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (apiToken).
By default, every request must be authenticated.
apiToken— UpCloud API uses HTTP Bearer authentication. An API token is required to authenticate. The API token can be created in the UpCloud control panel. Alternatively…
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
User can define a set of free-form tags to group and identify a subset of their servers.
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are tagError409 (1 property), tagError (1 property), tagServers (1 property), tag (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from UpCloud 12
Other APIs UpCloud publishes across the network.
This is an independent, third-party profile of UpCloud 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.