Changelog

Clearer API reference

4 October 2026

Improvements

• Partner API: each endpoint in the API reference now shows a single, clear description instead of several joined together, and keeps its paragraphs and lists. Validation errors are shown as response examples.

Prop Chains are now free

3 October 2026

New

• Partner API: apps can now see a user's licences, redeem a licence, and manage their teams: list teams and members, create a team, invite, remove or change the role of a member, leave a team, give a member a licence from the team's pool, take it back, and move the user's own licences into a team. Team members are identified by an opaque id, never a user id.
• Partner API: apps can now list a user's notifications (all or just unread) and mark one or all of them as read.
• Partner API: apps can now read and change a user's own profile (name, contact and company details, and how widely each is shared), their status, and their weekly availability. The weekly availability is now replaced in one step, so a failed save can no longer leave someone with no availability.
• Creating and editing a Prop Chain is now free for everyone. Chains no longer need a licence and are never put into read-only mode.

Improvements

• Paid plans are now for Pro and Team features and Adaptive QR codes, not for how many chains you can create. The pay-as-you-go option for Prop Chains has been removed, and the pricing page, checkout and team licence screens have been updated to match.
• The partner API no longer reports whether a new chain was licensed (the licensed field has been removed from the create-chain response).

Fixes

• Teams are now private: you can only see the teams you belong to and their members, and nobody can add themselves to a team or change a team role by any route other than the team's own admin controls.
• If an invitation email (to a transaction or a team) can't be sent, you are now told, instead of being shown that the invite was sent. The invite itself is still created, so the person can find it under their invites. The partner API also reports correctly whether its invite emails went out.

Partner API access, and invites, licences and transaction access locked down

2 October 2026

New

• Partner applications can now connect to Land Your Home on a user's behalf. The user signs in and approves the connection on a new "Authorise access" screen showing which application is asking and what it can see, and can deny it. The partner API now issues each partner its own revocable keys with usage limits, and every request also needs the user's approval, so a partner can only see and do what that user could.

• Partners can now read a user's property chains, transactions, the people on a transaction, stages and properties through the API, with paging for long lists. Each person's name, email, phone and company are shown only as far as they have chosen to share them, and nothing outside what the user themselves could see is returned.

• Partners can now make changes on a user's behalf through the API: remove a link from a chain, merge two chains, leave a chain, and change their own or another person's role and permissions on a transaction. Each change needs both the partner's permission to write and the user's own permission on that transaction, and can never give someone more access than the user has themselves.

• Partners can now create a chain, link existing transactions together, and add a property to a chain through the API. Each step is checked against the user's own permissions on the chain.

• Partners can now read a single stage, add stages to a transaction, change them, set what a stage depends on, and delete them through the API. A stage can be assigned to the user or left unassigned, and a stage can only depend on another stage of the same transaction.

• Partners can now work with invitations and access requests through the API: see the invitations a user has received and sent, invite someone to a transaction (they get the usual email, and an in-app notification if they have an account), accept, decline or revoke invitations, ask to join a transaction, and accept other people's requests to join. Nothing outside what the user could do themselves is allowed.

• Partners can now read a user's address book through the API: the other people on their chains and the transactions they're on together. Each person's name, email, phone and company are only shown as far as that person has chosen to share them.

Improvements

• Stages that partners create or change through the API now get the same update reminders as stages edited in the app: a stage assigned to the user with a date for its next update reminds them at 9am that day, and the reminder is moved or cancelled if the stage changes or is deleted.

• Behind-the-scenes tidy-up of how PropChain talks to the database, so the same logic can be shared with the partner API. There is no change to how anything looks or works.

Fixes

