Search API

API Endpoints

Census Demographics

Sex by Single Year of Age

Tokens
× 1

API Credit Cost

Endpoint Overview

Census2021 Demographics

The Sex by Single Year of Age endpoint delivers a detailed breakdown of the population in a postcode area, segmented by sex and each year of age for precise demographic analysis.

Coverage

EnglandEngland
WalesWales

Update Frequency

Census

Request Format

HTTP Method:

GET

To use the API you should send an HTTP request to the following endpoint URL. This will return a JSON response.

https://api.postcodearea.co.uk/census-ts009/?key=&postcode={postcode}

Note that your key has automatically been added to the API endpoint for convenience.

Querystring Parameters:

{postcode}

A valid UK postcode (e.g., SW1A 1AA). Note that you can send the postcode with or without the space separating the outward and inward codes. For example, both "SW1A 1AA" and "SW1A1AA" are both valid.

{api_key}

A valid API key that authenticates your account.

Authorisation

For every endpoint request your API Key should be sent as part of the querystring:

https://api.postcodearea.co.uk/census-ts009/?key={api_key}&postcode=WS3+3PD

For example:

https://api.postcodearea.co.uk/census-ts009/?key=&postcode=WS3+3PD

Example Request and Response

If the above URL endpoint exists and the API key is valid, our system will return the following example response:

https://api.postcodearea.co.uk/census-ts009/?key=&postcode=WS3+3PD
 

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'


[MySQL][ODBC 9.2(w) Driver][mysqld-8.0.41]Unknown column 'oa_ts009' in 'field list'


/default.asp, line 309

Error Handling

HTTP Status Code Error Message Reason
400 Invalid postcode format The postcode provided is not valid.
401 Unauthorised request API key missing or invalid.
404 Postcode not found No data available for the given postcode.
404 No Results Found No data available for the given radius.
429 Too many requests Exceeded rate limit.
500 Internal server error An unexpected issue occurred.

Caching Policy

You may temporarily cache data retrieved from the API for performance optimisation purposes, provided that the cached data is:

  1. Stored in-memory only (e.g., application-level cache).
  2. Retained for no longer than one hour.

Caching API data to any persistent storage, including but not limited to databases, files, or external systems, constitutes a breach of our API Terms and Conditions. Such actions are strictly prohibited to ensure data accuracy and compliance with our licensing agreements.

If you have specific requirements for extended caching, you must seek prior written consent from us.

Get started today

Ready to use this data for your own business or organisation? Sign up today and get immediate access to all the PostcodeArea API endpoints.

Sign up and access the API-or-Explore the docs

Share this page