How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Pricefinder Suburbs API

The suburbs API from Pricefinder — 15 operation(s) for suburbs.

Pricefinder Suburbs API is one of 19 APIs that Pricefinder publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include suburbs. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and authentication docs.

This API exposes 15 operations across 15 paths, and defines 64 schemas. It is described by OpenAPI 3.2.0, at version 1.13.1.

Requests are made against a single base URL, /v1.

15 operations 15 paths 64 schemas 15 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.13.1
Base URL
https://api.pricefinder.com.au/v1
Contact
Pricefinder
Resource Areas
1

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 15 GET. Each is listed below with its method, path, parameters, and response codes.

suburbs 15
GET
/suburbs/{suburbId}
Get the basic suburb information
suburb 1 param → 200
GET
/suburbs/{suburbId}/demographics
demographics 1 param → 200
GET
/suburbs/{suburbId}/flyover
Generate a 'flyover' of the suburb. A flyover is a summary of the recent sales and rental activity.
flyover 1 param → 200
GET
/suburbs/{suburbId}/flyover/pdf
A suburb flyover in a pdf report
flyoverReport 3 params → default
GET
/suburbs/{suburbId}/listings
listings 29 params → 200
GET
/suburbs/{suburbId}/properties
properties 19 params → 200
GET
/suburbs/{suburbId}/rentals
rentals 29 params → 200
GET
/suburbs/{suburbId}/sales
sales 28 params → 200
GET
/suburbs/{suburbId}/stats/peaksellingperiods/{propertyType}
peakSellingPeriods 6 params → 200
GET
/suburbs/{suburbId}/stats/pricesegmentation/sales/{propertyType}deprecated
priceSegmentSales 2 params → 200
GET
/suburbs/{suburbId}/stats/timeseries/pricesegmentation/sales/{propertyType}
priceSegmentSales2 6 params → 200
GET
/suburbs/{suburbId}/stats/timeseries/rentals/{propertyType}
timeSeriesRentals 5 params → 200
GET
/suburbs/{suburbId}/stats/timeseries/sales/{propertyType}
timeSeriesSales 8 params → 200
GET
/suburbs/{suburbId}/streets
streets 1 param → 200
GET
/suburbs/{suburbId}/summary
Rolling year sales statistics summary (median etc.) for the current year;
summary 1 param → 200

Schemas 64

The contract defines 64 schemas that model the data the API accepts and returns. The most detailed are ExtendedPropertyFeatures (40 properties), Sale (30 properties), Property (26 properties), Listing (26 properties). Each schema is shown below with its type and property counts.

SensitivePrice
object
4 properties
OwnershipSummary
object
3 properties
ListingStatus
object
3 properties
StatisticDouble
object
2 properties
StatisticsWrapper
object
1 property
Phone
object
6 properties
SuburbIdentifier
object
2 properties
Demographics
object
3 properties
SuburbSalesTimeseriesWrapper
object
2 properties
Sale
object
30 properties
PriceRangeSegment2
object
4 properties
SuburbSalesWrapper
object
3 properties
Agency
object
3 properties
Property
object
26 properties
Sales
object
3 properties
PropertyMapIdentifier
object
2 properties
SuburbRentalsTimeseriesWrapper
object
1 property
SuburbStatisticsSummary
object
7 properties
Message
object
2 properties
YearByMonthStatisticsLong
object
5 properties
SalesTimeSeriesValue
object
10 properties
SuburbStatistics
object
3 properties
MarketStatus
object
8 properties
Properties
object
3 properties
ImageIdentifier
object
2 properties
SensitiveDate
object
3 properties
CensusValue
object
2 properties
PriceRangeSegment
object
4 properties
StatisticLong
object
2 properties
ListingIdentifier
object
3 properties
Point
object
2 properties
CensusTopic
object
5 properties
Streets
object
3 properties
RentalsTimeSeries
object
6 properties
SearchExtra
object
3 properties
AgencyIdentifier
object
1 property
PriceRangeSegments2
object
6 properties
SalesTimeSeries
object
6 properties
TimeSeriesPeriod
object
4 properties
Address
object
15 properties
ListingListingHistory
object
5 properties
StreetIdentifier
object
1 property
Listings
object
3 properties
SensitiveChange
object
3 properties
StatisticsPropertyTypeWrapper
object
2 properties
PriceRangeSegments
object
5 properties
SuburbRentalsByBedroomStatisticsWrapper
object
1 property
SuburbSummary
object
5 properties
Listing
object
26 properties
SaleMetadata
object
2 properties
RentalTimeseriesValue
object
4 properties
SaleParticipantsSummary
object
2 properties
PropertyIdentifier
object
5 properties
SuburbFlyover
object
7 properties
SuburbRentalsByBedroomStatistics
object
5 properties
LandDetails
object
3 properties
PeakSellingPeriods
object
5 properties
RentalTimeSeriesValueGroup
object
5 properties
Suburb
object
7 properties
MarketStatusEventObject
object
2 properties
RentalsTimeSeries2
object
6 properties
Agent
object
3 properties
ExtendedPropertyFeatures
object
40 properties
SaleListingHistory
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pricefinder-suburbs-api-openapi.yml Raw ↑

Other APIs Pricefinder publishes across the network.

Pricefinder Appraisals API
Pricefinder Events API
Pricefinder Features API
Pricefinder Images API
Pricefinder Listings API
Pricefinder Names API
Pricefinder Oauth2 API
Pricefinder Postcodes API
Pricefinder Properties API
Pricefinder References API
Pricefinder Rentals API
Pricefinder Sales API
Where this information came from

This is an independent, third-party profile of Pricefinder Suburbs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.