Not receiving response on call back URL for API v0.5/users/auth/fetch-modes

HIP Implementation
#1

Hi,
I’m not receiving response on the call back URL for API v0.5/users/auth/fetch-modes.

I have done below steps.

  1. Updated the Health Repository URL using API - devservice/v1/bridges
  2. Registered the Facility using API devservice/v1/bridges/services

Here are the details.

Client ID : SBX_001807
“bridge”: {
“id”: “SBX_001807”,
“name”: “Oakland Systems Pvt Ltd”,
“url”: " https://webhook.site/5b78ec71-a046-4246-9cdf-9cdccdb746dd",
“active”: true,
“blocklisted”: false
}
“services”: [
{
“id”: “oakland-demo-1”,
“name”: “Oakland Demo 1”,
“types”: [
“HIP”
],
“endpoints”: {},
“active”: true
}
]
}

URL : https://dev.ndhm.gov.in/gateway/v0.5/users/auth/fetch-modes
Payload:
{
“requestId”: “89b2c7b8-8dca-42ab-863e-ab5ed2e4cac8”,
“timestamp”: “{{timestamp}}”,
“query”: {
“id”: “narendraghogre@sbx”,
“purpose”: “KYC”,
“requester”: {
“type”: “HIP”,
“id”: “oakland-demo-1”
}
}
}

Response : 202 Accepted.

Please let me know what is missing from our side.

#2

@Govind_Deshmukh - Please look into it.

#3

Hi,
Please follow the below Payload :

/v0.5/users/auth/on-fetch-modes
{
“requestId”: “6ecda9d3-024d-4163-949d-0a62a00c0baa”,
“timestamp”: “2022-06-22T07:45:02.281965”,
“auth”: {
“purpose”: “LINK”,
“modes”: [
“AADHAAR_OTP”,
“MOBILE_OTP”,
“DEMOGRAPHICS”,
“PASSWORD”
]
},
“error”: null,
“resp”: {
“requestId”: “5229f89a-c70e-4931-a524-06c921771131”
}
}

if in case any issue please let us we will help you further issue.
Thanks,
Govind D

#4

Thanks @Govind_Deshmukh for the response.
But my question was different.

After I call the API v0.5/users/auth/fetch-modes., I’m not getting the response on the call back URL (its webhook url).

#5

Hi,
Please let me know your availability for schedule meeting and share your details.

Thanks,
Govind D

#6

Hi,
You can contact me on narendra.ghogre@oaklandsystems.net today till 6:30 PM or tomorrow between 10 AM to 6 PM

#7

Hi @nghogre,

Can we connect know?

Thanks,
Govind D

#8

Hi @Govind_Deshmukh, We can connect now

#9

Hi @nghogre,

As per our discussion we are closing this issue.

Thanks,
Govind D.