Census Demographics
Legal Partnership Status

× 1
API Credit Cost
The Legal Partnership Status endpoint provides data on the marital and civil partnership statuses of residents in a postcode area.
Coverage

England

Wales
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/v1/census-ts002/?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/v1/census-ts002/?key={api_key}&postcode=WS3+3PD
For example:
https://api.postcodearea.co.uk/v1/census-ts002/?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/v1/census-ts002/?key=&postcode=WS3+3PD
{"data":[{"Postcode":"ST20 0LY","Total":279,"Never married and never registered a civil partnership":49,"Married or in a registered civil partnership":188,"Married or in a registered civil partnership; Married":188,"Married or in a registered civil partnership; Married; Opposite sex":188,"Married or in a registered civil partnership; Married; Same sex":0,"Married or in a registered civil partnership; In a registered civil partnership":0,"Married or in a registered civil partnership; In a registered civil partnership; Opposite sex":0,"Married or in a registered civil partnership; In a registered civil partnership; Same sex":0,"Separated but still legally married or still legally in a civil partnership":1,"Separated but still legally married or still legally in a civil partnership; Separated but still married":1,"Separated but still legally married or still legally in a civil partnership; Separated but still in a registered civil partnership":0,"Divorced or civil partnership dissolved":24,"Divorced or civil partnership dissolved; Divorced":24,"Divorced or civil partnership dissolved; Formerly in a civil partnership now legally dissolved":0,"Widowed or surviving civil partnership partner":17,"Widowed or surviving civil partnership partner; Widowed":17,"Widowed or surviving civil partnership partner; Surviving partner from civil partnership":0}],"response_time":0.0938,"Source":"PostcodeArea API","Output Area":"OA","Radius":10,"Distance Unit":"Mile","Records":1,"Unique Fields":1,"Referrer":"api.postcodearea.co.uk"}
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:
- Stored in-memory only (e.g., application-level cache).
- 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.