Request Official Copies API

Order official Land Registry documents directly from your software.

Access official copies of title registers, title plans, leases, charges and other available property documents using our API.

Search for properties, check which documents are available and request official copies directly from HM Land Registry. Documents are delivered instantly as downloadable PDFs, making it easy to automate document ordering within your existing applications.

How does the Official Copies API work?

Our API lets you find a property, identify its available documents and request official copies using three straightforward API calls.

What documents can you request?

The API provides access to official copies of documents held by HM Land Registry for registered properties in England and Wales.

Title Register

An official title register contains information about a registered property's legal ownership and title. Depending on the property, it can include registered proprietors, title number, tenure, registered mortgages and charges, restrictions, notices, and rights or covenants affecting the property. An official copy of the title register can be used as evidence of ownership, including where documentary evidence is needed for legal proceedings.

Title Plan

An official title plan shows the location and general boundaries of registered land. It helps identify the extent of the registered title and should be read alongside the title register. Title plans generally show general boundaries rather than precise legal boundary measurements.

Lease Documents

Official copies of filed leases may be available for leasehold properties. These can contain information about the duration of the lease, rights, obligations and conditions affecting the property.

Charge Documents

Official copies of charge documents can contain information relating to registered mortgages or other legal charges.

Other Filed Documents

Depending on availability, other documents may include transfers, deeds, agreements and documents referred to in the title register.

Note: Not every document mentioned in a title register is necessarily held on file or available for ordering. The API's document availability endpoint identifies which documents can be requested.

An API alternative to OC1 and OC2 document requests

HM Land Registry's OC1 and OC2 forms are used to request different types of official copies.

• Form OC1 is used to request official copies of title registers and title plans, as well as certain other official title information.
• Form OC2 is used to request official copies of documents held on file, such as leases, charges and transfer deeds.

The PropertyChecker Official Copies API allows developers to automate requests for many of the same types of documents, directly within their own software. Instead of preparing individual document applications, your application can identify a property, retrieve its available documents and submit requests programmatically. Most eligible documents are delivered immediately as PDFs.

Why use our Official Copies API?

Genuine official copies

Request official documents from HM Land Registry.

Instant PDFs for most requests

The vast majority of successful document orders return a PDF download link immediately.

Automate document ordering

Add Land Registry document ordering to your property platform, case management system or internal software.

Search by postcode

You don't need to know the property's title number before starting. Search by postcode and identify the available documents.

No subscription or minimum top-up

Use a prepaid API balance. Add funds when you need them, with no recurring subscription requirement.

Retrieve existing documents

Access previously purchased documents through the API without authorising another purchase, and generate fresh download links after previous links expire.

Who can use the Official Copies API?

Getting Started with the Official Copies API

Integrating the Official Copies API takes just a few minutes. You will need a PropertyChecker account, an API application and an API key:

1. Visit the PropertyChecker API documentation.
2. Create or select an API application in your account dashboard.
3. Copy your API key.
4. Add funds to your prepaid account balance as required.
5. Start making requests.

Authentication

Authentication uses the x-api-key HTTP header. All endpoints in this guide accept POST requests with JSON bodies.

x-api-key: YOUR_API_KEY
Content-Type: application/json

API keys for the Official Copies API should be stored securely on your server (for example, in environment variables) and never exposed in publicly accessible frontend code.

Step 1: Find a property

POST https://api.propertychecker.co.uk/propertytools.api.v1.Public/ListProperties

Search for properties within a UK postcode to retrieve matching records and their unique Property Identifier (PID).

Example Request Body

{
  "postcode": "EX4 9BT"
}

Example Response (Shortened)

{
  "property": [
    {
      "address": {
        "paon": "12",
        "street": "Meadowbrook Rise",
        "town": "Holmbury",
        "county": "Devon",
        "postcode": "EX4 9BT",
        "description": "12 Meadowbrook Rise, Holmbury"
      },
      "pid": "2d98ff20adfa491da0d668fc0ab53f6e",
      "dataSource": "internal",
      "type": "Semi-Detached"
    },
    {
      "address": {
        "paon": "14",
        "street": "Meadowbrook Rise",
        "town": "Holmbury",
        "county": "Devon",
        "postcode": "EX4 9BT",
        "description": "14 Meadowbrook Rise"
      },
      "pid": "044a761117b035a97850c245f7e77445",
      "dataSource": "internal",
      "type": "Mid Terrace"
    },
    {
      "address": {
        "postcode": "EX4 9BT",
        "description": "Garage Associated With, 14 Meadowbrook Rise, Holmbury"
      },
      "pid": "bc91bf654811f1809f2bbb473e3d3e26",
      "dataSource": "internal"
    }
  ]
}

