Have an application registered within the INT environment.
Obtaining the access token for API requests is working fine but we need advice on how to make requests to APIs that have ‘Application-restricted access’.
Seems we might need additional configuration applying?
Understand that the application does not need CIS2 as it’s for unattended execution.
Could someone advise on what additional configuration is needed please?
Hi, can we just confirm which App ID you are using please? If you are user and app restricted you’d need an application for each, and we’d need to help you set them up.
Currently as I understand it you are using d2e09b90-865e-423b-a7aa-82007da69874 for application restricted? Could you confirm that 
hi Tony
Thanks for the reply.
Yes that’s correct but needed for both:
5fa0c357-c924-4ee3-aa33-140906f47bb4
and
d2e09b90-865e-423b-a7aa-82007da69874
Ah okay, I will check on both apps and check how they are setup and respond on here
Hi,
So, d2e09b90-865e-423b-a7aa-82007da69874 looks as expected and contains all the attributes required for application-restricted access.
We don’t recognise 5fa0c357-c924-4ee3-aa33-140906f47bb4. We haven’t configured this application, and it appears to have an unusually long ASID, which looks a little odd, although it may have been provisioned by another team.
From an e-RS perspective, d2e09b90-865e-423b-a7aa-82007da69874 is the correct application and should work for application-restricted access when sending referrals to the test organisation with ODS code I7K3M.
At present, you only have a single application configured for application-restricted access. We do not have any applications configured for user-restricted access, and the additional application appears to be a duplicate of the same authentication type, with values that we have not configured.
If calls are failing when using d2e09b90-865e-423b-a7aa-82007da69874, could you please provide a few correlation IDs? We can then ask a developer to investigate the logs and determine where the requests are failing.
Kind regards,
Tony
hi Tony
thanks again for looking into this for us.
Re d2e09b90-865e-423b-a7aa-82007da69874.
Given the application configuration is correct for application restricted access:-
One of my colleagues raised this ticket Clarification Required Regarding A023 User-Restricted Authentication for Automated Integration, which may help distinguish the different implementation issues as they are approaching integration from different perspectives.
For the other application, 5fa0c357-c924-4ee3-aa33-140906f47bb4.
I wasn’t involved with the creation of this application and so unsure as to what had or hadn’t been configured in terms of onboarding etc.
Perhaps with the exception of the ODS code, the other custom attributes (including the ASID) were added whilst trying to prove at what point the API requests were stalling and so will contain invalid values.
These obviously need reconfiguring.
Do we need to obtain a value for the NHSD-Target-Identifier for these apps?
Good Morning,
Okay as you are exploring app + healthcare worker its important you have that seperation.
Please can you create an additional application, but this time set the product for healthcare worker.
Follow section 2.1 for instructions https://digital.nhs.uk/services/e-referral-service/api/integration-process/stage-2-build
The access mode (2.15) here is important - I’ll then make a request to link the new app to an ASID.
You’ll then have x1 app restricted and x1 healthcare worker application. Please post the new app ID when you’ve done that.
morning Tony
Thanks again for the update.
A new e-Referral Service - Healthcare Worker restricted application has been created.
App Id is 062ac9b2-7ff5-434f-ab7a-3552bd33b491
I have made the request, will respond when complete.
That change has been made - the app should now be ready to use. Use this one for any healthcare worker calls.
morning Tony
Thanks for the update and setting up of the new user-restricted health care worker application.
The request was originally raised to ask for your help in setting up the application restricted apps.
5fa0c357-c924-4ee3-aa33-140906f47bb4
d2e09b90-865e-423b-a7aa-82007da69874 - believe this one is configured correctly
These applications will use application restricted API calls for:
e-Referral Service - Application Restricted
Booking and Referral FHIR API
Is this something you can advise on please as I remember you looking at the configuration for 5fa0c357-c924-4ee3-aa33-140906f47bb4 and advising that the configuration was incorrect and that perhaps this application has not been onboarded.