| 500 | Something went wrong | ABDM-1000 | Unable to connect the database |
| 500 | No data found | ABDM-1001 | No data found |
| 500 | Something went wrong | ABDM-1002 | Integrity violation |
| 500 | Something went wrong | ABDM-1003 | Email Gateway is unavailable |
| 500 | Something went wrong | ABDM-1004 | SMS Gateway is unavailable |
| 500 | Something went wrong | ABDM-1005 | Invalid receiver |
| 400 | Bad Request, invalid request | ABDM-1006 | Bad Request, invalid request Body |
| 500 | Something went wrong | ABDM-1007 | Connection failed due to timeout |
| 500 | Something went wrong | ABDM-1008 | SMS service currently disabled |
| 500 | Something went wrong | ABDM-1009 | Email service currently disabled |
| 400 | Validation failed | ABDM-1010 | Validation failed |
| 500 | Something went wrong | ABDM-1011 | Gateway database unavailable |
| 400 | No records found against the ABHA Address | ABDM-1012 | No records found against the ABHA Address |
| 400 | Invalid ABHA Number | ABDM-1013 | Invalid ABHA Number |
| 400 | Invalid Mobile Email | ABDM-1014 | Invalid Mobile Email |
| 500 | Something went wrong | ABDM-1015 | Invalid Response |
| 500 | Something went wrong | ABDM-1016 | Invalid TimeStamp |
| 500 | Something went wrong | ABDM-1017 | Invalid TransactionId |
| 500 | Unable to share the details with Hospital | ABDM-1018 | Share Profile database unavailable |
| 500 | Something went wrong | ABDM-1019 | Dependent Service Unavailable |
| 500 | Something went wrong | ABDM-1020 | Unknown database |
| 500 | Something went wrong | ABDM-1021 | ABDM-1021 |
| 500 | Too many requests | ABDM-1022 | Too many requests |
| 500 | Something went wrong | ABDM-1023 | Invalid User |
| 500 | Something went wrong | ABDM-1024 | Dependent service unavailable |
| 500 | Something went wrong | ABDM-1025 | Invalid ServiceId |
| 500 | Something went wrong | ABDM-1026 | Invalid Link Token |
| 500 | You are blocked. Please try again after 24 hours. | ABDM-1027 | You are blocked. Please try again after 24 hours. |
| 500 | Something went wrong | ABDM-1028 | HIP is unavailable |
| 500 | Something went wrong | ABDM-1029 | Redis server is unavailable |
| 400 | Something went wrong | ABDM-1030 | Invalid request ID |
| 400 | Something went wrong | ABDM-1031 | Invalid request |
| 400 | Something went wrong | ABDM-1032 | Invalid header |
| 500 | Something went wrong | ABDM-1033 | HIU is unavailable |
| 500 | Something went wrong | ABDM-1034 | Notification service unavailable |
| 500 | Something went wrong | ABDM-1035 | Invalid HIP ID |
| 400 | OTP doesn’t match | ABDM-1035 | OTP does not matched |
| 500 | Something went wrong | ABDM-1036 | Data does not matched |
| 500 | Something went wrong | ABDM-1037 | Counter and Care context count mismatch |
| 500 | Something went wrong | ABDM-1038 | ABHA address and Link token mismatch |
| 500 | Something went wrong | ABDM-1039 | Invalid Consent request id |
| 500 | Something went wrong | ABDM-1040 | Invalid HIU ID |
| 500 | Something went wrong | ABDM-1041 | Invalid Acknowledgement |
| 400 | Invalid request | ABDM-1042 | Provider Mandatory |
| 500 | Something went wrong | ABDM-1043 | ABHA Address does not match with KYC details. |
| 500 | Something went wrong | ABDM-1044 | Broadcast Failed |
| 500 | Something went wrong | ABDM-1045 | Database Access is restricted |
| 500 | Something went wrong | ABDM-1046 | Invalid Purpose |
| 500 | Something went wrong | ABDM-1047 | Purpose does not exist |
| 500 | Something went wrong | ABDM-1048 | Timeout |
| 500 | Something went wrong | ABDM-1049 | Invalid Profile Share Intent Keys |
| 500 | Something went wrong | ABDM-1050 | Invalid Profile Share Metadata Keys |
| 500 | Something went wrong | ABDM-1051 | Invalid ABHA Number or ABHA Address |
| 500 | Something went wrong | ABDM-1052 | Invalid TransactionId or response’s requestId |
| 500 | Something went wrong | ABDM-1053 | Data already exists |
| 500 | Something went wrong | ABDM-1054 | Invalid Subscription Request Id |
| 500 | Something went wrong | ABDM-1401 | HIP is not available |
| 500 | Something went wrong | ABDM-1402 | Acknowledgement is not received from HIP |
| 500 | Something went wrong | ABDM-9999 | Unknown exception |
| 400 | Consent artefact expired | ABDM-1061 | Consent artefact expired |
| 400 | Consent Not granted | ABDM-1062 | Consent Not granted |
| 400 | Date Range given is invalid | ABDM-1063 | Date Range given is invalid |
| 400 | Something went wrong | ABDM-1064 | request with this request id already exists |
| 500 | Something went wrong | ABDM-1109 | ABHA DB service unavailable |
| 500 | Something went wrong | ABDM-1108 | Notification DB service unavailable |
| 500 | Something went wrong | ABDM-1205 | Document DB Gateway is unavailable |
| 500 | Something went wrong | ABDM-1202 | Document Gateway is unavailable |
| 500 | Something went wrong | ABDM-1200 | LGD Gateway is unavailable |
| 500 | Something went wrong | ABDM-1201 | IDP Gateway is unavailable |
| 500 | Something went wrong | ABDM-1101 | This ABHA Address already exists. Please create with unique ABHA Address |
| 500 | Something went wrong | ABDM-1006 | Invalid combinations of scopes |
| 500 | Something went wrong | ABDM-1100 | You have requested multiple OTPs Or Exceeded maximum number of attempts for OTP match in this transaction. Please try again in 30 minutes. |
| 500 | ABHA User not found. | ABDM-1110 | ABHA User not found. |
| 400 | Mobile number not found. | ABDM-1111 | Mobile number not found. |
| 400 | Aadhaar details not found. | ABDM-1112 | Aadhaar details not found. |
| 400 | Login via Password is not allowed | ABDM-1113 | Login via Password is not allowed |
| 400 | Login via ABHA Number OTP is not allowed | ABDM-1114 | Login via ABHA Number OTP is not allowed |
| 400 | Login via Aadhaar OTP is not allowed | ABDM-1115 | Login via Aadhaar OTP is not allowed |
| 400 | Mobile number verification is pending. | ABDM-1102 | Mobile number verification is pending. |
| 400 | The OTP that you have entered is incorrect. Please try again. | MIS-1013 | OTP(One Time Password) is invalid, Please enter the correct OTP. |
| 500 | Transaction not found for UUID. | MIS-1026 | Transaction is not found for UUID. |
| 400 | This account has already been claimed by the mobile number: mobile_number | EKA-1001 | This account has already been claimed by the mobile number: mobile_number |
| 400 | This account has already been claimed by another mobile number: mobile_number | EKA-1002 | This ABHA belongs to a different mobile number, shown in the message (last 10 digits). Use that mobile number. |
| 400 | Session expired. Please try again. | EKA-1003 | The transaction was not found or has expired. Start the flow again with a new OTP or a new session. |
| 400 | Some details are missing or not valid. Please check and try again. | EKA-1004 | A field in the request is missing, malformed or not accepted. Check the request body. |
| 400 | Please enter at least 3 letters to search. | EKA-1004 | The search name is too short. Send at least 3 letters. |
| 404 | We could not find this ABHA. Please check the details and try again. | EKA-1005 | Check the ABHA number or address sent. If it is correct, the ABHA does not exist. If the user has no ABHA linked, see EKA-1015. |
| 500 | Something went wrong. Please try again. | EKA-1006 | A problem on Eka’s side, such as a store or search failure. Retry later. If it continues, contact support. |
| 400 | Invalid aadhaar number | EKA-1007 | The Aadhaar number failed validation before ABDM was called. Ask the user to re-enter it. Do not retry the same value. |
| 400 | Invalid mobile number | EKA-1008 | Ask the user to re-enter a valid 10-digit mobile number. |
| 400 | An ABHA health_id already exists for your profile | EKA-1009 | This profile already has an ABHA, shown in the message. Use it. Do not create another. |
| 400 | You have reached the maximum number of ABHA that can be created for this mobile | EKA-1010 | Do not retry. This mobile has reached its limit for creating ABHA. Contact support. |
| 400 | Please enter a valid date of birth. | EKA-1011 | Ask the user to enter a real date of birth. |
| 400 | Invalid ABHA number | EKA-1012 | Ask the user to re-enter the 14-digit ABHA number. |
| 403 | ABHA search is turned off for your workspace. | EKA-1013 | Do not retry. ABHA search is off for this workspace. Contact support to turn it on. |
| 429 | Too many requests. Please try again later. | EKA-1014 | Wait, then retry. Slow down the request rate. |
| 400 | No ABHA is linked to your profile. Please link one and try again. | EKA-1015 | Ask the user to create or link an ABHA first. |
| 400 | We could not find your workspace. Please sign in again, or contact support if this continues. | EKA-1016 | Ask the user to sign in again. If it continues, contact support. |
| 404 | We could not find this consent request. Please check the request ID and try again. | EKA-1017 | Check the consent request ID and health ID sent. If they are correct, the consent request does not exist. |
| 403 | Not authorised to access this profile | EKA-1018 | Do not retry. This profile is not linked to the caller’s clinics. Contact support. |
| 400 | Your healthcare facility is not onboarded on HMIS yet. Please reach out to our support team. | EKA-1019 | Do not retry. The clinic is not onboarded on HMIS. Contact support. |
| 400 | This HIP ID is not linked to your workspace. Check the ID, or link it in Eka Console. | EKA-1020 | Check the HIP ID sent. If it is correct, link the facility to the workspace in Eka Console (ABDM Connect). If it is already linked, contact support. |
| 404 | We could not find this facility. Please check the facility ID and try again. | EKA-1021 | Check the facility ID sent. If it is correct, the facility does not exist in the HFR. |