LISTINGS
No longer observed
Records archived or removed from observation. They may be sold, relisted or temporarily unavailable; withdrawal is not inferred.
/api/v1/properties/no-longer-observed1 credit / callParameters
| Parameter | Type | Description |
|---|---|---|
q | string | Search public address, suburb and agency fields only. Maximum 100 characters. |
state | string | Australian state or territory code.ACT, NSW, NT, QLD, SA, TAS, VIC, WA |
postcode | string | Exact four-digit postcode. |
property_type | string | Normalised public property type.house, apartment, unit, townhouse, villa, land, rural, commercial, other |
bedrooms | integer | Minimum bedrooms, 0–20. |
agency_id | integer | Agency identifier from the agency endpoint. |
updated_since | string | UTC ISO 8601 timestamp; at most 90 days ago. |
page | integer | Page number, 1–20. Deep exports are unavailable. |
per_page | integer | Records per page, 1–50. |
MAKE IT YOUR OWN
Build a request
Edit the parameters to generate a ready-to-use code example. No request runs until you select Send request. Python uses the requests package; PHP requires cURL; JavaScript examples run on your backend with Node.js 18 or later.
Example response
Illustrative structure, not a live property record. Fields may be null when the source has not supplied a value.
{
"data": [
{
"id": "123456",
"address": {
"formatted": "12 Example Street, Brisbane QLD 4000",
"suburb": "BRISBANE",
"state": "QLD",
"postcode": "4000"
},
"property_type": "house",
"status": "active",
"marketing_price": "Offers over $900,000",
"bedrooms": 3,
"bathrooms": 2,
"car_spaces": 1,
"agency": {
"id": "12",
"name": "Example Agency"
},
"first_observed_at": "2026-11-01T02:30:00Z",
"last_observed_at": "2026-11-07T01:45:00Z",
"source_updated_at": "2026-11-06T23:00:00Z",
"indexed_at": "2026-11-07T02:00:00Z"
}
],
"meta": {
"example": true,
"credit_cost": 1
}
}Also available through MCP
Use the listingdata_inactive tool with the same documented inputs. Calls share your REST API credit balance and rate limits. Connect your MCP client →
Errors and retrying
| Status | Meaning | Recommended handling |
|---|---|---|
400 / 422 | Invalid or unsupported parameters. | Correct the input using the error response. |
401 / 403 | Invalid key or ineligible account. | Check key status and account verification. |
404 | The requested record is not available. | Check the ID; do not infer a property’s status. |
402 | Monthly credit allowance exhausted. | Wait for the next UTC calendar month. |
429 | Minimum interval or daily request allowance exceeded. | Honour Retry-After and reset details. |
503 | A required data service is unavailable. | Back off and retry later. Service-side charges are refunded. |
Property descriptions, internal search price bands and agent contact email or telephone numbers are never included. Source status and timestamps describe observations, not a guarantee of current availability. Future-dated source times are withheld. A record’s indexed_at is its last public index write; use the coverage endpoint for the last completed refresh cycle. Read the field policy.