The Street Open API Explained: What Letting Agents Can Actually Build (With Real Examples)

The Street Open API is a free, RESTful API that lets any Street.co.uk user or supplier read and write agency data — properties, tenancies, applicants, maintenance, tasks and much more — using a bearer token generated inside your Street account. It follows the JSON:API standard, supports webhooks for real-time event notifications, and comes with a sandbox environment on request. In plain terms, it is the plumbing that lets other software work directly with your Street data instead of your team rekeying it.

Key takeaways

• Street's developer docs state the API is "open and free of charge, available to any user or supplier to use".
• It is RESTful and follows the JSON:API standard, with bearer-token authentication set up in Street under Settings > Account Administration > Applications.
• Rate limits are up to 600 GET calls per minute and up to 100 POST/PUT/PATCH/DELETE calls per minute, and can be raised by contacting Street's API team.
• Around 40 resource groups are exposed, from Properties and Tenancies to Enquiries, Maintenance Requests, Invoices and Tasks.
• Webhooks deliver real-time event notifications so connected systems stay in sync without polling.

What is the Street Open API in plain English?

An API (application programming interface) is a controlled doorway that lets one piece of software talk to another. The Street Open API is Street.co.uk's doorway: with a token an agency generates itself, an approved tool — or your own developer — can fetch records from Street and post updates back, securely and in a documented format.

Technically, it is a RESTful API with predictable resource-oriented URLs that accepts and returns JSON, and it follows the JSON:API standard — a widely used convention for structuring responses, which makes it easier for developers to work with. It is one of three APIs on Street's developer portal, alongside a Property Feed API for powering search and listings on agency websites, and the Spectre API.

For an agency owner, the significance is simple: you are not locked into whatever features ship in the CRM. Street's directory already lists 69+ off-the-shelf integrations built this way, and anything the directory does not cover, you can commission.

What data can you read and write with the Street API?

The API reference spans roughly 40 resource groups. The lettings-relevant ones include Properties, Tenancies, Tenants, Landlords, Applicants, Enquiries, Viewings, Valuations, Lettings Applications, Lettings Offers, Maintenance Requests, Maintenance Jobs, Inspections, Invoices, Documents, Notes, Tasks, Property Keys and Users. Sales-side resources (Sales, Sales Offers, Vendors and so on) sit alongside them.

It is not read-only. The documentation sets separate rate limits for POST, PUT, PATCH and DELETE requests — the operations that create, update and remove records — so systems can write into Street as well as read from it. Which operations each resource supports varies, so check the endpoint reference in the developer docs before designing around a specific write.

Two practical details for anyone scoping a build: results are paginated (there is a dedicated pagination guide), and rate limits — 600 GET calls and 100 write calls per minute — can be increased by contacting Street's API team.

Does the Street API support webhooks?

Yes. A webhook is a push notification for software: instead of your system repeatedly asking Street "anything new?", Street sends an event the moment something happens. Street describes its webhooks as "real-time event notifications so your systems stay synchronised without polling", and the developer documentation includes a dedicated webhooks section.

This is what makes reactive workflows possible — a tool that responds when a new enquiry, tenancy change or maintenance issue appears, rather than on an hourly sync. The exact event catalogue is listed in the developer docs, so confirm the specific events you need are covered before committing to a design.

What can a letting agency actually build with it?

Here are six things agencies build — or buy from suppliers who built them — on the Street Open API.

1. Auto-logging of portal and website enquiries. Capture enquiries from your website or other channels into Street's Enquiries and Applicants resources, so every lead lands in the CRM with no copy-and-paste.
2. Landlord report generators. Read Tenancies, Invoices, Maintenance Jobs and Inspections for a landlord's properties and assemble a branded monthly statement automatically.
3. Maintenance intake flows. A tenant-facing form or chatbot that creates Maintenance Requests in Street with the right property attached, then tracks the resulting Maintenance Jobs. We cover the workflow end to end in our guide to handling maintenance requests in Street.
4. Operations dashboards. Pull Tasks, Viewings, Lettings Offers and Tenancies into a wallboard or BI tool so branch managers see pipeline and workload in real time.
5. Email assistants. Match each incoming email to the right Street contact, property and tenancy, then write back notes, tasks and work orders. This is the pattern Lanten follows: it reads the matching Street records beside each Outlook email, drafts a reply, and only writes back to Street once a human approves. Any email tool you build or buy should keep that approval step.
6. Key and compliance tracking. Sync Property Keys, Documents and Inspections with whatever your office uses on the ground, so audits stop being an archaeology project.

Example use case	Street Open API capability it relies on
Auto-logging website enquiries	Enquiries and Applicants resources (write); webhooks for instant capture
Landlord monthly reports	Tenancies, Invoices, Maintenance Jobs, Inspections (read); pagination for large portfolios
Maintenance intake form	Maintenance Requests and Maintenance Jobs (write); Properties lookup (read)
Branch operations dashboard	Tasks, Viewings, Lettings Offers, Tenancies (read); GET rate limit of 600/min
Email assistant in Outlook	People, Properties, Tenancies (read); Notes, Tasks, Maintenance Jobs (write)
Key tracking and audits	Property Keys, Documents, Inspections resources

How do you get started with the Street Open API?

Access is self-serve for reading the docs, and tokens are generated in Street under Settings > Account Administration > Applications, then sent as an Authorization: Bearer header. For development work, Street advises against using production tokens and offers a sandbox account on its staging environment — email [email protected] to request one. Developer support runs through Street's API support portal.

If a supplier is building for you, ask five questions before signing:

• Which Street resources and webhooks does the product use, and does it write back or only read?
• Does it update the correct existing records, or create duplicates?
• What happens when rate limits are hit — does data queue or silently drop?
• Is there human approval before anything tenant- or landlord-facing goes out?
• Where is data processed and stored, and under what UK GDPR arrangements?

And before commissioning anything bespoke, check whether someone has already built it — our roundup of the best off-the-shelf Street.co.uk integrations covers the established options by category.

FAQs

Is the Street API free?

Yes. Street's developer documentation states the Open API is "open and free of charge, available to any user or supplier to use". You still pay for whatever software you build or buy on top of it, but Street does not charge for API access itself.

Does Street support webhooks?

Yes. Street offers webhooks described as real-time event notifications that keep connected systems synchronised without polling. Check the webhooks section of the developer docs for the current list of supported events.

Can the Street API write data or only read?

It can do both. The documentation defines rate limits for GET requests (up to 600 per minute) and separately for POST, PUT, PATCH and DELETE requests (up to 100 per minute), which are the operations used to create and update records. Support varies by resource, so confirm the specific endpoints in the API reference.

How do I get a Street API sandbox account?

Email [email protected] and request a token for Street's staging environment. Street recommends developing there rather than against your live production account, and its API support portal handles developer queries.

---

Want the benefits of the Street Open API without a development project? Lanten puts your Street data to work inside Outlook, with every action approved by you.