The Teploy Cloud REST API — authenticate with a Bearer API key
Every /api/v1 request needs an API key and an organization scope.
Headers
Authorization: Bearer tp_live_... X-Organization-Id: your-org-id
Example
curl https://cloud.teploy.com/api/v1/whoami \ -H "Authorization: Bearer $TEPLOY_KEY" \ -H "X-Organization-Id: $TEPLOY_ORG"
Keys are deny-by-default: each endpoint requires its read:/write: permission on the key. Lists return { items, total } envelopes.
Manage VPS servers across providers
/api/v1/serversList servers/api/v1/servers/{id}Get a server by id/api/v1/serversProvision a server/api/v1/servers/{id}Destroy a server/api/v1/providersList providers and plans/api/v1/providers/{provider}/regionsProvider regions/api/v1/providers/{provider}/sizesProvider sizesPublic keys for new servers (no private key is stored or returned)
/api/v1/ssh-keysList the organization's public keys/api/v1/ssh-keysImport a public key (an existing one is returned as is; 20 per organization)DNS zones and records
/api/v1/dns/zonesList DNS zones/api/v1/dns/recordsCreate a DNS record/api/v1/dns/records/{id}Delete a DNS recordObject storage
/api/v1/storage/presignPresign an upload or download URL