Hi, we are trying to test our connection to e-RS API but we are not getting passed our user authorisation call as your end complains about invalid client id
https://int.api.service.nhs.uk/oauth2/authorize
Are you able to advice? Believe we should be using the KEY associated with ‘e-Referral Service - Healthcare Worker’
Believe it’s the KEY we received here?
I have read you problem and test about the API,
Just by the API’s docs said that, you need to use the client_id for request the API, follow the demo data will redirect to ‘example.com/callback’ was not correct for all the case, that was an example.
The client_id by the API doc’s said that you need to use the step1 created id’s, that means you need to make sure you have created the now application project in the dashboard, and check you access permission with the API.
Answer you question, KEY will return in this response?
No: Plz look at the state and step4 to know more about the status.
You can only get the return key to redirect to your URI. This KEY is doesn’t means your ‘Healthcare Worker’.
I have cap the screen for you to clear more:
invalid_request in response error, you can understand what are the error from.
I think you can explain more about your query for RESTful APIs.
In the [step4](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/user-restricted-restful-apis-nhs-cis2-combined-authentication-and-authorisation#step-4-receive-authorisation-results) you can understand more with state and code from the response to redirect, this is the Oauth2 access request API.
I hope this answer can help you to understand the API usage are for the app project redirect permission request.
Any more question post on here and let us for help.
Thank you.
If I understood you correctly, you are suggesting our Callback URL is not recognised, will revisit the creation and setting up as per your guidelines and see where we end up.
Callback URL was not specified on API … We will retry on Thursday and will come back if any problems.
Eyes, important feature.
Well, I use most part to enplane with the API from INS-API
it means you are request the access right pass by the Oauth2.
In the docs of Step.4,
It clear to say you need the /callback?code=xxxx response into your service application to success the data passing.
So you are correct to make the data you need under the callback?code=
And it not api.service.nhs.uk/oauth2/, ← this just for access right request 