Actual responses may include additional property details, such as historic transaction records and valuation estimates. The primary fields needed for document ordering are:

• property[] — Array of matching properties for the postcode.
• address.description — The formatted address for identification.
• pid — The unique identifier required for Step 2.

Note: Results may list separate titles such as associated garages, parking spaces or leasehold flats. Ensure the intended property interest is selected before checking documents.

Step 2: Check available documents

POST https://api.propertychecker.co.uk/propertytools.api.v1.Public/ListAvailableDocuments

Submit either the Property ID (pid) obtained in Step 1 or a registered titleNumber to retrieve all official documents available from HM Land Registry for that property.

Example Request Body

{
  "pid": "044a761117b035a97850c245f7e77445"
}

Example Response

{
  "documents": [
    {
      "titleNumber": "DN546531",
      "type": "Charge",
      "typeCode": "20",
      "entryNumbers": [
        "B2",
        "C2",
        "C3"
      ],
      "documentTypeCode": "50",
      "documentDate": "2006-12-22",
      "titleNumberFiledUnder": "DN546531",
      "availableForDownload": true,
      "titleNumberMatches": true,
      "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
      "tenure": "Leasehold",
      "titleNumberHasPendingApplications": false
    },
    {
      "titleNumber": "DN546531",
      "type": "Lease",
      "typeCode": "20",
      "entryNumbers": [
        "A2"
      ],
      "documentTypeCode": "90",
      "documentDate": "2006-12-22",
      "titleNumberFiledUnder": "DN546531",
      "availableForDownload": true,
      "titleNumberMatches": true,
      "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
      "tenure": "Leasehold",
      "titleNumberHasPendingApplications": false
    },
    {
      "titleNumber": "DN546531",
      "type": "Title Register",
      "typeCode": "10",
      "documentTypeCode": "10",
      "availableForDownload": true,
      "titleNumberMatches": true,
      "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
      "tenure": "Leasehold",
      "titleNumberHasPendingApplications": false,
      "backdated": false
    },
    {
      "titleNumber": "DN546531",
      "type": "Title Plan",
      "typeCode": "10",
      "documentTypeCode": "20",
      "availableForDownload": true,
      "titleNumberMatches": true,
      "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
      "tenure": "Leasehold",
      "titleNumberHasPendingApplications": false,
      "backdated": false
    }
  ]
}

Response Fields

Some fields may be omitted depending on the document type. Only documents where availableForDownload: true can be requested. When requesting a document in Step 3, pass the exact fields returned by this endpoint rather than generating your own identifiers.

Step 3: Request an official copy

POST https://api.propertychecker.co.uk/propertytools.api.v1.Public/GetOfficialCopy

This endpoint is used to purchase a new official copy or retrieve an existing, previously purchased document. Construct the request body using the exact metadata returned from ListAvailableDocuments.

Example Request Body

{
  "titleNumber": "DN546531",
  "type": "Lease",
  "typeCode": "20",
  "documentTypeCode": "90",
  "documentDate": "2006-12-22",
  "titleNumberFiledUnder": "DN546531",
  "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
  "tenure": "Leasehold",
  "allowPurchase": false
}

Example Successful Response

{
  "titleNumber": "DN546531",
  "type": "Lease",
  "typeCode": "20",
  "documentTypeCode": "90",
  "documentDate": "2006-12-22",
  "titleNumberFiledUnder": "DN546531",
  "availableForDownload": true,
  "titleNumberMatches": true,
  "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
  "orderStatus": "Completed",
  "filePath": "https://storage.googleapis.com/official_copies/...",
  "tenure": "Leasehold",
  "titleNumberHasPendingApplications": false,
  "backdated": false,
  "allowPurchase": false
}

The response above illustrates a completed order (signed URL shortened for readability). Key points:

• orderStatus: "Completed" confirms the document is ready for immediate download.
• filePath provides a secure signed PDF download URL.
• Signed download URLs remain valid for seven days.
• Fresh signed URLs can be generated at any time by repeating the original request with allowPurchase: false.

Billing, caching and duplicate request protection

PropertyChecker operates a transparent prepaid API with no monthly subscription or minimum top-up. Visit the API documentation for current per-endpoint pricing.

When are document purchases charged?

