# A030 - HTTP 403 Error

**URL:** <https://developer.community.nhs.uk/t/a030-http-403-error/916>\
**Category:** e-Referral Service FHIR API\
**Tags:** fhir\
**Created:** [10 May 2024 07:13 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916 "2024-05-10T07:13:50Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![jh398](https://avatars.discourse-cdn.com/v4/letter/j/cab0a1/32.png) [@jh398](https://developer.community.nhs.uk/u/jh398)\
**Post date:** [10 May 2024 07:13 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/1 "2024-05-10T07:13:50Z")

</div>

Hi  
After setting up INT environment with the test data, we are getting 403 error from A030 endpoint, with the follow response.

{  
“resourceType”: “OperationOutcome”,  
“meta”: {  
“lastUpdated”: “2022-03-01T10:00:00.42Z”  
},  
“issue”: [  
{  
“severity”: “error”,  
“code”: “forbidden”,  
“details”: {  
“coding”: [  
{  
“system”: “[https://fhir.nhs.uk/CodeSystem/http-error-codes](https://fhir.nhs.uk/CodeSystem/http-error-codes)”,  
“code”: “REC\_FORBIDDEN”  
}  
]  
},  
“diagnostics”: “Example diagnostics message.”  
}  
]  
}

Can someone help in diagnosing this error?

thanks

Jeff

---

<div class="post-metadata">

**Author:** ![adam.oldfield](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/adam.oldfield/32/327_2.png) [@adam.oldfield](https://developer.community.nhs.uk/u/adam.oldfield)\
**Post date:** [10 May 2024 08:07 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/2 "2024-05-10T08:07:23Z")

</div>

Hi @jh398,

We will need more information in order to be able to trace your request.

Can you please provide the X-Correlation-ID or X-Request-ID and the date/time the call was made.

Thanks,

Adam.

---

<div class="post-metadata">

**Author:** ![jh398](https://avatars.discourse-cdn.com/v4/letter/j/cab0a1/32.png) [@jh398](https://developer.community.nhs.uk/u/jh398)\
**Post date:** [11 May 2024 02:25 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/3 "2024-05-11T02:25:50Z")

</div>

Hi Adam,  
x-correlation-id : fd8d59ef-e34f-4d4b-bef4-bb3d86203f92

thanks

Jeff

---

<div class="post-metadata">

**Author:** ![adam.oldfield](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/adam.oldfield/32/327_2.png) [@adam.oldfield](https://developer.community.nhs.uk/u/adam.oldfield)\
**Post date:** [13 May 2024 07:47 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/4 "2024-05-13T07:47:32Z")

</div>

@nhserspartners It looks like there is an issue with the configured ASID. The error is stating that ASID 200000039320 cannot be found in SDS.

Can you investigate?

---

<div class="post-metadata">

**Author:** ![LucyK](https://avatars.discourse-cdn.com/v4/letter/l/ba8739/32.png) [@LucyK](https://developer.community.nhs.uk/u/LucyK)\
**Post date:** [13 May 2024 15:08 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/5 "2024-05-13T15:08:41Z")

</div>

@adam.oldfield and @jh398 - Jeffrey, it looks as though you’re trying to use your Production ASID in INT. Your INT ASID is 200000002219

---

<div class="post-metadata">

**Author:** ![LucyK](https://avatars.discourse-cdn.com/v4/letter/l/ba8739/32.png) [@LucyK](https://developer.community.nhs.uk/u/LucyK)\
**Post date:** [13 May 2024 18:02 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/6 "2024-05-13T18:02:25Z")

</div>

@adam.oldfield @jh398 I’ve just double checked the full set up - I set you up on 2nd May with the following details:

Cinapsis-eRs-Int and Application ID: 9f41f810-8856-45be-96cb-dadc9a6dcb8a and ASID 200000002219 with test data I sent you on 18th April

---

<div class="post-metadata">

**Author:** ![hayward](https://avatars.discourse-cdn.com/v4/letter/h/b9e5f3/32.png) [@hayward](https://developer.community.nhs.uk/u/hayward)\
**Post date:** [14 May 2024 13:09 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/7 "2024-05-14T13:09:43Z")

</div>

Interesting enough , we had a working integration until Thursday. Our CIS authentication is working and our ERS authorization exchange is working as well. **However** the only call that seems to work for us is A030 which is the Business function call. Any call to A004, A005, A029 are returning a 403 Forbidden error.

This might indicate a wider issue in the INT environment?

---

<div class="post-metadata">

**Author:** ![adam.oldfield](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/adam.oldfield/32/327_2.png) [@adam.oldfield](https://developer.community.nhs.uk/u/adam.oldfield)\
**Post date:** [14 May 2024 15:26 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/8 "2024-05-14T15:26:55Z")

</div>

Hi @hayward,

Looking at the logs for the latest 403 code returned to you was at 14/05/2024  
09:47:51.753 (UTC).

403 was returned as user `555302836103` is attempting to select the `REFERRING_CLINICIAN` (via header `NHSD-eRS-Business-Function`) role at Organisation with ODS Code `R69` (via header `NHSD-End-User-Organisation-ODS`) - the user does **not** have a role at that organisation.

`R69` is the test organisation used in the API sandbox (used by “Try this API” in the documentation). I don’t think your user will have a role at this organisation.

Please use the result of A030 to determine the applicable organisation/role combinations.

Thanks.

---

<div class="post-metadata">

**Author:** ![hayward](https://avatars.discourse-cdn.com/v4/letter/h/b9e5f3/32.png) [@hayward](https://developer.community.nhs.uk/u/hayward)\
**Post date:** [15 May 2024 14:22 UTC](https://developer.community.nhs.uk/t/a030-http-403-error/916/9 "2024-05-15T14:22:54Z")

</div>

Thanks @adam.oldfield The R69 header was likely a remnant around us switching between dev (sandbox) and int environments during the day. Weirdly your reply **did** help us along. We recently had a lot of roles added and changed on our test smartcards, which now highlighted an issue around sending the correct OrgID in the headers (linked to the role / org chosen by the smartcard user)