• Invites and licences can now only be seen by the people they concern: the person who sent an invite, the person invited, the people on the property chain, and team admins for team invites. Invite codes are no longer visible to anyone in the app.
• Nobody can add themselves to someone else's property transaction, create licences, or reassign licences by going around the app. Inviting someone, declining or revoking an invite, redeeming a licence, putting a licence on a chain, and creating a QR code now all run as single checked steps.
• Inviting someone to a transaction now also stops you giving them more access than you have yourself, and an invite is created before its email is sent.
• A licence that already belongs to a team can no longer be redeemed by someone outside it, and a free licence assigned to one team member can no longer be used up by another.
• Who can change a transaction's people and details is now enforced everywhere, not just in the screens. You can only change someone else's role or permissions if you're allowed to edit parties, only up to your own level, and never someone with more access than you; the last person able to manage parties can't be removed. Editing sale, property and listing details needs the matching edit permission, and you now get a clear message if you don't have it.
• Transactions, their people, stages and history are only visible to the people involved (and their neighbours in the same chain), and the transaction history can no longer be forged.
• Accepting a request to join a transaction can no longer grant more access than the person accepting holds.
• Merging two chains now checks that you are involved in the shared property, and either moves everything across or nothing, so a chain can no longer be left half-merged.
• Starting a chain, linking transactions and adding a property to a chain now each happen as a single step, so a failure part-way no longer leaves a half-built chain behind. Previously anyone signed in could link any two transactions into any chain; that is no longer possible, and linking now needs permission to edit the chain on the transactions involved.
• Stages created through the API are checked: an owner has to be someone on the transaction, and stages can't be made to depend on each other in a loop.
• The address book now decides what each person has shared in the database itself, instead of sending everyone's details to the screen to hide, so contact details a person keeps private are never sent to anyone else.

Safer invites, chains, listing import and sign-in

1 October 2026

Improvements

• Importing a property from a Rightmove or OnTheMarket link is now stricter and more reliable: only genuine listing links are accepted, slow or oversized pages are given up on quickly, and automated abuse is blocked. If a listing can't be read, you're asked to fill in the details manually instead of seeing an error.
• Accepting an invite now makes sure it was sent to your email address and hasn't expired, and team invites are handled in the same single step as property invites. If you left a chain or team before, you can be re-invited and rejoin.

Fixes

• Accounts that have been deactivated can no longer sign in using an emailed one-time code. Previously only password sign-in blocked them; now both sign-in methods send them to the account recovery page.
• Removing a link from a chain, leaving a chain, and accepting a request to join are now all-or-nothing, so a failure part-way can no longer leave a chain in a half-changed state (for example an empty leftover chain, or a request accepted without the person being added).
• When the person who holds a chain's licence leaves, the licence now reliably passes to another member who has one; previously this could fail silently and leave the chain read-only.
• Creating a team, adding or removing members, changing roles, and assigning or taking back licences are now all-or-nothing, and always checked against who you are signed in as. This fixes removing a team member (which could remove you instead), two admins assigning the same licence at once, and a team being left without an admin if setup failed part-way.
• Team invites are now created before the invite email is sent, so the code in an email always works.
• Removing a link in the middle of a chain with several branches now only splits off the part that actually becomes disconnected.

Dev-only quick sign-in for testing preview and local deployments

29 September 2026

New

• Added a /dev-login page (PropChain, Marketing, and this documentation site) that lets you sign in with a plain email and password directly on that app, without going through the shared login app. It only works on preview and local environments, never in production, and is meant for developers checking signed-in pages on a preview link where the normal cross-app sign-in doesn't work.

Improvements

• Removed the unused preview-domain names from the sign-in redirect safety list, now that the dev-only quick sign-in above covers testing signed-in pages on previews.
• PropChain and Marketing's "Sign in" link now automatically sends you to the right place: the shared login app in production, or the new dev-only quick sign-in on preview and local environments.

Fixes

• Visiting a signed-in-only page in PropChain while signed out now sends you to the right place on preview and local environments too, instead of always trying the shared login app (which can't send you back on anything but the live site).
• Signing in with the dev-only quick sign-in on PropChain now takes you to the dashboard instead of a page that didn't exist.