Repeating Lengthy Steps for QR Code Generation with M1 APIs

Hello,

I am currently implementing M1 APIs. I need to generate a health number and obtain a QR code. However, when I enter incorrect data, the API responds with a 422 error, indicating that the current request cannot be processed due to incorrect information. Surprisingly, even when I enter the correct data, I still receive the same response. As a result, I have to start the entire process again, which includes obtaining an Aadhar OTP, verifying the OTP, checking for the generated mobile OTP, validating the ID for the X token, and finally obtaining the QR code. It seems quite inconvenient to go through all these steps again for a small mistake. Is there an alternative approach available?
@IntegrationSupport

@kaustubh There is no alternative approach to this API. So sequence need to followed as you have mentioned.