Rate Limits
To ensure platform stability, security and service quality, DevHub API applies multiple layers of rate limiting to its infrastructure and APIs.
These limits are used to prevent abuse, protect the platform from automated attacks and ensure fair usage of resources among all users.
1. Global Infrastructure Protection
All requests sent to DevHub API are protected by an infrastructure-level rate limiting system applied through the application server.
This protection layer is independent from API license tiers and is globally applied to all incoming requests.
| Type | Limit | Scope | Behavior |
|---|---|---|---|
| Global infrastructure protection | 240 requests per minute | Per IP address | HTTP 429 response when exceeded |
This mechanism is mainly used to mitigate abnormal activity, abuse attempts, automated attacks and brute force scenarios.
2. API Rate Limits
In addition to the global infrastructure protection layer, DevHub API applies additional API-specific limits based on the license assigned to each endpoint.
Limits may vary depending on the required license tier and are managed at application level.
The required license for each endpoint is always specified within the official OpenAPI / Swagger documentation.
Currently, license-based rate limits are automatically renewed on the first day of each month.
3. Currently Available Licenses
| License | Description | Rate Limit |
|---|---|---|
| FREE | Access to the public APIs currently available on the platform. | 1000 requests per month for each API |
| BASIC | Future license with extended limits. | Coming soon |
| PRO | Future license dedicated to advanced APIs and higher throughput. | Coming soon |
| PLATINUM | Future custom solutions with dedicated limits. | Future availability |
4. Currently Available APIs
At the moment, all public APIs available on the platform belong to the FREE license tier.
| API Category | Current License |
|---|---|
| Data Conversion APIs | FREE |
| Utility APIs | FREE |
| Validation APIs | FREE |
In the future, APIs belonging to the same category may require different license tiers.
For this reason, the required license should always be verified directly within the endpoint documentation.
5. Limit Exceeded
When a limit is exceeded, DevHub API returns an HTTP 429 - Too Many Requests response.
When limits are exceeded, users are advised to reduce request frequency and retry after an appropriate interval.
{
"error": "Too Many Requests: you have exceeded your rate limit.",
"status": 429,
"path": "/api/v1/example/api-called",
"requestId": "d7032406-b49e-4786-96cc-42cda8dc6e45",
"supportCode": "SC_001",
"timestamp": "2026-01-11T15:42:10.123"
}
6. API Documentation
The OpenAPI / Swagger documentation for each endpoint specifies:
- required license
- authentication requirements
- usage restrictions
- technical endpoint details
The official OpenAPI / Swagger documentation is available here.
For additional details, always refer to the official technical documentation of the APIs being used.