Login History

Description :

This API endpoint is used to get the login history of the user.

Endpoint URL :
Request Parameters
Request Parameter Data Type Default Value Required Description Change Date Change Description
from_date Date Yes date in Y-m-d format
to_date Date Yes date in Y-m-d format
offset integer 0 No number of records to skip before starting to return results.
limit integer 10 No determines the maximum number of records to return in the response.
Request Example
Responses (JSON)
  • Status Code 1: records fetched
    • Description: records successfully fetched.
    • status_code (integer): The status code of the response (1).
    • 'message' (string): "records successfully fetched"
    • 'recordsTotal' (integer): "number or total records"
    • 'recordsFiltered' (integer): "number or records filtered"
    • 'data' (Array): "it contains array of object"
      • 'id' (integer): "unique id of the record"
      • 'ip_address' (string): "ip address"
      • 'browser' (string): "name of browser"
      • 'login_mode' (string): "mode of lgin either web or app"
      • 'device_name' (string): "name of device where login"
      • 'imei_no' (string): "imei of device where login"
      • 'latitude' (string): "latitude while login"
      • 'longitude' (string): "longitude while login"
      • 'status' (string): "status of login success or failed"
      • 'created_date' (string): "date of record created"
      • 'created_time' (string): "time of record created"
  • Status Code 2: Validation Error
    • Description: Validation error in the input parameters.
    • 'status_code' (integer): 2
    • 'message' (string): "A specific validation error message."
  • Status Code 0: Error message
    • Description: A specific error message.
    • 'status_code' (integer): 0
    • 'message' (string): "there is no data found"
Note
  • The API endpoint should be accessed via a POST request.
  • Ensure that the request is properly validated and sanitized to prevent security vulnerabilities.
  • Implement proper error handling on the client side to display user-friendly error messages based on the 'status_code' and 'message' fields in the response.
© Redpay.
Design & Develop by Redpay Payments Private Limited