Frequently Faced Issues - NHA-ABDM/ABDM-wrapper GitHub Wiki

Following are some of the issues you might face quite often while integrating with wrapper:

• Unstable Gateway: The ABDM sandbox environment is very unstable and it keeps facing downtime. There is no other way but to wait for it to come back up again.
• 429 Too many requests: Do not use the same request id to issue requests to wrapper. You should always send an unique request id every time you are making a new request. For status calls though, you should use the client request id which you used to issue the original request.
• Internal Server Error (Bad Gateway): This means there was no problem with wrapper but there was some problem with gateway in which case you should try again with a different request id.
• Internal Server Error (Timeout): This means there was no problem with wrapper but gateway didn't respond timely in which case you should try again with a different request id.
• 401 Unauthorized: This message is misleading and in all likelihood your access-token is valid. You just need to request again with a different request id.
• HIP Initiated Linking using demographics as auth mode: get status of the link request: Got Error in onAuthConfirmCall callback: Invalid auth confirm request. This can mean that demographics data stored in database does not match with what is stored in ABDM (which was provided by PHR app) check your name, gender and date of birth in wrapper database