How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ordnance Survey Landing Page API

Ordnance Survey NGD API – Features

Ordnance Survey Landing Page API is one of 25 APIs that Ordnance Survey publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Landing Page. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.os.uk/features/ngd/ofa/v1, https://api.os.uk/maps/vector/ngd/ota/v1.

2 operations 2 paths 8 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.os.uk/features/ngd/ofa/v1
Authentication
API Key, API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Ordnance Survey Landing Page API declares 3 security schemes for authenticating requests. An API key is passed in the query as key (api-key). An API key is passed in the header as key (api-key-header). It supports OAuth 2.0 (oauth2) using the clientCredentials flow.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Landing Page 2

Ordnance Survey NGD API – Features

GET
/
OS NGD API – Features landing page
getLandingPageResponse → 200400405406
GET
/conformance
OS NGD API – Features conformance page
getConformanceResponse → 200400405406

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are exceptionDto (8 properties), link (8 properties), landingPage (4 properties), Link (4 properties). Each schema is shown below with its type and property counts.

Link
object
4 properties
ConformanceResponse
object
1 property
LandingPageResponse
object
3 properties
confClasses
object
1 property 1 required
exceptionDto
object
JSON schema for exceptions based on RFC 7807
8 properties 1 required
getConformance_200_response
link
object
8 properties 2 required
landingPage
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ordnance-survey-landing-page-api-openapi.yml Raw ↑

Other APIs Ordnance Survey publishes across the network.

OS Match & Cleanse API (withdrawn)
OS OAuth 2 API
Ordnance Survey Bounding box API
Ordnance Survey Collections API
Ordnance Survey Data Collections API
Ordnance Survey Data Packages API
Ordnance Survey Features API
Ordnance Survey Find API
Ordnance Survey Get Capabilities API
Ordnance Survey Nearest API
Ordnance Survey Open Data API
Ordnance Survey OS OpenData Users API
Where this information came from

This is an independent, third-party profile of Ordnance Survey Landing Page API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.