A new document purchase is charged when HM Land Registry accepts the request. The vast majority of accepted requests return a downloadable PDF immediately. In rare cases where the document requires manual processing or upstream systems undergo maintenance, the fee is charged upon acceptance; if the document ultimately cannot be supplied, a credit for the purchase fee is automatically issued back to your PropertyChecker account balance. Requests rejected because the document is unavailable or the title number is incorrect do not incur a document purchase fee.

How caching works

Each API application has a configurable cache duration (default: 86,400 seconds / 24 hours), editable within your application settings on the Apps page. Caching prevents duplicate billing from accidental retries or coding loops.

Important: Caching alone does not guarantee against duplicate charges. The only guaranteed safeguard against initiating a new purchase is setting allowPurchase: false.

Store your order information

We recommend storing original request parameters, document types, title numbers and response metadata in your database. This makes it effortless to check order status, retrieve fresh PDF URLs or verify previous purchases without incurring additional charges.

What happens if a document requires manual processing?

While most official copy orders return a PDF instantly, some requests require manual processing, or are submitted when the HM Land Registry system is closed outside operating hours (11:00 PM – 6:30 AM). When this occurs, the request is accepted and queued, and the API returns:

{
  "titleNumber": "DN546531",
  "type": "Charge",
  "typeCode": "20",
  "documentTypeCode": "50",
  "documentDate": "2006-12-22",
  "titleNumberFiledUnder": "DN546531",
  "additionalInformation": "The document request has been accepted by HM Land Registry and is queued for manual processing.",
  "availableForDownload": false,
  "titleNumberMatches": true,
  "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
  "orderStatus": "Needs Manual Processing",
  "filePath": "",
  "tenure": "",
  "titleNumberHasPendingApplications": false,
  "backdated": false,
  "allowPurchase": true
}

This indicates that the order was accepted by HM Land Registry, but the PDF document is queued or being prepared. You will receive an automated email at your registered PropertyChecker account email address as soon as the document is ready.

You can also check the status programmatically by re-sending the original GetOfficialCopy request with allowPurchase: false. When processing completes, the API returns the standard completed response with the signed PDF URL in filePath. Do not submit a new purchase while waiting for processing.

Retrieve existing documents without purchasing again

To access a previously purchased document or refresh an expired download link, repeat the original GetOfficialCopy request with allowPurchase: false:

• If the document exists, the API returns the document metadata and a fresh signed download URL valid for 7 days.
• If no previous purchase exists, the API returns an HTTP 404 response without creating a purchase charge.

Example 404 Response (No Existing Purchase)

{
  "code": 5,
  "message": "No existing document found for this property. Please pass 'allowPurchase: true' with the request body to purchase this document.",
  "details": [
    {
      "@type": "type.googleapis.com/google.rpc.DebugInfo",
      "stackEntries": [],
      "detail": "internal"
    }
  ]
}

If you receive this response and your user confirms they wish to purchase the document, re-send the request with allowPurchase: true. Never retry automatically with purchases enabled.

Test the API without making a document purchase

You can test the end-to-end GetOfficialCopy flow without contacting HM Land Registry or incurring a document purchase fee by using the special test title number: "TEST".

Test Request Body

{
  "titleNumber": "TEST",
  "type": "Lease",
  "typeCode": "20",
  "documentTypeCode": "90",
  "documentDate": "2006-12-22",
  "titleNumberFiledUnder": "TEST",
  "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
  "tenure": "Leasehold",
  "allowPurchase": false
}

Test Response

{
  "titleNumber": "TEST",
  "type": "Lease",
  "typeCode": "20",
  "documentTypeCode": "90",
  "documentDate": "2006-12-22",
  "titleNumberFiledUnder": "TEST",
  "additionalInformation": "This is a test request. HM Land Registry was not contacted and no charge was incurred.",
  "availableForDownload": true,
  "titleNumberMatches": true,
  "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
  "orderStatus": "Completed",
  "filePath": "https://storage.googleapis.com/official_copies/sample/title-register.pdf?...",
  "tenure": "Leasehold",
  "titleNumberHasPendingApplications": false,
  "backdated": false,
  "allowPurchase": false
}

This mock request confirms that your application handles response parsing, order statuses and PDF downloads correctly without contacting HM Land Registry or deducting document purchase fees from your balance.

Integrate the API using an AI coding assistant

You can use an AI coding assistant to add the Official Copies API to an existing application. We've prepared a comprehensive prompt containing the API endpoints, request parameters, purchase safeguards and document retrieval processes.

