On-discover 403 error

HIP Implementation
#21

@kiran02 can u please provide a sample response .

{
status: response.status,
statusText: response.statusText,
data: response.config.data,
}

as you are referring there is a statusText inside response in this line statusText: response.statusText, can u please provide a sample response

and also after calling on-discover api we get 202 accepted then only we have to return the response in this format
{
status: response.status,
statusText: response.statusText,
data: response.config.data,
}

#22

Yes. All these things like status, statusText, and config are present in response object

#23

@kiran02 can you please provide the sample of response that have all this parameter in it

#24

Sample response that need to send is

    {
status: 202,
statusText: 'Accepted',
data: {
    "requestId": "86492506-bdd8-401a-aeb4-7e953af5b77f",
    "timestamp": "2023-11-03T09:00:37.118Z",
    "transactionId": "cb76b512-330d-4498-bcaa-558b669407f2",
    "patient": {
        "referenceNumber": "Ref - 4736ba72-c2d0-41a8-bfa9-2fc4ec46005f",
        "display": "Consultation at Fri Nov 03 2023",
        "careContexts": [
            {
                "referenceNumber": "Ref - b44798c6-cdd0-49b9-af3f-bda7964f12ce",
                "display": "Consultation at Fri Nov 03 2023"
            }
        ],
        "matchedBy": [
            "MOBILE"
        ]
    },
    "resp": {
        "requestId": "ca171bfd-41d8-45c4-b22c-bbefe93ea7b1"
    }
  }
}
#25

@kiran02 still we didn’t received the response from ABDM gateway with URL v0.5/links/link/init

#26

@kiran02 we are waiting for your response. This are creating blocker in our development.

#27

Hi @pritamsingh07100 I’m not from @IntegrationSupport support team, I am just like you, fellow integrator. Just trying help each other. I have explained everything what needs to be done.

@IntegrationSupport Please help.

#28

@IntegrationSupport Your immediate solution is crucial to avoid further delays in our development process. Your prompt assistance would be greatly appreciated.

#29

@pritamsingh07100 Please confirm which api are you hitting and you are not getting response from ABDM.

#30

I will describe the process that I am following. Please tell me if I am wrong in any steps.

  1. /v0.5/care-contexts/discover (we received the callback after hitting fetch record in phr app

  2. /v0.5/care-contexts/on-discover(we are calling this api as soon as we get the /v0.5/care-contexts/discover response ) we are getting 202 accepted from this api.

  3. we are expecting callback from this api v0.5/links/link/init but we haven’t received any callback

#31

@IntegrationSupport @Sachin we are waiting for your response

#32

@IntegrationSupport @Sachin we are waiting can someone going to provide the solution as no documentation are clearly understandable for discover api we have more number of doubts pending we are stuck with the development

1 Like
#33

For them it doesn’t matter that you are stuck or your investment is being wasted. They are getting their salaries that’s enough for them

#34

For them it doesn’t matter that you are stuck or your investment is being wasted. They are getting their salaries that’s enough for them

#35

Getting same issue @IntegrationSupport

#36

@IntegrationSupport does we need to wait for more than a week for one solution?

#37

@pritamsingh07100

Please drop a mail on abdm.pc20@nha.gov.in, including this devforum link

Lets connect on a call to resolve this issue.
From API point, they are working fine.

image (31)

Also, add your client is and entity name.

@IntegrationSupport

#38

@Sachin we already mailed you 2 times with all our details

#39

Hello,

Just want to ask question, Lets say we are making mistakes in API calls, but should it impact the things you have provided us, like if things are in ABHA SBX app they should work fine? Correct?

But we are facing issues, can you check, error message is could not find the user details in popup & yesterday it was working fine

#40

Hi /v0.5/care-contexts/on-discover i calling this api and getting 403 Resource forbidden.
Response in this format
{

"code": "900908",

"message": "Resource forbidden ",

"description": "User is NOT authorized to access the Resource. API Subscription validation failed."

}
How to fix this issue?