Introduction

Loop is the platform UK estate agents run their business on — sales, lettings,
properties, applicants, viewings, offers, and tenancies, etc...

The Loop API gives you direct access to that data over a conventional REST interface, so you can power
your agency's website, feed your own tools and reporting, or integrate Loop with
your business. Requests and responses are JSON, over HTTPS, at
https://api.loop.software/v2.

Things you should know

  • Sales and lettings are separate namespaces. Resources that genuinely
    differ between the two live under /v2/sales/ and /v2/lettings/ — a sales
    property carries asking price and tenure, a lettings property carries rent
    and furnishing. Shared resources like documents and notes sit at the top level. If
    you're unsure where something lives, the API reference sidebar
    mirrors this structure.
  • Your API key is scoped to a team or an organisation. Every response contains that
    team's or organisations data and nothing else. See Authentication.
  • Keys are issued by Loop support. Email
    [email protected] with the organisation
    and office you're building for, and you'll receive your key through a secure
    one-time link. It's shown exactly once, so store it safely when you open it.
  • Keys belong on your server, not in the browser. Anyone holding your key
    can read your team's data, so proxy API calls through your own backend
    rather than calling the API from client-side JavaScript.
  • State changes are explicit actions. Transitions like withdrawing a
    property or accepting an offer are POST actions on the resource
    (POST /v2/sales/properties/{id}/withdraw), not status-field updates — each
    one is documented and validated in its own right.
  • The API grows without breaking. New fields and endpoints can appear at
    any time, so build your integration to ignore what it doesn't recognize.
    Breaking changes only ever arrive in a new API version.
  • v2 is not a drop-in replacement for v1. URLs, resource shapes, and key
    formats have all changed. v1 keeps working while you migrate — if you're
    planning that move, contact support and we'll
    help you map your usage across.


Did this page help you?