404 Resource Not Found for large number of urls

API Platform
1

Hello

I am receiving the following error message for a large number of urls when calling the API:

{ “statusCode”: 404, “message”: “Resource not found” }

I am interested in types ConditionsPage, ConditionsSubPage, MedicinesPage, ArticlePage and out of 3609 possible urls 406 return this error.

I have manually checked the below handful of urls and found their webpages to be active, yet even a single/basic call to the API returns the error:

https://api.nhs.uk/symptoms/fever-in-children/

https://api.nhs.uk/tests-and-treatments/cornea-transplant/

https://api.nhs.uk/symptoms/watering-eyes/

I’d be grateful if someone could please investigate the cause and advise accordingly.

Many thanks

Alex

2

Hi Alex,

The old developer portal and API management infrastructure hosted at api.nhs.uk (frequently referred to historically as the NHS Digital API platform / developer.api.nhs.uk) has been systematically transitioned to NHS England’s API platforms hosted under digital.nhs.uk/developer.

Before April 2025, the Conditions A to Z contained a broad mix of content including conditions, symptoms, tests, treatments, and baby-related information. This has been reorganized into a new Health A to Z hub with content logically grouped into dedicated sections.

The April 2025 update introduces new endpoints for ‘health-a-to-z’, ‘health-a-to-z/conditions’, ‘symptoms’, ‘tests-and-treatments’, ‘baby’ and ‘social-care-and-support’ that reflect the reallocation of these pages to new A to Z pages on the website.

You should be able to access the APIs through NHS Website Content API v2 - NHS England Digital

Thanks,

NHS England API Platform team

Please note: The API Platform team can only address queries relevant to the NHS England API Platform, including security, rate limiting, logging, monitoring and alerting. For any API, CIS2, NHS Login specific queries, please reach out to the relevant API / Service teams.

3

Hi Navin

Thank you for your response. I believe I understand the issue now.

Those examples I gave you all used api.nhs.uk when they should be using api.service.nhs.uk/nhs-website-content/. Using this instead these links now work and do not return the error. Scanning the other urls for which I have experienced this error, all use api.nhs.uk.

This does raise another issue though. The reason I was using api.nhs.uk for a subset of urls is because that is what is returned via the manifest pages (i.e. https://api.service.nhs.uk/nhs-website-content/manifest/pages). The majority of pages use api.service.nhs.uk/nhs-website-content/ but a large subset still use api.nhs.uk.

It is simple enough for me to correct these to api.service.nhs.uk/nhs-website-content/ locally, but I wanted to make you aware.

Thank you once again for your assistance.

Alex