Issue with Request API Callback Response v0.5/health-information/cm/request

HIU Implementation
#1

I’m currently working on the Request API (v0.5/health-information/cm/request) in HIU side, but I’m not receiving any response at the callback URL. Could you please help me identify what might be going wrong?

My Code is like this 

{
    "requestId":"65b388eb-08b6-db48-bebd-653a608ae360",
    "timestamp":"2023-10-26T12:48:52.416526",
    "transactionId":"c9d26006-57ee-4520-b9ce-5d26ae5be5b4",
    "hiRequest":{
        "consent":{
            "id":"9d384ee1-a777-42f7-b7f6-dadadc3dd2ff"
        },
        "dateRange":{
            "from":"2023-10-25T00:00:00.000000",
            "to":"2023-10-27T00:00:00.000000"
        },
        "dataPushUrl":"https:\/\/webhook.site\/5e882d47-b9a9-4c8a-a662-1c24410820ea",
        "keyMaterial":{
            "cryptoAlg":"ECDH",`Preformatted text`
            "curve":"Curve25519",
            "dhPublicKey":{
                "expiry":"2023-11-01T00:00:00.000000",
                "parameters":"Curve25519\/32byte random key",
                "keyValue":"MIIBMTCB6gYHKoZIzj0CATCB3gIBATArBgcqhkjOPQEBAiB\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/7TBEBCAqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqYSRShRAQge0Je0Je0Je0Je0Je0Je0Je0Je0Je0Je0JgtenHcQyGQEQQQqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq0kWiCuGaG4oIa04B7dLHdI0UySPU1+bXxhsinpxaJ+ztPZAiAQAAAAAAAAAAAAAAAAAAAAFN753qL3nNZYEmMaXPXT7QIBCANCAAQCDefiVmzXSbbBsobHVELEhYwC7jRGE9LJs22WJg1BQWsLK2uwRTOip6f8bjsnWC+ftObkYaoRPGYExnILdf5Y"
            },
            "nonce":"pNtj8paLuJxSpJNy29ryhote5AGiURem8tIJJRYJEn8="
        }
    }
}

@IntegrationSupport
@rajveer.parchaa @saiki

#2

hey anand,

are you getting response on /v0.5/health-information/hiu/on-request endpoint

after getting response on this gateway sends request to HIP on /v0.5/health-information/hip/request endpoint and HIP will push data on https://webhook.site/5e882d47-b9a9-4c8a-a662-1c24410820ea , but it seems like webhook endpoint is also not so correct or if it is correct then most welcome.

Thanks

for more you can reachout to @IntegrationSupport on their mail address.

#3

Hi Rajveer,

It appears that the issue is not related to the Push URL. I noticed that you might be getting confused by multiple slashes, but this seems to be a different problem. As you suggested, I am now connecting with the Support Team to address this issue.

Thanks.

#4

I’ve noticed that there are escaped characters within your JSON, particularly in the public key section (keyValue attribute). This is likely what’s affecting the intended functionality of your request.

Please make the necessary adjustments to your request body to ensure it is correctly formatted without the escape characters. This should hopefully help resolve the issue you are experiencing.

#5

Thanks SAI for pointing it out.Now I am trying to remove this.