---
title: "Search for Sales Properties"
method: GET
path: "/sales/search"
tags: ["Sales"]
---

# Search for Sales Properties

`GET /sales/search`

This endpoint returns all active sales properties in your Street account. 

By default it will only return 'active' properties i.e. those with a status of `For Sale`, `For Sale and To Let`, `Under Offer` or `Sold STC`.

It will also return properties for **ALL** branches within your Street account, if you wish to limit to a specific branch you can use the `filter[branch]` query param and pass the `UUID` of the desired branch.

## Query parameters

- `filter[areas]` string
- `filter[bedrooms]` string
- `filter[min_bedrooms]` string
- `filter[branch]` string
- `filter[features]` string
- `filter[include_land]` string
- `filter[max_price]` string
- `filter[min_price]` string
- `filter[postcode]` string
- `filter[status]` string[]
- `filter[tags]` string
- `include` string[]
- `page[number]` number
- `page[size]` number
- `sort` 'price' | '-price' | 'created_at' | '-created_at'
- `filter[include_archived]` string

## Response `200`

The API endpoint responds with a JSON object containing a list of sales properties matching the specified criteria. Each property object within the response typically includes information such as property ID, address, description, price, number of bedrooms, and other relevant details. The response also includes pagination metadata, such as the total number of properties, the current page number, and the number of properties per page.

## Other responses

- `401` — The HTTP 401 Unauthorized response status code indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource.
- `403` — The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
- `406` — The HTTP 406 Not Acceptable client error response code indicates that the server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers, and that the server is unwilling to supply a default representation.
- `415` — The HTTP 415 Unsupported Media Type client error response code indicates that the server refuses to accept the request because the payload format is in an unsupported format.
- `422` — The HTTP 422 Unprocessable Entity response status code indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions.
- `500` — The HTTP 500 Internal Server Error server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

---

[API](https://skmtc.net/street/apis/property-feed.md) · [All operations](https://skmtc.net/street/apis/property-feed/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/street/property-feed/revisions/f152e142c053/schema)