Gazette Data, UK API

Government / OAuth Advanced HTTPS
Varies by plan (check documentation)

Overview

The Gazette Data API provides access to official UK public record notices published in The London, Edinburgh, and Belfast Gazettes, including insolvency, company, and government notices. Authentication uses OAuth 2.0, so you will need to register for credentials before making requests. It is a specialized API useful for legal, financial, and compliance applications in the UK.

💡

Beginner Tip

Start by registering for an account at thegazette.co.uk to obtain OAuth credentials. The API supports Linked Data formats like Turtle and JSON-LD in addition to standard JSON, which makes it useful for semantic web projects.

Available Data

Use case: Integrate uk official public record api data into web and mobile applications
Gazette Data, UK data via REST API
JSON-formatted response data
Requires OAuth authentication

Example Response

JSON Response
{
  "status": "success",
  "data": {
    "result": "Data from Gazette Data, UK",
    "description": "UK official public record API",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

title Title of the official gazette notice
notice-code Unique code identifying the type of notice (e.g., insolvency, company registration)
publish-date Date the notice was officially published in ISO 8601 format
gazette-url Direct URL to the full text of the notice on thegazette.co.uk
edition Which Gazette edition published the notice: London, Edinburgh, or Belfast

Implementation Example

const url = "https://www.thegazette.co.uk/data";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "Authorization": "Bearer YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

401 Unauthorized Missing or expired OAuth access token in the request header
Complete the OAuth 2.0 flow to obtain a fresh access token and include it as Authorization: Bearer YOUR_TOKEN
Unexpected XML response The default response format is XML if no Accept header is sent
Always include the header Accept: application/json in your requests to receive JSON output
400 Bad Request on date filter Date parameters not in the expected ISO 8601 format
Use YYYY-MM-DD format for start-publish-date and end-publish-date parameters

Matrix Score Breakdown

🌐 Reachability 0/30
⚡ Speed 10/20
🔒 Security 15/15
🛠 Developer XP 3/20
✓ Reliability 0/15

Partially tested on Apr 5, 2026

Technical Specifications

Auth OAuth
HTTPS REQUIRED
CORS UNKNOWN
Category Government
Difficulty Advanced
Verified: 2026-04-04

Similar APIs

View All →