API: Overview
StableWhat API v2 does and how to use it for customer-facing automation.
Updated: April 6, 2026
API v2 is the public HTTP interface of SPG99 for managing accounts, tenants, and databases.
Base URL
https://provisioner.spg99.ru/v2
If your team has a separate environment, use the address shown in Console or in your onboarding materials.
What the API is used for
The API is typically used to:
- create tenants and databases;
- obtain credentials and
dsn_template; - read resource state;
- start database export;
- delete resources that are no longer needed;
- build provisioning and inventory automation.
What the API is not used for
Application PostgreSQL connections do not go to the API. They go to Gateway on :5432. This separation is one of the core SPG99 principles: resource management is separate from SQL traffic.
The standard managed workflow
A normal working path looks like this:
create tenant -> save credentials -> create db -> connect through Gateway
After that, the platform automatically wakes the database on the first connection and returns it to idle after inactivity.
Which fields matter most
For everyday automation, it is usually enough to read:
state;- the database profile;
- connection activity;
- the last usage time.
That gives the customer exactly what they need to know: ready, idle, or needs attention.
