"Troubleshooting On-Fetch Issue: M3 API Connectivity Challenges and ABDM Behavior"

HIU Implementation
#1

M3 api on-fetch not working.
On-Init
On-Status
apis are working
Bridge url is correctly set.

But still on-fetch not working after fetch api is called. (fetch is giving 200)
on-fetch is working if we send dummy data from postman.
But ABDM is not sending it

1 Like
#2

client ID:- SBX_003468 @IntegrationSupport

#3

Please reply @IntegrationSupport
​Consent Flow consists of following api’s for M3 HIU implementation

  1. Init
  2. On init
  3. Status
  4. On Status
  5. Notify
  6. On Notify
  7. Fetch
  8. On Fetch

APIs 1-7 are working correcly (We get correct response from ABDM Gateway for on init, on status and notify)
API 7 is giving 202 response

But On Fetch API not getting triggered by ABDM Gateway. No error message is obtained because api endpoint is not called.
Following is the Fetch API number 7 curl

curl --location --request POST ’ https://dev.abdm.gov.in/gateway/v0.5/consents/fetch ’
–header 'accept: / ’
–header ‘X-CM-ID: sbx’
– header ‘Content-Type: application/json’
–header ‘Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE2OTI2OTg3OTEsImlhdCI6MTY5MjY3NzE5MSwianRpIjoiNjQ5MzQ3YWYtYzQ1OS00MDVlLTkxYTgtMTk4OTUzMjQ0YTJlIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiIzOGQ4OTQ3NS1mOWVjLTQ2ZTQtOWUyYS1iMjdmODkzYTA1ZTMiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJTQlhfMDAzMDA5Iiwic2Vzc2lvbl9zdGF0ZSI6ImIxYTJlNmZmLWEwZmItNDRlMy1hNmNkLTRjZjk3YmMxYjlmNCIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDA3Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsImhlYWx0aElkIiwicGhyIiwiT0lEQyIsImhpcCJdfSwicmVzb3VyY2VfYWNjZXNzIjp7IlNCWF8wMDMwMDkiOnsicm9sZXMiOlsidW1hX3Byb3RlY3Rpb24iXX0sImFjY291bnQiOnsicm9sZXMiOlsibWFuYWdlLWFjY291bnQiLCJtYW5hZ2UtYWNjb3VudC1saW5rcyIsInZpZXctcHJvZmlsZSJdfX0sInNjb3BlIjoib3BlbmlkIGVtYWlsIHByb2ZpbGUiLCJjbGllbnRJZCI6IlNCWF8wMDMwMDkiLCJjbGllbnRIb3N0IjoiMTAuMjMzLjY4LjIxOCIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LXNieF8wMDMwMDkiLCJjbGllbnRBZGRyZXNzIjoiMTAuMjMzLjY4LjIxOCJ9.do3 mVehxrXCvLNeuAEUN_M9mopwoM-gj7z83NNRqc4GXg4kAvNQc8wy6zzNTajkcZLwaes8M0aPOUzeXMg9HwOU8Aib3o_g1oY-z94s0Jw2o-2Lfb6vRqRHY19vplf9VDXxmawlSroRLKCrzX8-9 PR7L20UGzz-a4-nNyLlsWMPh8p1xkD3gSEwjt1-NHHcjYktTlDmR52ZJrM4MilZJVNrmcV97r9bkiR76A43APW6LIierP8Oy6dSZFc5cbxAVvJXxPkRcBxtJvYiCdzZaU48xj8pkn 5_lgVPDHb8BfvbP-IdEL-cgLaF_ahjNW-ekcTNoOxlwq1gpgWubvflKxw’do3mVehxrXCvLNeuAEUN_M9mopwoM-gj7z83NNRqc4GXg4kAvNQc8wy6zzNTajkcZLwaes8M0aPOUzeXMg9HwOU8Aib3o_g1oY-z94s0Jw2o-2Lfb6vRqRHY19vplf9VDXxmawlSroRLKCrzX 8-9PR7L20UGzz-a4-nNyLlsWMPh8p1xkD3gSEwjt1-NHHcjYktTlDmR52ZJrM4MilZJVNrmcV97r9bkiR76A43APW6LIierP8Oy6dSZFc5cbxAVvJXxPkRcBxtJvYiCdzZaU48xj8 pkn5_lgVPDHb8BfvbP-IdEL-cgLaF_ahjNW-ekcTNoOxlwq1gpgWubvflKxw’do3mVehxrXCvLNeuAEUN_M9mopwoM-gj7z83NNRqc4GXg4kAvNQc8wy6zzNTajkcZLwaes8M0aPOUzeXMg9HwOU8Aib3o_g1oY-z94s0Jw2o-2Lfb6vRqRHY19vplf9VDXxmawlSroRLKCrzX 8-9PR7L20UGzz-a4-nNyLlsWMPh8p1xkD3gSEwjt1-NHHcjYktTlDmR52ZJrM4MilZJVNrmcV97r9bkiR76A43APW6LIierP8Oy6dSZFc5cbxAVvJXxPkRcBxtJvYiCdzZaU48xj8 pkn5_lgVPDHb8BfvbP-IdEL-cgLaF_ahjNW-ekcTNoOxlwq1gpgWubvflKxw’
–header ‘Cookie: TS011c04bd=01445fed04e09753ce5cc70c66c1476d8180fd3412ace2d4eb63ce672d9388ab8310be2edf16cd84888e238627b7b664cd51882782’
–data-raw ‘{
“ requestId”: “7386b5b5-abba-4086-a06b-b331f725a4c6”, “timestamp”: “2023-08-22T06:39:57.029000
”,
“consentId” : “d4af7857-6e82-4d86-85c8-e22116041ba6”
}’

