Vepler logo
v5.32.0

Check a title deed before you buy it, and read why a purchase was refused

Three free reads on title deeds: whether a title can be bought, what is pending against it, and what your account has already been charged for it.

Added

  • GET /v1/title-deeds/{titleNumber}/availability reports whether a title can be bought today, and why not. purchasable is the answer, reason_code is one of register_unavailable, applications_pending or null, and register.availability_code, title_plan.availability_code and title_status pass through the codes HM Land Registry returns, so treat those as open values rather than a fixed set. The check shares its refusal list with the purchase path, so a pre-check and the purchase itself cannot disagree. It costs nothing, and it does not require you to own the title.
  • GET /v1/title-deeds/{titleNumber}/applications lists what is pending against a title at HM Land Registry: the application type, who lodged it, its priority_date, priority_start_date and priority_end_date, and its progress. Each entry carries every field and most can be null, so handle an absent applicant, progress or priority date. An empty list means nothing is pending rather than a lookup that failed: a rejection comes back as 404 and an upstream failure as 502. Free to call.
  • GET /v1/title-deeds/{titleNumber}/purchase-status reports what your account has been charged for a title, without buying it again. A title you already hold comes back with its full payload, already_owned true and credits_charged of 0. One still being delivered answers 202. One your account has never held answers 404 with purchase_status of none or refunded, carrying failure_code and failure_message so a refusal that cannot clear on a retry is distinguishable from a transient one. It is free, so an integration reconciling an uncertain sale can ask rather than send the purchase again.

Changed

  • A title whose plan HM Land Registry can only issue by hand can now be bought. The register extract is asked for without the plan on those titles, so POST /v1/title-deeds/{titleNumber}/purchase returns the register-extract and official-title entries in documents and the title-plan entry is absent. GET /v1/title-deeds/{titleNumber}/availability reports this up front under title_plan.availability_code, so you can tell before you spend anything which documents a title will yield.

Affected endpoints