AePS Authentication Api
AePS Authentication
Description :
This API endpoint is used to do AePS authentication.
Endpoint URL :Request Parameters
| Request Parameter | Data Type | Default Value | Required | Description | Change Date | Change Description |
|---|---|---|---|---|---|---|
| token | string | Yes | Please pass the app access token | |||
| agent_id | string | Yes | id of the aeps agent | |||
| latitude | string | Yes | Please enter latitude | |||
| longitude | string | Yes | Please enter longitude | |||
| refid | string | Yes | please enter refid | |||
| req_mode | string | Yes | please enter req_mode from (API,App) | |||
| pid_data | string (base64 encoded) | Yes | finger print data |
Request Example [JSON]
Responses (JSON)
- status_code (integer): The status code of the response.
- message: Transaction Successfully Completed.
- status: Status of transaction report
- auth_reference_no: authentication token
- txn_id: transaction id
- created_at: transaction request time
- updated_at: transaction complete time
{"status_code": 2, "message": "token is required"}
- 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, "message": "Agent id not found"}
- Status Code 0: Error message
- Description: A specific error message.
- 'status_code' (integer): 0
- 'message' (string): "Agent id not found"
- 'status' (string): "Failed"
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.