Skip to main content
Release notes

September 2026

Changes listed in these release notes are for version 1.1 of the submit an application to change the Land Register service only, and include:

This release does not contain breaking changes.

New functionality

This release introduces the following new functionality.

Search reference validation

You can now provide the reference number of the search certificate for an official search, using the search_reference parameter. Applications with search references that match the highest priority search on the daylist can benefit from faster processing.

Note:

Search reference validation is currently limited to:

  • official searches with a priority of whole, which are for a valuable consideration, such as a charge or purchase
  • title charge transactions at title level (transaction code "C")

API updates

  • Submit an application API: POST /v1/applications now supports nine-character search certificate reference numbers in the search_reference parameter of the titles object. The search_reference parameter was previously in the transactions object.

  • Application information API: GET /v1/applications/{APPLICATION_REQUEST_ID}/information now returns warning messages for submitted search certificate reference numbers that do not match the highest priority search.

Digital mortgage submissions

Note:

Digital mortgage submissions are currently limited to:

  • integrators who already use our digital mortgage service, and their customers
  • single title charge transactions with a title scope of WHOLE

A digital mortgage application is now accepted without an attached legal charge document or deed. Instead, when you submit an application, provide the electronic mortgage deed (e-MD) reference, using the mdref parameter.

The e-MD reference is required for all digital mortgages applications that have been created using our digital mortgage service. Applications with an incorrect e-MD reference will be requisitioned.

API updates

New transaction types

You can now submit 12 additional types of transaction.

  • Adverse possession (under schedule 12) (ADV1S12)
  • Second notice of adverse possession (ADV1NT2)
  • Cancellation of adverse possession (CADV)
  • Removal of adverse possession entry (proprietorship protective entry) (RADV)
  • Application to note appointment of an administrator (NAOA)
  • Registering official receiver in bankruptcy as proprietor (RORBAP)
  • Registering trustee in bankruptcy as proprietor (RTBAP)
  • New lease - including profit a prendre in gross (PAPIG) (DPR)
  • New lease - taking effect more than three months from the date of the grant (DFL6)
  • Withdrawal of a restriction (WDR)
  • De-registration of a manor (DM)
  • Correction or alteration registration (mistakes, updates or superfluous entries) (SCH)

For more information about which transactions are accepted for different application types, see the Valid transaction types per application type section of the Submit an application API technical guide.

API updates

Supporting documents for bankruptcy and administration transactions

You can also upload the following new types of document to provide supporting evidence for bankruptcy and administration transactions (NAOA, RORBAP, and RTBAP):

  • Certificate by the official receiver (OR_CERT_BE)
  • Certificate by the trustee in bankruptcy that the registered estate or charge is comprised within the bankrupt’s estate (TIB_CERT_BE)
  • Certified copy of the certificate of appointment as trustee by a meeting of the bankrupt’s creditors (BCA_TRUST)
  • Certified copy of the certificate of appointment as trustee by the Secretary of State (SSA_TRUST)
  • Notice of appointment (NOTICE_OF_APPOINTMENT)
  • Office copy or certified copy of the bankruptcy order (BANKRUPTCY_COURT_ORDER)
  • Office copy or certified copy of the order of the court appointing the trustee (TRUSTEE_COURT_ORDER)

For full information about how these document types map to transactions, see the Transaction and document mapping section of the Submit an application API technical guide.

API updates

  • Send a Document API: POST /v1/documents/url now supports the new document types in the document_type parameter of the data object.

  • Submit an application API: POST /v1/applications now supports codes for the new document types in the type parameter of the documents object for a property.

New party roles

Three new party roles are also for bankruptcy and administration transactions (NAOA, RORBAP, and RTBAP):

  • APPLICANT
  • OFFICIAL_RECEIVER
  • TRUSTEE_IN_BANKRUPTCY

API updates

Submit an application API: POST /v1/applications now supports the new party roles in the role property in the party_roles object for a transaction.

Enhancements

This release includes the following service improvements.

Property address information for titles

You can now, optionally, submit property address information for titles, including:

  • Building description (required) - the postal number or name of the residential or commercial premises
  • Organisation name (optional)
  • Street (optional)
  • Post town (optional)
  • County (optional)
  • Postcode (optional)
  • UPRN (optional)

API updates

  • Submit an application API: POST /v1/applications now supports additional address properties for the property_address under the properties object in the titles object.

Improved validation messages

Improved validation error messages aim to help customers resubmit their failed applications successfully. Returned error messages are now:

  • clear, concise, and actionable
  • ready for use in customer-facing applications by integrators

API updates

  • Application information API: GET /v1/applications/{application_request_id}/information now returns the updated error messages for failed application submissions.

Improved notifications

As part of the ongoing development of application notifications, we have introduced additional validation and a new parameter, subject_type.

Validation for the following parameters has been updated:

  • subject: Maximum length increased from 64 to 128 characters and the format updated to allow spaces
  • notification_type: Format updated to allow spaces

The subject_type parameter is optional. Currently, the only valid value is application.

API updates

Fixes

This release includes the following bug fixes.

Completion documents for multi-title applications

Multiple title application completion documents are now fully issued for the lead application and any attached applications, including:

  • a Register Completion Sheet (RCS)
  • a Title Information Document (TID)
  • a copy of the register

If you send a request for application information pre-completion, all correspondence from Land Registry is also returned for both the lead application and any attached applications. On completion, references to this correspondence are removed.

API updates

  • Application information API: GET /v1/applications/{APPLICATION_REQUEST_ID}/information now returns a new title_no field, and the hmlr_reference field in the correspondences object of a successful response. The two fields identify the title and Land Registry application to which the correspondence record applies.
Note:

We have added the title_no field, and duplicated thehmlr_reference field, to help integrators handling applications that contain multiple titles. Existing functionality will not be affected by this update.

Application statuses

The following application statuses are now correctly returned by the Application information API:

  • CANCELLED
  • COMPLETED

These two statuses were missing from the Open API specification in version 1.0.

API updates

  • Application information API: GET /v1/applications/{APPLICATION_REQUEST_ID}/information now returns the CANCELLED and COMPLETED application statuses in the status field. Additionally, the data object has been renamed from ApplicationInformationResponse to ApplicationInformation.

Use of the register_action parameter

Due to issues with applications failing validation, the register_action parameter is no longer available for use in the Submit an application API, and will be removed from the Open API specification in a forthcoming release. This parameter is not required for the successful processing of an application.

API updates

  • Submit an application API: POST /v1/applications no longer includes the register_action parameter in the Party object.

Overseas addresses

The validation for overseas addresses has been updated to include the first line of the address.

  • Required in version 1.0: country parameter. In this version, the requirement for a line1 parameter was omitted in error
  • Required in version 1.1: country and line1 parameters

API updates

  • Submit an application API: POST /v1/applications now requires the line1 parameter in the details object for an overseas address.