If you manage infrastructure with scripts and code rather than clicks, the client area now meets you there. You can generate API tokens for your cloud service and manage it from Terraform, both self-serve.
API tokens
The API page in your cloud service shows your connection details and generates tokens with an expiration you choose. Tokens authenticate as username:token. Each one appears once at creation, and you can revoke it the moment you stop needing it. That is exactly how automation credentials should behave.
Use them from scripts, CI pipelines, or anything else that talks to the API. Keep your account password out of it.
Terraform
The Terraform page hands you a ready-to-use provider configuration. Copy it, drop in a token, and start defining VMs, volumes, and networks as code. Provider documentation and a security checklist sit right on the page: keep credentials in environment variables, protect your state file.
Why infrastructure-as-code
A Terraform config is documentation that cannot drift: the environment is what the code says it is. Rebuilding staging stops being an afternoon of remembering and becomes terraform apply.
If you have wanted a reason to move your Togglebox resources into code, the on-ramp is built in now. You will find both pages under API in your cloud service sidebar.
