Deed API

Name: Deed API API
Brand: Deed API
Availability: InStock

✓ Official Vendor SpecFinanceAccountingnone2 EndpointsREST

For Agents

Create and retrieve digital mortgage deeds with HM Land Registry's Deed API to support property registration workflows.

Connect the Deed API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Deed API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Deed API API.

Submit a new digital mortgage deed payload for registration with HM Land Registry

Retrieve a deed document by its reference for review or downstream signing

Extract the structured deed contents for storage in a property workflow system

Validate deed payload contents against the schema before submission

GET STARTED

Start building with Deed API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Deed API API for, with concrete tasks.

★ Digital Mortgage Deed Submission

A conveyancing platform creates a digital mortgage deed by posting the structured payload to the Deed API, receiving a deed reference that the borrower and lender can later sign. This replaces the paper deed step in the property purchase or remortgage workflow and ties into HM Land Registry's wider digital registration process.

POST a deed payload containing borrower, lender, charge, and property details to /deed/ and store the returned deed reference for the e-signature step.

Deed Retrieval for Review

A solicitor's case management tool fetches an existing deed by reference to display its contents to the client before signing or to attach the document to a case file. The Deed API returns the structured deed payload, which the application can render in a human-readable form. Useful for audit, review, and reconciliation tasks.

GET /deed/{deed_reference} for the supplied reference and surface the borrower, lender, and property fields for client review.

AI Agent Conveyancing Assistant

An AI agent embedded in a conveyancing workflow uses the Deed API through Jentic to draft and submit a digital mortgage deed, then retrieve it for signing. The agent searches Jentic for deed submission, loads the schema, and executes the call without manually wiring HM Land Registry endpoints. This shortens the time from instruction to signing-ready deed.

Use Jentic to submit a new deed for property TT12345 with the supplied borrower and lender details, then immediately GET the deed by the returned reference to confirm the payload.

Key Endpoints

2 endpoints — the hm land registry deed api supports the digital mortgage deed workflow used to register a deed against a property in england and wales.

METHOD

PATH

DESCRIPTION

POST

/deed/

Create a new digital mortgage deed payload.

GET

/deed/{deed_reference}

Retrieve a deed by its reference.

POST

/deed/

Create a new digital mortgage deed payload.

GET

/deed/{deed_reference}

Retrieve a deed by its reference.

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Any credentials issued by HM Land Registry for the digital mortgage service are stored encrypted in the Jentic vault. Agents receive scoped tokens at execution time so the underlying credentials never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a digital mortgage deed') and Jentic returns the Deed API's matching operation with its input schema, so the agent can submit without browsing HM Land Registry docs.

Time to first call

Direct Deed API integration: 1-2 days to wire the deed schema, error handling, and retrieval flow. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

GOV.UK API

GOV.UK exposes content and notification services that pair with HM Land Registry workflows.

Use GOV.UK alongside the Deed API when a workflow needs official government content or notifications in addition to deed registration.

Complementary

PandaDoc

PandaDoc handles document signing flows that can capture borrower and lender signatures on a generated deed.

Use PandaDoc after creating a deed when the workflow needs a general-purpose e-signature step outside the Land Registry signing service.

Complementary

SignRequest

SignRequest provides simple e-signature flows that complement the Deed API's document creation step.

Choose SignRequest when a lightweight, low-cost signing layer is needed on top of the deed produced by HM Land Registry.

FAQs

Specific to using Deed API API through Jentic.

What authentication does the Deed API use?

The published OpenAPI spec does not declare a security scheme. In practice the digital mortgage service is restricted to authorised conveyancers and lenders; access is arranged with HM Land Registry rather than self-service. Through Jentic, any credentials configured for the API are stored encrypted in the vault and never enter the agent context.

Can I create a digital mortgage deed with the Deed API?

Yes. POST /deed/ accepts a structured deed payload and returns a deed reference that downstream signing and registration steps use to identify the deed.

Can I retrieve an existing deed with the Deed API?

Yes. GET /deed/{deed_reference} returns the structured deed document for the supplied reference, which clients can render for review or attach to a case file.

What are the rate limits for the Deed API?

The spec does not enumerate rate limits. As an HM Land Registry service, throughput expectations are governed by the digital mortgage onboarding agreement; check with Land Registry directly for production limits.

How do I submit a deed through Jentic?

Search Jentic for 'create a digital mortgage deed', load the operation schema, and POST the payload to /deed/. Capture the returned deed_reference for the signing step.

Is the Deed API free to use?

There is no per-call fee in the spec; access is governed by HM Land Registry's digital mortgage service agreements rather than a public pricing tier.