Projects
CoreCreate and manage the projects that organize your cloud resources.
Route/v1/projects
Use for: setting up a workspace for your integration.
Cloud API documentation
Clear guides, structured endpoints, and practical examples to take you from first read to first response.
Request flow
A clear path to your response
AUTHENTICATION
Bearer token
ENDPOINT
GET /v1/resources
RESPONSE
Useful data, clearly documented
Authentication → endpoint → response
01 / Platform overview
Cloud API gives your application a consistent way to access platform services. Use these docs to understand the surface area, authenticate, and make a working request.
Learn the core concepts and API boundaries.
Configure credentials before calling an endpoint.
Find methods, parameters, and response details.
Adapt working patterns for your integration.
Authentication
Create an API key, keep it private, then send it as a bearer token with each request.
Generate an API key in your project settings and copy it once.
Load the key from a server-side environment variable. Never expose it in browser code.
Include the key in the Authorization header on each API call.
curl https://api.cloud.example/v1/projects \
-H "Authorization: Bearer $CLOUD_API_KEY" \
-H "Content-Type: application/json"
API reference Endpoints
Find the capability you need, then use its routes to shape your first request.
Create and manage the projects that organize your cloud resources.
Route/v1/projects
Use for: setting up a workspace for your integration.
Read and update the records connected to a project.
Route/v1/resources/{id}
Use for: retrieving or changing a specific resource.
Submit long-running work and check its processing status.
Route/v1/jobs
Use for: tracking work that completes asynchronously.
Help & troubleshooting
Quick answers to common questions as you get your first requests running.
Check that your API key is active and sent in the Authorization: Bearer header. Keep keys out of query strings and client-side code.
限Rate-limited requests return 429. Use the response’s Retry-After value and retry with exponential backoff.
Requests use the version configured for your project. Pin a version in production and review the changelog before upgrading.
Use your sandbox credentials to make test requests. Sandbox activity is isolated from live data; switch to live credentials only when you are ready.
Contact support with the request ID, endpoint, and approximate time. Never include secret keys or other credentials in your message.