Skip to main content

Device App Connection Log

Register and track network connection logs from devices to applications.

Base URL: https://gate.zequenze.com/api/v1

Authentication: All endpoints require a Bearer token:

Authorization: Bearer <your-api-token>

Endpoints

POST /device_app_connection_log/

Register a network connection log entry for tracking device-to-application connectivity.

Parameters:

Parameter Type In Required Description
data string body Yes JSON string containing connection log information

Example Request:

POST /api/v1/device_app_connection_log/
Content-Type: application/json
Authorization: Bearer <your-api-token>

{
  "data": "{\"device_id\": \"dev_12345\", \"app_id\": \"app_67890\", \"connection_type\": \"wifi\", \"connection_status\": \"connected\", \"timestamp\": \"2024-01-15T10:30:00Z\", \"ip_address\": \"192.168.1.100\", \"signal_strength\": -45, \"data_transferred\": 1024}"
}

Example Response:

{
  "id": "log_abc123",
  "status": "created",
  "timestamp": "2024-01-15T10:30:01Z"
}
Status Description
201 Connection log created successfully
400 Invalid data format or missing required fields
401 Unauthorized - invalid or missing API token
422 Unprocessable entity - data validation failed

Best Practices

  • Data Format: Ensure the data parameter contains valid JSON string with all required connection details
  • Timestamp Accuracy: Use ISO 8601 format for timestamps to ensure proper chronological ordering
  • Error Handling: Always check the response status and handle validation errors appropriately
  • Rate Limiting: Implement appropriate delays between requests to avoid overwhelming the API
  • Data Validation: Validate connection log data on the client side before sending to reduce API errors
  • Retry Logic: Implement exponential backoff for failed requests, especially for network connectivity issues
Back to top