Device App Register
Register and manage device applications in the backend system.
Base URL: https://gate.zequenze.com/api/v1
Authentication: All endpoints require a Bearer token:
Authorization: Bearer <your-api-token>
Endpoints
POST /device_app_register/
Register a new application with the device backend system. This endpoint allows you to associate an application with a device for tracking and management purposes.
Parameters:
| Parameter | Type | In | Required | Description |
|---|---|---|---|---|
| data | string | body | Yes | JSON string containing application registration data |
Example Request:
POST /api/v1/device_app_register/
Content-Type: application/json
Authorization: Bearer <your-api-token>
{
"data": "{\"device_id\":\"device_12345\",\"app_name\":\"MyApplication\",\"app_version\":\"1.0.0\",\"platform\":\"android\",\"installation_date\":\"2024-01-15T10:30:00Z\"}"
}
Example Response:
{
"id": "app_reg_67890",
"device_id": "device_12345",
"app_name": "MyApplication",
"app_version": "1.0.0",
"platform": "android",
"registration_status": "active",
"created_at": "2024-01-15T10:30:00Z"
}
Response Status Codes:
| Status | Description |
|---|---|
| 201 | Application successfully registered |
| 400 | Invalid request data or malformed JSON |
| 401 | Unauthorized - invalid or missing token |
| 422 | Validation error - missing required fields |
| 500 | Internal server error |
Best Practices
-
Data Format: Ensure the
dataparameter contains properly escaped JSON string with all required application details - Error Handling: Always check the response status code and handle validation errors appropriately
- Unique Registration: Verify that the same application isn't registered multiple times for the same device
- Version Tracking: Include accurate version information to help with application lifecycle management
- Platform Specification: Use standardized platform identifiers (e.g., "android", "ios", "windows") for consistency