Copy the prompt below into your preferred AI coding tool, add your API key and follow the setup instructions:

Integrate the PropertyChecker Official Copies API into my existing application.

Inspect the project and use the current programming language, framework, architecture, styling and authentication system.

Build an interface allowing users to:
Search for properties by postcode.
Select the correct property.
View official documents available for that property.
Retrieve existing documents or explicitly authorise new purchases.
Download completed documents as PDFs.
Check the status of documents requiring manual processing.

API base URL:
https://api.propertychecker.co.uk

Authentication headers:
x-api-key: YOUR_API_KEY
Content-Type: application/json

The API key must be stored securely on the server using an environment variable named PROPERTYCHECKER_API_KEY.
Never expose the key to the browser.

STEP 1
POST /propertytools.api.v1.Public/ListProperties
Example body:
{"postcode":"EX4 9BT"}
The response contains an array named property. Each record has a pid and address object.
Show the results and allow selection of a property.

STEP 2
POST /propertytools.api.v1.Public/ListAvailableDocuments
Example body:
{"pid":"PROPERTY_PID"}
The response contains a documents array.
Show each document's type, title number and availability.
Only allow ordering when availableForDownload is true.

STEP 3
POST /propertytools.api.v1.Public/GetOfficialCopy
Example request:
{
  "titleNumber": "DN546531",
  "type": "Lease",
  "typeCode": "20",
  "documentTypeCode": "90",
  "documentDate": "2006-12-22",
  "titleNumberFiledUnder": "DN546531",
  "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
  "tenure": "Leasehold",
  "allowPurchase": false
}
Use the selected document details returned by ListAvailableDocuments to construct the request.
Do not invent missing parameters.

PURCHASE RULES:
allowPurchase: false only retrieves existing documents or order statuses. It must not create a new purchase.
allowPurchase: true authorises a chargeable document purchase.
Never send allowPurchase: true automatically.
Require explicit user confirmation before making any purchase.
Show a warning that the request is chargeable and refer users to the current API pricing.

COMPLETED ORDERS:
orderStatus:"Completed" means the document is ready.
filePath contains a signed PDF download URL.
Display a download action.
Signed URLs expire after seven days.
To retrieve a fresh URL, repeat the original request with allowPurchase: false.

MANUAL PROCESSING:
orderStatus:"Needs Manual Processing" means the order was accepted but the PDF is not ready (for example, when queued for manual processing or requested outside HM Land Registry operating hours between 11PM and 6:30AM).
Display a pending status and a Check Status button.
Check Status must repeat the original request with allowPurchase: false.
Do not submit a new purchase.

ERROR HANDLING:
HTTP 404 with code 5 may indicate that no previously purchased document exists.
Display an appropriate message and allow the user to explicitly choose whether to make a new purchase.
Never automatically retry with allowPurchase: true.
Handle other API errors safely without assuming undocumented error formats.

TESTING:
Test GetOfficialCopy using this body:
{
  "titleNumber": "TEST",
  "type": "Lease",
  "typeCode": "20",
  "documentTypeCode": "90",
  "documentDate": "2006-12-22",
  "titleNumberFiledUnder": "TEST",
  "propertyDescription": "14 Meadowbrook Rise, Holmbury, EX4 9BT",
  "tenure": "Leasehold",
  "allowPurchase": false
}
This does not initiate a real document purchase.

Build secure server-side API routes or actions.
Store the original document request parameters and relevant response metadata if the project has a suitable database.
Never make a real document purchase during development or testing.
Preserve authentication and authorisation when allowing access to stored document data.
Provide an environment variable example, explain configuration and test the integration before completion.
Implement the full workflow using the project's existing design system and conventions.

Security and data protection

Official property documents may contain personal data, including proprietor names, addresses and details of financial or legal interests. When integrating the API, consider your obligations under UK GDPR and the Data Protection Act 2018:

• Secure storage: Store retrieved PDF documents in encrypted, access-controlled cloud storage or private application databases.
• Access control: Restrict document downloads to authorised users within your platform.
• Credential safety: Store API keys in secure server-side environment variables; never include them in client bundles.
• Handling signed URLs: Anyone with a valid signed download URL can access the document. URLs expire after seven days; do not expose them in public logs, tracking scripts or open frontend code.

Start requesting official property documents through our API

Whether you need to request a handful of documents or automate document ordering across a larger property platform, our API makes it straightforward to find properties, check availability and request official copies. Most documents are delivered instantly, and our prepaid billing means you can add funds when you need them. Create an API application, get your API key and start testing.