API References
General information for Devora APIs, including base URL, authentication, versioning, and available endpoints.
Welcome to the Devora API documentation. All Devora APIs are RESTful, versioned, and follow the same authentication pattern.
Base URL
The production API is accessible at:
https://devora.my.id[!NOTE] All endpoints are versioned under
/api/v1/. Internal dashboard APIs use/api/without versioning.
Authentication
All endpoints require an API Key in the Authorization header as a Bearer Token.
You can manage your API Keys in the API Key Management section.
Example Header
Authorization: Bearer devora_your_key_hereAvailable APIs
Devora provides the following API services:
| API | Description | Endpoint Prefix |
|---|---|---|
| AI Models | OpenAI-compatible reverse proxy for multiple LLM providers | /api/v1/ai |
| Airdrop | Manage airdrop projects, tasks, and hunting workflows | /api/v1/airdrops |
| Temp Mail | Create and manage temporary email accounts | /api/v1/temp-mail |
Versioning
Devora uses URI versioning. The current version is v1.
/api/v1/ai/models
/api/v1/airdrops
/api/v1/temp-mail/accountsBreaking changes will be introduced in a new version (e.g., v2) with advance notice.
Response Format
All responses are returned as JSON. Successful responses include the requested data, while errors include a standard error object.
Success Response
{
"id": "abc123",
"name": "Example"
}Error Response
{
"error": "Invalid API Key",
"type": "invalid_request_error",
"code": "invalid_api_key"
}HTTP Status Codes
| Status | Meaning | Description |
|---|---|---|
200 | OK | Request succeeded |
201 | Created | Resource created successfully |
400 | Bad Request | Invalid JSON or missing required parameters |
401 | Unauthorized | Missing or invalid API key |
403 | Forbidden | Insufficient permissions |
404 | Not Found | Resource not found |
500 | Internal Server Error | Server-side error occurred |