Skip to main content
Every Basaltic API is addressed by service, on its own hostname. There is no single API gateway host.

​
Region codes

A region code is <continent>-<metro>-<n> — the geographic prefix is a strict continent, and the metro token is what carries the legal jurisdiction your data sits in. GET https://iam.basaltic.sh/v1/regions returns the live catalogue. It needs no authentication, so it is a safe first call to confirm connectivity.

​
Global and regional services

Your account, its identity and its bill are global — one of each, wherever you build. The resources you create are regional, and so are most of the APIs that manage them.
Addressed as https://<service>.<region>.basaltic.sh, for example https://compute.sa-saopaulo-1.basaltic.sh.Sign these with the region code in the credential scope.

​
Object storage

S3-compatible object storage is the one endpoint that is not on basaltic.sh:
It sits on a separate domain deliberately, off the product domain, because it is driven by ordinary AWS SDKs and signed as S3 rather than with the Basaltic scheme. Point any S3 client at it as a custom endpoint. The management side of storage — volumes, snapshots, bucket lifecycle — is on storage.<region>.basaltic.sh with the rest of the platform API.

​
Choosing the scope when you sign

The <region> element of the credential scope must match the endpoint you are calling:
Getting this wrong is a 401, not a redirect.