# Integration endpoint returning "ASID is not configured in the application" error **URL:** \ **Category:** e-Referral Service FHIR API\ **Tags:** fhir\ **Created:** [19 January 2026 13:10 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181 "2026-01-19T13:10:00Z")\ **Posts on this page:** 7\ **Page:** 3
**Author:** ![tony.marsh1](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/tony.marsh1/32/855_2.png) [@tony.marsh1](https://developer.community.nhs.uk/u/tony.marsh1)\ **Post date:** [23 February 2026 16:12 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181/41 "2026-02-23T16:12:48Z")
I’ve put that request in - is the screenshot above from a UUID that we’ve previously updated? Do you have the ID# ---
**Author:** ![Rinaldo\_Tempo](https://avatars.discourse-cdn.com/v4/letter/r/9fc29f/32.png) [@Rinaldo\_Tempo](https://developer.community.nhs.uk/u/Rinaldo_Tempo)\ **Post date:** [23 February 2026 16:29 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181/42 "2026-02-23T16:29:24Z")
Hi @tony.marsh1 The smart card ID used to book those eRS referrals was: 555295320104 ---
**Author:** ![Rinaldo\_Tempo](https://avatars.discourse-cdn.com/v4/letter/r/9fc29f/32.png) [@Rinaldo\_Tempo](https://developer.community.nhs.uk/u/Rinaldo_Tempo)\ **Post date:** [23 February 2026 17:06 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181/43 "2026-02-23T17:06:31Z")
Thanks @tony.marsh1 , our A005 call is now successful!! When we make the follow-up A042 call to retrieve the document, we get an error back, details below GET: [https://int.api.service.nhs.uk/referrals/FHIR/R4/Binary/3a410236-bfa1-4474-9bb1-08d5f6ac68bf](https://int.api.service.nhs.uk/referrals/FHIR/R4/Binary/3a410236-bfa1-4474-9bb1-08d5f6ac68bf) Authorization: Bearer REDACTED Accept: application/fhir+json X-Correlation-ID: 68763192-93a0-40c7-9b73-beaa8f8e4ad2\_2 Response: ```auto InvalidArgument Only one auth mechanism allowed; only the X-Amz-Algorithm query parameter, Signature query string parameter or the Authorization header should be specified Authorization Bearer vfcLw2K9wXzhGitDTHJRgZua27AV 87E7J5CHR554M1HK vqLr3Vc9cc3yn+PgkR1QJ+xymeRH0B4wSYFlVxPIYg91pBbjsOWcs936d0y/NEVXaJlcVpIxjFo= ``` ---
**Author:** ![tony.marsh1](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/tony.marsh1/32/855_2.png) [@tony.marsh1](https://developer.community.nhs.uk/u/tony.marsh1)\ **Post date:** [23 February 2026 18:15 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181/44 "2026-02-23T18:15:49Z")
Might need some help with that one. But seems to indicate you’re using two auth methods at once and getting an error. eg, signed JWT _and_ CIS auth header? ---
**Author:** ![Rinaldo\_Tempo](https://avatars.discourse-cdn.com/v4/letter/r/9fc29f/32.png) [@Rinaldo\_Tempo](https://developer.community.nhs.uk/u/Rinaldo_Tempo)\ **Post date:** [24 February 2026 08:52 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181/45 "2026-02-24T08:52:05Z")
Hi @tony.marsh1 It looks like it’s related to this issue. Leave this with us and we’ll see if we can work through it > [@Error with Retrieve attachment (A042, FHIR R4)](https://developer.community.nhs.uk/t/error-with-retrieve-attachment-a042-fhir-r4/9873/2): > > Hi Devendra, This error is happening because this endpoint uses a 307 Temporary Redirect to a pre-signed S3 download URL. Your initial call to A042 (/R4/Binary/{id}) should include the normal e-RS header, as you’ve said: Authorization: Bearer However, when the client follows the 307 redirect and makes the second request to the Location URL, it is still sending the same Authorization: Bearer header. Since the redirect URL already contains its own authentication details (for example X-Amz-A… Rinaldo ---
**Author:** ![Rinaldo\_Tempo](https://avatars.discourse-cdn.com/v4/letter/r/9fc29f/32.png) [@Rinaldo\_Tempo](https://developer.community.nhs.uk/u/Rinaldo_Tempo)\ **Post date:** [24 February 2026 14:10 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181/46 "2026-02-24T14:10:31Z")
@tony.marsh1 by not following the redirect on the A042 call and making a fresh call to AWS without the NHS access token, A042 now successfully returns the documents. Thanks for your help. ---
**Author:** ![tony.marsh1](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/tony.marsh1/32/855_2.png) [@tony.marsh1](https://developer.community.nhs.uk/u/tony.marsh1)\ **Post date:** [24 February 2026 16:30 UTC](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181/47 "2026-02-24T16:30:44Z")
no problem, good luck with your development - and thanks for using the forum so others can see similar issues/answers [Previous page](https://developer.community.nhs.uk/t/integration-endpoint-returning-asid-is-not-configured-in-the-application-error/10181.md?page=2)