API & Automation FAQs
This page covers common questions about the CloudRaya API.
For the full endpoint reference, request/response formats, and code samples, see the CloudRaya API Reference.
Q: Is the CloudRaya API available?
A:
Yes. The CloudRaya API is live and covers compute, networking, storage, Kubernetes, container registry, billing, and more.
See the CloudRaya API Reference for the full list of services and endpoints.
Q: What can I use the API for?
A:
The API lets you integrate CloudRaya into your own systems and workflows, such as:
- Automating routine platform operations instead of using the Control Panel
- Connecting CloudRaya to internal tools, dashboards, or customer portals
- Building custom provisioning and reporting workflows
Q: How does authentication work?
A:
The API authenticates with a bearer token, not a separate API key.
Exchange your CloudRaya account e-mail and password for a token via the login endpoint on the Core
service, then send that token on every other request as an Authorization: Bearer <token> header.
The token expires after a limited time (currently around two hours); once it does, log in again
for a new one.
There is no separate API key to create or manage, this uses the same account credentials you use to log in to the Control Panel. See the Reference's Authentication page for the exact request format.
Q: Is there a rate limit?
A:
If you run into rate limiting or have questions about usage limits for your account, contact CloudRaya Support. Current limits aren't published here since they may change.
Q: Will API behavior differ between the old panel and CloudRaya New Panel?
A:
Yes. The CloudRaya API documented here is built for CloudRaya New Panel and is a separate, independently versioned interface from the old panel's API.
If you have automation or integrations built against the old panel's API, review and test them against the new endpoints, request/response formats, and authentication model before relying on them in production.
Q: Is it safe to use automation in production?
A:
Automation can be powerful but also risky if not designed carefully. Recommended practices:
- Test automation against a non-production project first
- Add safeguards or manual approval steps before destructive actions (delete, resize down, etc.)
- Keep credentials and tokens out of source control and client-side code
Learn More
📄 API & Automation (what the API is for and how authentication works)
📄 CloudRaya API Reference (full endpoint documentation)