M2 Linking and sharing errors
Seeing a symptom rather than a code? Start at Troubleshooting.
Codes
Code, message and error name are as published. The action column reads the message text by a documented rule, and says Unclassified rather than guessing.
| Code | Message | What to do |
|---|---|---|
ABDM-1000 | Unable to connect the database | Retry |
ABDM-1001 | No data found | Fix request |
ABDM-1004 | SMS Gateway is unavailable | Retry |
ABDM-1006 | Invalid HIType, it must be in Prescription,DiagnosticReport,OPConsultation,DischargeSummary,ImmunizationRecord,HealthDocumentRecord,WellnessRecord,Invoice | Fix request |
ABDM-1006 | Bad Request, invalid request Body | Fix request |
ABDM-1006 | Invalid combinations of scopes | Fix request |
ABDM-1006 | Invalid count, must be 2 digit and ranges between 1 to 20 | Fix request |
ABDM-1007 | Connection failed due to timeout | Retry |
ABDM-1008 | SMS service currently disabled | Retry |
ABDM-1010 | Validation failed | Fix request |
ABDM-1011 | Gateway database unavailable | Retry |
ABDM-1012 | No records found against the ABHA Address | Fix request |
ABDM-1013 | Invalid ABHA Number | Fix request |
ABDM-1015 | Invalid Response | Fix request |
ABDM-1016 | Invalid TimeStamp | Fix request |
ABDM-1017 | Invalid TransactionId | Fix request |
ABDM-1018 | Share Profile database unavailable | Retry |
ABDM-1019 | Dependent Service Unavailable | Retry |
ABDM-1020 | Unknown database | Retry |
ABDM-1022 | Too many requests | Back off |
ABDM-1023 | Invalid User | Fix request |
ABDM-1024 | Dependent service unavailable | Retry |
ABDM-1025 | Invalid ServiceId | Fix request |
ABDM-1026 | Invalid Link Token | Fix auth |
ABDM-1027 | You are blocked. Please try again after 24 hours. | Blocked, no retry |
ABDM-1028 | HIP is unavailable | Chase the HIP |
ABDM-1029 | Redis server is unavailable | Retry |
ABDM-1030 | Invalid request ID | Fix request |
ABDM-1030 | Request id not found | Fix request |
ABDM-1031 | Invalid request | Fix request |
ABDM-1032 | Invalid header | Fix request |
ABDM-1033 | HIU is unavailable | Chase the HIU |
ABDM-1034 | Notification service unavailable | Retry |
ABDM-1035 | Invalid HIP ID | Fix request |
ABDM-1036 | Data does not matched | Fix request |
ABDM-1037 | Counter and Care context count mismatch | Fix request |
ABDM-1038 | ABHA address and Link token mismatch | Fix auth |
ABDM-1040 | Invalid HIU ID | Fix request |
ABDM-1041 | Invalid Acknowledgement | Fix request |
ABDM-1042 | Provider Mandatory | Fix request |
ABDM-1043 | ABHA Address does not match with KYC details. | Fix request |
ABDM-1044 | Broadcast Failed | Retry |
ABDM-1045 | Database Access is restricted | Retry |
ABDM-1046 | Invalid Purpose | New consent |
ABDM-1047 | Purpose does not exist | New consent |
ABDM-1048 | Timeout | Retry |
ABDM-1049 | Invalid Profile Share Intent Keys | Ask support |
ABDM-1050 | Invalid Profile Share Metadata Keys | Ask support |
ABDM-1051 | Invalid ABHA Number or ABHA Address | Fix request |
ABDM-1052 | Invalid TransactionId or response's requestId | Fix request |
ABDM-1055 | Invalid HIP Id or PHR Id | Fix request |
ABDM-1056 | This care contexts has been already linked | Treat as success |
ABDM-1056 | Invalid Link Reference Number | Fix request |
ABDM-1057 | Invalid Care Contexts | Fix request |
ABDM-1059 | Invalid Care Contexts count | Fix request |
ABDM-1060 | Invalid Patient Reference Number | Fix request |
ABDM-1061 | Invalid Patient Display | Fix request |
ABDM-1061 | Consent artefact expired | New consent |
ABDM-1062 | ABHA number mismatch with Link token | Fix auth |
ABDM-1062 | Consent Not granted | New consent |
ABDM-1063 | HIP Id mismatch with Link token | Fix auth |
ABDM-1063 | Date Range given is invalid | New consent |
ABDM-1064 | request with this request id already exists | New request id |
ABDM-1064 | Request body was missing | Fix request |
ABDM-1065 | Invalid X Auth token | Fix auth |
ABDM-1066 | Invalid JWT token | Fix auth |
ABDM-1067 | Request body not required | Fix request |
ABDM-1084 | ABHA address mismatch with X Auth token | Fix auth |
ABDM-1085 | ABHA number mismatch with X Auth token | Fix auth |
ABDM-1086 | Patient profile mismatch with X Auth token | Fix auth |
ABDM-1087 | Duplicate patient share request | New request id |
ABDM-1090 | Duplicate HIP link request | New request id |
ABDM-1091 | Duplicate Get links request | New request id |
ABDM-1092 | Duplicate Link token request | New request id |
ABDM-1093 | Duplicate Bridge request | New request id |
ABDM-1094 | Duplicate bridge patch request | New request id |
ABDM-1095 | Duplicate Bridge service request | New request id |
ABDM-1102 | Profile information cannot be null | Ask support |
ABDM-1103 | Duplicate Discovery request | New request id |
ABDM-1104 | Duplicate Init request | New request id |
ABDM-1105 | Duplicate Confirm request | New request id |
ABDM-1106 | Duplicate On discovery request | New request id |
ABDM-1107 | Duplicate On init request | New request id |
ABDM-1108 | Duplicate On confirm request | New request id |
ABDM-1108 | Notification DB service unavailable | Retry |
ABDM-1109 | Invalid On discovery response | Fix request |
ABDM-1109 | ABHA DB service unavailable | Retry |
ABDM-1110 | Invalid On init response | Fix request |
ABDM-1111 | Invalid On confirm response | Fix request |
ABDM-1112 | Invalid or already expired consent artefact id | New consent |
ABDM-1113 | Duplicate health information provider data flow response | New request id |
ABDM-1149 | Intent type is not supported at HIP end | Fix request |
ABDM-1150 | Bridge API version cannot be null | Ask support |
ABDM-1170 | Invalid ABHA address | Fix request |
ABDM-1201 | IDP Gateway is unavailable | Retry |
ABDM-1401 | HIP is not available | Chase the HIP |
ABDM-1402 | Acknowledgement is not received from HIP | Chase the HIP |
ABDM-1407 | The ABHA Number associated with this ABHA Address is currently deactivated. Please reactivate it. | Fix request |
ABDM-2401 | The X Auth token is invalid. | Fix auth |
ABDM-2402 | Invalid Timestamp | Fix request |
ABDM-2403 | Invalid X-CM-ID | Fix request |
ABDM-2404 | Invalid Request Id | Fix request |
ABDM-2406 | Invalid API sequence flow, please follow logical flow | Fix request |
ABDM-2406 | The status is invalid. Please follow the logical status flow or transition. | Fix request |
ABDM-2429 | Too many requests found | Back off |
ABDM-2500 | Authorization header is missing | Fix auth |
ABDM-2500 | No mapping found for | Fix request |
ABDM-2501 | Payment status should be : `SUCCESS,CANCELED,PENDING,FAIL,REFUND_INITIATED,REFUND_SUCCESS | Ask support |
ABDM-9001 | No open order against ABHA. Please ensure a minimum of one open order | Ask support |
ABDM-9002 | No registration found at <<hospital name>>. Contact counter support | Ask support |
ABDM-9003 | Hospital services temporarily unavailable. Please try again after some time. | Retry |
ABDM-9004 | Services disrupted, please try again. | Retry |
ABDM-9005 | Bank server not responding. Please try again later | Ask support |
ABDM-9006 | Service details mismatch. Please ensure original service ID from HMIS | Ask support |
ABDM-9007 | The Scan and Pay functionality is not enabled at this facility. Kindly contact the hospital administration. | Ask support |
ABDM-9999 | HIP is unable to generate a token at this time. Please try again later. | Chase the HIP |
ABDM-9999 | HIP is unable to process at this time. Please try again later. | Chase the HIP |
ABDM-9999 | Unknown exception | Retry |
ABDM-9999 | Cannot process the request at the moment, please try later. | Retry |
ABDM-9999 | User not found | Retry |
Every code above is recorded in the specification that owns it. The aggregated list across modules is at error codes.