# UNKONWN ERROR for spine-directory/FHIR/R4/Endpoint

**URL:** <https://developer.community.nhs.uk/t/unkonwn-error-for-spine-directory-fhir-r4-endpoint/4562>\
**Category:** Spine Directory Service (SDS)\
**Tags:** fhir\
**Created:** [18 February 2025 05:24 UTC](https://developer.community.nhs.uk/t/unkonwn-error-for-spine-directory-fhir-r4-endpoint/4562 "2025-02-18T05:24:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Annick\_Guirate](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@Annick\_Guirate](https://developer.community.nhs.uk/u/Annick_Guirate)\
**Post date:** [18 February 2025 05:24 UTC](https://developer.community.nhs.uk/t/unkonwn-error-for-spine-directory-fhir-r4-endpoint/4562/1 "2025-02-18T05:24:51Z")

</div>

Hi Team,

I am trying to access the SDS (spine directory service FHIR API) to get the ASID and provide URL that would be consume in “Access Record HTML” . I am following the documentation as given on the link ([https://digital.nhs.uk/developer/api-catalogue/spine-directory-service-fhir#get-/Endpoint](https://digital.nhs.uk/developer/api-catalogue/spine-directory-service-fhir#get-/Endpoint)).  
Further, I have also seen the discussion on the link [SDS FHIR API (?Device endpoint) to fetch the End user's system ASID(consumer system), - #4 by chauhangaurav](https://developer.community.nhs.uk/t/sds-fhir-api-device-endpoint-to-fetch-the-end-users-system-asid-consumer-system/703/4)

The above discussion suggests that first request we need to invoke the SDS /Enpoint request, and the output response will further supply in the /Device request. The /Device response will have the SSPTO (ASID) and the provider URL. Please advise me if this understanding is correct.

Given below are the details of my request and FHIR API response . Could you please help me identifying the issue.

Thank you in advance.

Request URL: [https://int.api.service.nhs.uk/spine-directory/FHIR/R4/Endpoint](https://int.api.service.nhs.uk/spine-directory/FHIR/R4/Endpoint)  
Request QueryString: [https://fhir.nhs.uk/Id/ods-organization-code|B86071&identifier=https://fhir.nhs.uk/Id/nhsServiceInteractionId|urn:nhs:names:services:psis:REPC\_IN150016UK05](https://fhir.nhs.uk/Id/ods-organization-code%7CB86071&identifier=https://fhir.nhs.uk/Id/nhsServiceInteractionId%7Curn:nhs:names:services:psis:REPC_IN150016UK05)

Request Header: {Accept=[application/fhir+json], x-correlation-id=[2cd91016-949c-4a66-ac34-3aacc8f13a53]}  
Sending client request on thread  
1 \> GET [https://int.api.service.nhs.uk/spine-directory/FHIR/R4/Endpoint](https://int.api.service.nhs.uk/spine-directory/FHIR/R4/Endpoint)  
1 \> Accept: application/fhir+json  
1 \> x-correlation-id: 2cd91016-949c-4a66-ac34-3aacc8f13a53

Client response received on thread  
1 \< 401  
1 \< Connection: keep-alive  
1 \< Content-Length: 791  
1 \< Content-Type: application/json  
1 \< Date: Tue, 18 Feb 2025 04:46:00 GMT  
1 \< Strict-Transport-Security: max-age=31536000; includeSubDomains  
1 \< X-Correlation-ID: 2cd91016-949c-4a66-ac34-3aacc8f13a53

```
      {
        "resourceType": "OperationOutcome",
        "issue": [
          {
            "severity": "error",
            "code": "unknown",
            "details": {
              "coding": [
                {
                  "system": "https://fhir.nhs.uk/R4/CodeSystem/Spine-ErrorOrWarningCode",
                  "version": "1",
                  "code": "UNKNOWN_ERROR",
                  "display": "An unknown error occurred processing this request. Contact us for assistance diagnosing this issue: https://digital.nhs.uk/developer/help-and-support. (Message ID: rrt-8167670714985189407-a-geu2-831258-30928956-1)"
                }
              ]
            }
          }
        ]
      }

```

---

<div class="post-metadata">

**Author:** ![Rowan\_Gill](https://avatars.discourse-cdn.com/v4/letter/r/7bcc69/32.png) [@Rowan\_Gill](https://developer.community.nhs.uk/u/Rowan_Gill)\
**Post date:** [26 February 2025 09:37 UTC](https://developer.community.nhs.uk/t/unkonwn-error-for-spine-directory-fhir-r4-endpoint/4562/2 "2025-02-26T09:37:01Z")

</div>

Hello,

Could be a couple things so ill just list out what I think you could check!

If what you wrote for the URL and Querystring are a direct copy then you need to add “organization=” at the start of the querystring:

“organization=[https://fhir.nhs.uk/Id/ods-organization-code|B86071&identifier=https://fhir.nhs.uk/Id/nhsServiceInteractionId|urn:nhs:names:services:psis:REPC\_IN150016UK05](https://fhir.nhs.uk/Id/ods-organization-code%7CB86071&identifier=https://fhir.nhs.uk/Id/nhsServiceInteractionId%7Curn:nhs:names:services:psis:REPC_IN150016UK05)”

This works for me if I use my apikey which is my next question, I know you wouldn’t want to post that in here but double check that you are also sending the apikey header with the request, that belongs to an app that has access to the INT version of the SDS FHIR API.

This can be done through the developer portal where you can create an APIGEE app and onboard to the API - this will generate you an apikey that you can put in your request.

If you have any more issues with that then do let me know 🙂

Thanks,  
Rowan