Linking data with Abha Id

HIP Implementation
#1

Hi @IntegrationSupport @Pavan @anchal2909 @himanshu0502 @Sachin

We were trying to link the visit data with our ABHA ID, till yesterday this flow was working fine but today we are getting this error -
==::On-Fetch-Auth-Mode::===
on-fetch-modes > json :: {“requestId”:“ca29d19c-bfea-4b97-b2f0-a91aa49289c5”,“error”:{“code”:2500,“message”:“Token verification failed”},“timestamp”:[2023,12,1,9,32,38,454827000],“resp”:{“requestId”:“63d23ce2-73a0-4795-a542-1bd8c57f5b3f”}}

Can you please help us resolve this issue on priority as we have a demo scheduled with our client.

#2

@Preet_16 This is working at our end. please try again now.

image
image1218×733 107 KB

#3

@Preet_16

This happened because the token that you were using for authorization is expired. So, you have to regenerate and use it whenever your token verification fails.

#4

No. This is not the case. Even If provide fresh token the issue is still there…

#5

@himanshu0502 No we are sending a fresh token everytime also we tried using webhook the same error is still there. Please help us resolve this error as our work is till stuck and we have a demo scheduled.

#6

@Preet_16 Kindly provide your Code Snippet as cURL for the same.

#7

Hi @himanshu0502
The request json that I am sending -

::: Fetch auth mode : {“requestId”:“e69567e0-753f-412b-abcb-1cf2a0a31b38”,“timestamp”:“2023-12-04T06:33:09.000000431”,“query”:{“id”:“preet012@sbx”,“purpose”:“KYC_AND_LINK”,“requester”:{“type”:“HIP”,“id”:“DDH_HIP_23”}}}

The on fetch response-
===::On-Fetch-Auth-Mode::===
on-fetch-modes > json :: {“requestId”:“15ec3a04-7843-4ea0-b3dd-b212fec2fe20”,“error”:{“code”:2500,“message”:“Token verification failed”},“timestamp”:[2023,12,4,6,33,10,841958000],“resp”:{“requestId”:“e69567e0-753f-412b-abcb-1cf2a0a31b38”}}

Same code was working till last Thursday also some other integrators are getting the same problem if you find any mistake in the above provided json pls do let me know and please help us resolving this issue.

#8

@IntegrationSupport
Maybe this issue happens from the NHA server side.
Kindly look over it