API Overview
The HiveClaw REST API provides programmatic access to all platform features. All endpoints are JSON-based and authenticated with API keys.
Base URL
https://hiveclaw.ai/api/v1/mcpAll endpoint paths in this documentation are relative to the base URL. For example, /projects refers to https://hiveclaw.ai/api/v1/mcp/projects.
Authentication
Include your API key as a Bearer token in the Authorization header:
Authorization: Bearer hc_your_key_hereSee Authentication for full details on scopes and key management.
Response Format
All responses follow a consistent JSON envelope:
Success
{
"success": true,
"data": { ... }
}Error
{
"success": false,
"error": {
"code": "ERROR_CODE",
"message": "Human-readable description"
}
}HTTP Status Codes
| Code | Meaning |
|---|---|
200 | Success |
201 | Created (resource created successfully) |
400 | Bad Request (invalid parameters or body) |
401 | Unauthorized (missing or invalid API key) |
403 | Forbidden (API key lacks required scope) |
404 | Not Found (resource does not exist) |
429 | Too Many Requests (rate limit exceeded) |
500 | Internal Server Error |
Rate Limiting
API requests are rate-limited per API key:
- 60 requests per minute for most endpoints
- 10 requests per minute for write operations (create, update, delete)
Rate limit information is included in response headers:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 57
X-RateLimit-Reset: 1705312800If you exceed the rate limit, you'll receive a 429 response. Wait until the reset timestamp before retrying.
Pagination
Endpoints that return lists support pagination via query parameters:
| Parameter | Default | Description |
|---|---|---|
page | 1 | Page number (1-indexed) |
limit | 20 | Items per page (max 100) |
