/v1/service/@id/os-templatesOS templates for VPS rebuild
OS templates this VPS can be rebuilt with: one row per name, ordered by family (Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS, Fedora, Windows, other), clean installs before app images, newest first. id is the template value to send when rebuilding (POST /v1/service/@id/vms/@vmid/rebuild); kind is os or app (with an app, named in app); eol: past end of support; recommended: the newest supported clean install of each family; current: the template currently installed, or null.
Call it through the gateway https://api.tino.vn/v1 with a token that has the services:read scope; see Calling the Tino API.
Authentication
Send the token in the header Authorization:
Authorization: Bearer <token>
Tokens that can call it: app tokens (tinoat_, Sign in with Tino) or personal API tokens (tinopat_).
Scopes
services:readView services, including service login details
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | int | Required | Service ID |
Response
No live sample: the route changes real data or the test account has no data for it. The answer is a JSON object; errors follow the common shape in Calling the Tino API.
Error codes
| Error code | Description |
|---|---|
401 · invalid_token | The token is wrong, expired or revoked. |
403 · insufficient_scope | The token lacks the services:read scope. |
403 · ip_not_allowed | A personal API token called from an IP outside its allow-list. |
Business errors of a route usually come as HTTP 200 with {"error": ["<code>"]}; see common error codes.