Overview
Complete API reference for CONTROL API with 66 endpoints across 30 categories.
Version: v1
Base URL: https://control.zequenze.com/api/v1
Zequenze CONTROL platform API documentation
Authentication
All API endpoints require authentication using a Bearer token in the request header:
Authorization: Bearer <your-api-token>
You can obtain your API token from the portal administration panel.
Available Endpoints
| Category | Endpoints | Methods |
|---|---|---|
| Inventory Connection Profile | 2 | GET |
| Inventory Device | 6 | DELETE GET PATCH POST PUT |
| Inventory Device Diags | 2 | GET POST |
| Inventory Device Headless Operation | 2 | GET POST |
| Inventory Device Ipping | 1 | GET |
| Inventory Device Log | 2 | GET |
| Inventory Device Name | 6 | DELETE GET PATCH POST PUT |
| Inventory Device Name Diags | 2 | GET POST |
| Inventory Device Name Headless Operation | 2 | GET POST |
| Inventory Device Name Ipping | 1 | GET |
| Inventory Device Name Operation | 1 | PUT |
| Inventory Device Name Setting | 3 | GET PATCH PUT |
| Inventory Device Name Variables | 2 | GET PUT |
| Inventory Device Operation | 1 | PUT |
| Inventory Device Serial | 6 | DELETE GET PATCH POST PUT |
| Inventory Device Serial Diags | 2 | GET POST |
| Inventory Device Serial Headless Operation | 2 | GET POST |
| Inventory Device Serial Ipping | 1 | GET |
| Inventory Device Serial Operation | 1 | PUT |
| Inventory Device Serial Setting | 3 | GET PATCH PUT |
| Inventory Device Serial Variables | 2 | GET PUT |
| Inventory Device Setting | 3 | GET PATCH PUT |
| Inventory Device Variables | 2 | GET PUT |
| Inventory Device Whip | 1 | GET |
| Inventory Metric | 2 | GET |
| Inventory Metric Log | 2 | GET |
| Inventory Parameter | 2 | GET |
| Inventory Type | 2 | GET |
| Securedns Categoryget | 1 | GET |
| Securedns Hostcheck | 1 | GET |
Quick Start
1. Authentication
Obtain your API token from the portal and include it in all requests.
2. Make a Request
curl -X GET "https://control.zequenze.com/api/v1/endpoint/" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"
3. Handle the Response
All responses are in JSON format. List endpoints include pagination.
Response Codes
| Code | Status | Description |
|---|---|---|
| 200 | OK | Request successful |
| 201 | Created | Resource created successfully |
| 204 | No Content | Request successful (DELETE operations) |
| 400 | Bad Request | Invalid request parameters |
| 401 | Unauthorized | Missing or invalid authentication token |
| 403 | Forbidden | Insufficient permissions |
| 404 | Not Found | Resource not found |
| 500 | Server Error | Internal server error |
Pagination
List endpoints return paginated results:
{
"count": 150,
"next": "https://api.example.com/endpoint/?offset=50",
"previous": null,
"results": [...]
}
Use limit and offset query parameters to navigate through results.