UAE EID Fine Enquiry Check - Initiate
Overview of the API
The Emirates ID Fine Enquiry Service API allows users to check if a given Emirates ID (EID) has any fines associated with it. The API returns information on whether a fine is found, the number of days the fine has been active, and the total fine amount in dirhams.
Use Case
This API is useful for individuals and organizations needing to verify the fine status of an Emirates ID. It can be integrated into systems for background checks, compliance verification, and other administrative processes where fine status information is required. The Emirates ID Fine Enquiry Service API is beneficial in various scenarios:
- Background Checks:
- Employers: Verify candidates' fine status.
- Landlords: Screen potential tenants.
- Compliance Verification:
- Banks: Assess applicants for before approving loans and credit cards.
- Government Agencies: Check for fines before providing services.
- Administrative Processes:
- Insurance Companies: Evaluate policyholders' risk.
- Legal Firms: Provide accurate legal advice based on clients' fine status.
- Personal Use:
- Individuals: Check their own EID for fines.
- Real Estate Transactions:
- Agents and Buyers: Ensure parties have no fines before transactions.
API Input
curl --location 'https://api-preproduction.signzy.app/api/v3/uae-api/eid-fine-enquiry-async' \
--header 'Content-Type: application/json' \
--header 'Authorization: <auth_token>' \
--data '{
"emiratesIdNumber": "<emirates_id_number>",
"dateOfBirth": "<yyyy-mm-dd>",
"gender": "<male or female>",
"callbackUrl": "<callback_url>"
}'API Input Mapping
Input | Data Type | Mandatory/Optional | Description |
|---|---|---|---|
emiratesIdNumber | Number | Mandatory | The Emirates ID number to be checked. Must be a valid numeric EID. |
dateOfBirth | String | Mandatory | Date of birth of the EID holder, in YYYY-MM-DD format. |
gender | String | Mandatory | Gender of the EID holder. Only male or female are accepted (case-insensitive). |
callbackUrl | String | Optional | A valid URL to which the final asynchronous result will be POSTed. If omitted, use the Get Data API to retrieve the result. |
API Response
{
"result": {
"requestId": "<request_id>",
"statusCode": 102,
"status": "PROCESSING"
}
}API Output Mapping
Output | Data Type | Description |
|---|---|---|
requestId | String | Unique ID for the request. Use this in the Get Data API to fetch the result. |
statusCode | Number | Current status code of the request. 102 indicates the request is being processed. |
status | String | Current status of the request. Initially PROCESSING. |
Error Code Response & Mapping
{
"error": {
"name": "error",
"message": "Upstream down",
"status": 409,
"reason": "ERROR",
"type": "Conflict",
"statusCode": "409"
}
}Field | Type | Description |
|---|---|---|
name | string | Text displayed on the screen explaining error type. |
reason | string | Reason for the error. |
status | number | HTTP status code. |
message | string | Error message indicating an upstream error. |
type | string | Error type. |
statusCode | string | Status code representing the error scenario. |
Getting help
Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.
You can reach out to us at [email protected]. We strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively.
We value your feedback and are committed to making your experience smooth and enjoyable. Our team is dedicated to assisting you with any needs you may have. Thank you for choosing our services. We look forward to helping you!