Getting Started

Your journey with Outra begins here. This page covers the base URL, authentication, downloadable specifications and testing guidance so you can get live quickly.

Base URL

All endpoints are accessible via the base URL below. API versioning is applied at the root level to ensure backward compatibility as the platform evolves.

bash
https://property-api.k8s.outra.co.uk/api/v2

Authentication

Every request must include an Authorization header carrying your API key with the Api-Key scheme, and an accept header of application/json.

bash
curl 'https://property-api.k8s.outra.co.uk/api/v2/property-lookup-detailed?uprn=100023336956' \
  -H 'accept: application/json' \
  -H 'Authorization: Api-Key {api_key}'

Keep credentials secret

Treat your API key like a password. Never embed it in client-side code or commit it to source control. If you do not yet have credentials, contact your Outra account team.

API design principles

The Outra API follows RESTful design standards: predictable resource-based endpoints, consistent request and response structures, standard HTTP methods and clear status codes. This lets you integrate quickly and confidently across languages and frameworks while consuming data in a uniform, activation-ready format.

Responses use one of a few consistent shapes depending on the endpoint:

  • Field-group endpoints (for example /property/address, /property/valuation) return a flat JSON object of UPPERCASE-keyed fields. Modelled fields often carry FIELD$CONFIDENCE and FIELD$MODELLED companion keys.
  • List endpoints (/market-events/sales-listings, /market-events/rental-listings, and the paginated /property-lookup) return a paginated object, while /market-events/property-history and /address-lookup/postcode return a bare JSON array.
  • Errors return an ErrorResponse{ "detail": "…" }. See Errors & Status Codes.
json
{
  "data": [ ],
  "page": 1,
  "page_size": 100,
  "total_items": 0,
  "total_pages": 0
}

Specifications

PropertyAPI is built for enterprise-grade interoperability and provides downloadable specifications to support rapid integration, testing and internal documentation. These specifications can be imported directly into tools such as Postman, Swagger or any OpenAPI-compatible client — letting teams explore endpoints, validate responses and accelerate development workflows.

Testing & development

Before deploying to production, we recommend testing your requests using a third-party client. At Outra we use Postman for both web-based and desktop testing, which supports:

  • Authentication via API keys
  • Inspection of request and response payloads
  • Validation of pagination and filtering behaviour
  • Verification of error handling

For more information, visit postman.com.

Endpoint index

MethodEndpointPurpose
GET/property-lookupSearch by filter or free-text address
GET/property-lookup-detailedFull enriched record by UPRN
GET/address-lookup/postcodeAll properties for a UK postcode
GET/property/addressAddress & geospatial field group
GET/property/attributesStructural & internal attributes
GET/property/valuationValues, rebuild costs & confidence
GET/property/energyEnergy efficiency & consumption
GET/property/planningPlanning history & new-build signals
GET/property/constructionBuilding fabric & construction
GET/property/marketSale, rental & listing activity
GET/property/demographicsHousehold & occupant insight
GET/market-events/property-historyMarket event history by UPRN
GET/market-events/sales-listingsActive sales listings by location
GET/market-events/rental-listingsActive rental listings by location

Response envelope & errors

All responses follow the same envelope. For the full list of HTTP status codes and the error object structure, see Errors & Status Codes.