# uk-who/bulk-calculation failure with 404

**Category:** [Growth Charts](https://forum.rcpch.tech/c/rcpch-digital-growth-charts/6)
**Created:** 2025-11-25 17:46 UTC
**Views:** 13
**Replies:** 3
**URL:** https://forum.rcpch.tech/t/uk-who-bulk-calculation-failure-with-404/635

---

## Post #1 by @richardrobinson

I hope someone can help…

I am wanting to extend our application to use the bulk uk-who/bulk-calculation API endpoint. Using our subscription key I can access uk-who/calculation but not the bulk endpoint.

However when I connect (I have substituted XXX for our subscription key in the output below) I get a 404 back:

```
curl -v --fail-with-body \

-X POST https://api.rcpch.ac.uk/growth/v1/uk-who/bulk-calculation \

-H “Content-Type: application/json” \

-H “Accept: application/json” \

-H “Subscription-Key: XXX” \

-H “Origin: https://growth.rcpch.ac.uk/” \

–data '[

{

  "birth_date": "2015-01-01",

  "observation_date": "2024-09-30",

  "sex": "male",

  "measurement_method": "bmi",

  "observation_value": 18.5

},

{

  "birth_date": "2015-02-14",

  "observation_date": "2024-09-30",

  "sex": "female",

  "measurement_method": "bmi",

  "observation_value": 17.3

}

]’

Note: Unnecessary use of -X or --request, POST is already inferred.

*   Trying 4.158.171.31:443…

* Connected to api.rcpch.ac.uk (4.158.171.31) port 443 (#0)

* ALPN, offering h2

* ALPN, offering http/1.1

*  CAfile: /etc/ssl/certs/ca-certificates.crt

*  CApath: /etc/ssl/certs

* TLSv1.0 (OUT), TLS header, Certificate Status (22):

* TLSv1.3 (OUT), TLS handshake, Client hello (1):

* TLSv1.2 (IN), TLS header, Certificate Status (22):

* TLSv1.3 (IN), TLS handshake, Server hello (2):

* TLSv1.2 (OUT), TLS header, Finished (20):

* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):

* TLSv1.2 (OUT), TLS header, Certificate Status (22):

* TLSv1.3 (OUT), TLS handshake, Client hello (1):

* TLSv1.2 (IN), TLS header, Finished (20):

* TLSv1.2 (IN), TLS header, Certificate Status (22):

* TLSv1.3 (IN), TLS handshake, Server hello (2):

* TLSv1.2 (IN), TLS header, Supplemental data (23):

* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):

* TLSv1.3 (IN), TLS handshake, Certificate (11):

* TLSv1.3 (IN), TLS handshake, CERT verify (15):

* TLSv1.3 (IN), TLS handshake, Finished (20):

* TLSv1.2 (OUT), TLS header, Supplemental data (23):

* TLSv1.3 (OUT), TLS handshake, Finished (20):

* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384

* ALPN, server did not agree to a protocol

* Server certificate:

*  subject: CN=api.rcpch.ac.uk

*  start date: Jul 31 00:00:00 2025 GMT

*  expire date: Jan 31 23:59:59 2026 GMT

*  subjectAltName: host “api.rcpch.ac.uk” matched cert’s “api.rcpch.ac.uk”

*  issuer: C=US; O=DigiCert, Inc.; CN=GeoTrust Global TLS RSA4096 SHA256 2022 CA1

*  SSL certificate verify ok.

* TLSv1.2 (OUT), TLS header, Supplemental data (23):

> POST /growth/v1/uk-who/bulk-calculation HTTP/1.1

> Host: api.rcpch.ac.uk

> User-Agent: curl/7.81.0

> Content-Type: application/json

> Accept: application/json

> Subscription-Key: XXX

> Origin: https://growth.rcpch.ac.uk/

> Content-Length: 356

>

* TLSv1.2 (IN), TLS header, Supplemental data (23):

* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):

* TLSv1.2 (IN), TLS header, Supplemental data (23):

* Mark bundle as not supporting multiuse

< HTTP/1.1 404 Resource Not Found

< Content-Length: 54

< Content-Type: application/json

< Access-Control-Allow-Origin: *

< Access-Control-Expose-Headers: Content-Length

< Date: Fri, 21 Nov 2025 16:30:14 GMT

<

* Connection #0 to host api.rcpch.ac.uk left intact

curl: (22) The requested URL returned error: 404

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

---

## Post #2 by @pacharanero

Hi @richardrobinson - I think the issue is our end. The Bulk Calculation endpoint is new, and although it's in the GitHub repo and the backend API server is on the same version (4.3.5) as `main`, we haven't updated the openAPI spec in the middleware (Azure APIM) service. Hence the middleware is not aware of the bulk endpoint and returns 404.

Should be a quick fix though, we'll keep you posted.

---

## Post #3 by @michael.barton

Hi @richardrobinson, thanks for reporting! This is my fault, the schema doesn’t automatically update in our API gateway ( https://github.com/rcpch/digital-growth-charts-server/issues/229 ).

I’ve fixed it now.

Note that the bulk endpoint can only be used for one child at a time - you specify demographic data at the top level and then pass a list of observations:

```json
{
  "measurement_method": "height",
  "birth_date": "2020-04-12",
  "sex": "female",
  "observations": [
    {
      "observation_date": "2028-06-12",
      "observation_value": 115
    },
    {
      "observation_date": "2028-12-12",
      "observation_value": 130
    }
  ]
}
```

---

## Post #4 by @richardrobinson

Thank you both for the speedy reply. My intention was to use it to bulk calculate a school class of children, but I may be able to use it on another occasion - thanks for clearing that up.

---


**Canonical:** https://forum.rcpch.tech/t/uk-who-bulk-calculation-failure-with-404/635
**Original content:** https://forum.rcpch.tech/t/uk-who-bulk-calculation-failure-with-404/635