We are getting 202 response for this.

Here is bridge url registered : https://ions2onnxb.execute-api.ap-south-1.amazonaws.com/prod/
. Server is in Mumbai, India and since 7 out of 8 APIs are working, this indicates there is no whitelisting issue
Client Id: SBX_003468 ​Consent Flow consists of following api’s for M3 HIU implementation

  1. Init
  2. On init
  3. Status
  4. On Status
  5. Notify
  6. On Notify
  7. Fetch
  8. On Fetch

APIs 1-7 are working correcly (We get correct response from ABDM Gateway for on init, on status and notify)
API 7 is giving 202 response

But On Fetch API not getting triggered by ABDM Gateway. No error message is obtained because api endpoint is not called.
Following is the Fetch API number 7 curl

curl --location --request POST ’ https://dev.abdm.gov.in/gateway/v0.5/consents/fetch ’
–header 'accept: / ’
–header ‘X-CM-ID: sbx’
– header ‘Content-Type: application/json’
–header ‘Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE2OTI2OTg3OTEsImlhdCI6MTY5MjY3NzE5MSwianRpIjoiNjQ5MzQ3YWYtYzQ1OS00MDVlLTkxYTgtMTk4OTUzMjQ0YTJlIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiIzOGQ4OTQ3NS1mOWVjLTQ2ZTQtOWUyYS1iMjdmODkzYTA1ZTMiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJTQlhfMDAzMDA5Iiwic2Vzc2lvbl9zdGF0ZSI6ImIxYTJlNmZmLWEwZmItNDRlMy1hNmNkLTRjZjk3YmMxYjlmNCIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDA3Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsImhlYWx0aElkIiwicGhyIiwiT0lEQyIsImhpcCJdfSwicmVzb3VyY2VfYWNjZXNzIjp7IlNCWF8wMDMwMDkiOnsicm9sZXMiOlsidW1hX3Byb3RlY3Rpb24iXX0sImFjY291bnQiOnsicm9sZXMiOlsibWFuYWdlLWFjY291bnQiLCJtYW5hZ2UtYWNjb3VudC1saW5rcyIsInZpZXctcHJvZmlsZSJdfX0sInNjb3BlIjoib3BlbmlkIGVtYWlsIHByb2ZpbGUiLCJjbGllbnRJZCI6IlNCWF8wMDMwMDkiLCJjbGllbnRIb3N0IjoiMTAuMjMzLjY4LjIxOCIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LXNieF8wMDMwMDkiLCJjbGllbnRBZGRyZXNzIjoiMTAuMjMzLjY4LjIxOCJ9.do3 mVehxrXCvLNeuAEUN_M9mopwoM-gj7z83NNRqc4GXg4kAvNQc8wy6zzNTajkcZLwaes8M0aPOUzeXMg9HwOU8Aib3o_g1oY-z94s0Jw2o-2Lfb6vRqRHY19vplf9VDXxmawlSroRLKCrzX8-9 PR7L20UGzz-a4-nNyLlsWMPh8p1xkD3gSEwjt1-NHHcjYktTlDmR52ZJrM4MilZJVNrmcV97r9bkiR76A43APW6LIierP8Oy6dSZFc5cbxAVvJXxPkRcBxtJvYiCdzZaU48xj8pkn 5_lgVPDHb8BfvbP-IdEL-cgLaF_ahjNW-ekcTNoOxlwq1gpgWubvflKxw’do3mVehxrXCvLNeuAEUN_M9mopwoM-gj7z83NNRqc4GXg4kAvNQc8wy6zzNTajkcZLwaes8M0aPOUzeXMg9HwOU8Aib3o_g1oY-z94s0Jw2o-2Lfb6vRqRHY19vplf9VDXxmawlSroRLKCrzX 8-9PR7L20UGzz-a4-nNyLlsWMPh8p1xkD3gSEwjt1-NHHcjYktTlDmR52ZJrM4MilZJVNrmcV97r9bkiR76A43APW6LIierP8Oy6dSZFc5cbxAVvJXxPkRcBxtJvYiCdzZaU48xj8 pkn5_lgVPDHb8BfvbP-IdEL-cgLaF_ahjNW-ekcTNoOxlwq1gpgWubvflKxw’do3mVehxrXCvLNeuAEUN_M9mopwoM-gj7z83NNRqc4GXg4kAvNQc8wy6zzNTajkcZLwaes8M0aPOUzeXMg9HwOU8Aib3o_g1oY-z94s0Jw2o-2Lfb6vRqRHY19vplf9VDXxmawlSroRLKCrzX 8-9PR7L20UGzz-a4-nNyLlsWMPh8p1xkD3gSEwjt1-NHHcjYktTlDmR52ZJrM4MilZJVNrmcV97r9bkiR76A43APW6LIierP8Oy6dSZFc5cbxAVvJXxPkRcBxtJvYiCdzZaU48xj8 pkn5_lgVPDHb8BfvbP-IdEL-cgLaF_ahjNW-ekcTNoOxlwq1gpgWubvflKxw’
–header ‘Cookie: TS011c04bd=01445fed04e09753ce5cc70c66c1476d8180fd3412ace2d4eb63ce672d9388ab8310be2edf16cd84888e238627b7b664cd51882782’
–data-raw ‘{
“ requestId”: “7386b5b5-abba-4086-a06b-b331f725a4c6”, “timestamp”: “2023-08-22T06:39:57.029000
”,
“consentId” : “d4af7857-6e82-4d86-85c8-e22116041ba6”
}’

We are getting 202 response for this.

Here is bridge url registered : https://ions2onnxb.execute-api.ap-south-1.amazonaws.com/prod/
. Server is in Mumbai, India and since 7 out of 8 APIs are working, this indicates there is no whitelisting issue
Client Id: SBX_003468

#4

@rohan12 Please confirm, if you are entering correct consent-request-id. It should be consent-request-id and not consent-artifacts-id.

#5

Yes we are entering consent-request-id

#6

Please help us in this issue, it is already been 3 days @IntegrationSupport

#7

@rohan12 We have escalated the concerned issue with the tech team. Please wait, we will revert once we receive resolution for the same.

1 Like
#8

@rohan12 Resolution here—
Please pass consentArtefacts - id instead of consent request-id.

Consent Artefacts received on the response of API /v0.5/consent-requests/on-status .

image-20230824-104006

ex:

image-20230824-104118