essl Web server API Integration with PWC

Biometric Attendance API Documentation

This document provides the necessary details to integrate with the Biometric Attendance API for pushing device log data.

API Request

To send attendance data, make a POST request to the API endpoint with the specified headers and body.

• HTTP Method: POST
• Content-Type: application/json

Request Headers

The following headers are required for authentication and routing:

Request Body

The request body must be a JSON array of objects, where each object represents a single attendance record.

Sample JSON Payload

[
  {
    "deviceId": "001",
    "userId": "12206",
    "loginDateTime": "2025-08-07T08:45:00Z",
    "logoutDateTime": "2025-08-07T17:30:00Z",
    "deviceLogId": "1"
  },
  {
    "deviceId": "002",
    "userId": "6015",
    "loginDateTime": "2025-08-07T08:45:00Z",
    "logoutDateTime": "2025-08-07T17:30:00Z",
    "deviceLogId": "2"
  }
]
    

API Response

The API provides clear success or error messages in JSON format.

Success Response (Code 200)

A successful request will return a status code of 200 OK.

{
  "status": "success",
  "message": "Data recorded successfully"
}
    

Error Responses

If an error occurs, the API will return an appropriate HTTP status code and a descriptive error message.

• 400 Bad Request: The request is malformed, often due to missing fields.

  
  {
    "status": "error",
    "message": "Missing required field: userId"
  }
              

• 401 Unauthorized: The API key is missing or invalid.

  
  {
    "status": "error",
    "message": "Invalid or missing authentication token"
  }
              

• 500 Internal Server Error: An unexpected error occurred on the server.

  
  {
    "status": "error",
    "message": "An unexpected error occurred"
  }