If server lifecycle automation is a purchase requirement, contact support before ordering to confirm the currently supported API, authentication, permissions and service operations.
What to confirm
- The supported API base URL and versioned reference.
- How credentials are issued and revoked, and which services they can access.
- Available operations, rate limits, error behaviour and any additional charges.
- Whether events or webhooks are available and how to validate them.
Plan safe operations
Start with read-only access and a non-production service. Keep tokens outside source control, and require an explicit check before a rebuild, cancellation or other destructive change.
Use the configurator for published purchasing options. Payment verification is automatic; server preparation follows confirmation. That does not imply the availability of a general-purpose provisioning API.