API & Automation FAQs
This page covers common questions about the CloudRaya API and automation capabilities.
The CloudRaya API is currently under active development. The answers below describe the intended design principles and planned behavior, not a final, production-ready interface.
Q: Is the CloudRaya API available today?
A:
The CloudRaya API is currently in development and not yet publicly available for production use.
This page exists to help you understand the direction and design goals of the API so you can prepare your automation and integration plans in advance.
Q: What will the API be used for?
A:
The API is designed to help you integrate CloudRaya into your own systems and workflows, such as:
- Automating routine platform operations
- Connecting CloudRaya with internal tools, dashboards, or portals
- Building custom provisioning and reporting workflows
Exact capabilities and supported services will be published when the API is released.
Q: How will authentication work?
A:
The planned model is to use secure, token-based authentication tied to your CloudRaya account and project context.
Details such as token scopes, expiration, and rotation policies will be documented in the official API guide when the service becomes available.
Q: Will there be breaking changes between old panel and new panel?
A:
Yes. CloudRaya API New panel is a separate and independently versioned interface from old panel.
new panel may introduce:
- Different endpoint structures
- Updated request and response formats
- Changes in authentication and resource models
Applications and automation built for old panel should be reviewed and tested before being adapted to new panel.
CloudRaya will publish API reference documentation and version notes to help teams understand differences and plan their integration strategy.
Q: Will there be rate limits or usage safeguards?
A:
Yes. The API is planned to include rate limiting and operational safeguards to protect the platform and ensure fair usage across all customers.
Specific limits and policies will be published in the API reference.
Q: Is it safe to use automation in production?
A:
Automation can be powerful but also risky if not designed carefully.
Best practices will include:
- Using scoped credentials with limited permissions
- Testing automation in non-production environments
- Adding safeguards and manual approval steps for destructive actions
These practices will be covered in detail in the official automation guides.
Stay Updated
This FAQ will be updated as the API becomes available.
To stay informed:
- Subscribe to CloudRaya product updates
- Or check this page for release announcements
📩 Contact Support: support@wowrack.co.id