The Property Railway Station API is a means to access the location of Australian railway stations. For most users, this information isn't necessary nor relevant, but many have technical skills that permits them to integrate various types of data with their existing applications. The API itself is used extensively by the Yabber property modules.
Property Module: Yabber's Property Module is extensive. The module makes property listing, analytical, and other data available to you, your child users, and partners. A large number of APIs may be used to access data for other applications. Review an introduction to the Property Module here. A commonly referenced FAQ details how to include a Property Listing Widget on your website, and another details how to assign a property to an existing widget location.
Property API Key: The Property API Key is different to your standard 'Personal' API Key and must be accessed through the Property Module 
(and then saved on your website ). The Property Module is a completely standalone module that integrates directly with Yabber. Basic API Documentation introducing the Property API may be found here.If you would like to access the API programmatically, you may reference a basic PHP function here.
The primary purpose of the API is to make distance information available to property widgets (such as distances to nearest stations etc.) and to provide general information on user websites via a search engine.
Property API Endpoint
The Endpoint for all requests to the Property API is structured as follows:
api.beliefmedia.com/property/{category}?/{action}.json?apikey={apikey}
The preferred method of authentication of your API Key is in the Authorisation Header (Authorization: Bearer {token}) as support for the URL parameter will soon be deprecated. Requests to child datasets will always include a {category} while the primary (listing) property endpoint is accessed directly. More information on the Property API is available here.
Introduction
The Railway Station API is a very simple RESTful service that provides a facility to query Australian rail stations. Queries to the Rail API are made to property/rail/{action}.json with the various 'actions' detailed in this FAQ. Each action and typical responses will be introduced in turn.
Data is updated on the first Monday of each week.
State
The state action returns all stations within a particular state. The purpose is to provide a package that you can query individually and cache locally. A request to rail/state.json?state=nsw unfolds as follows. If no state is provided nsw will be used.
Results are indexed on the query key (valid for the Property listing API).
Nearest and Radius
The nearest and radius endpoints are virtually identical and will return stations within a defined radius of a specific geographical point. The latitude, longitude and radius are required. If the former two are not provided no results will be returned.
Results are indexed on the query key (valid for the Property listing API).
Browse and Search
The browse and search endpoints are virtually identical with the exception that the search endpoint is used if filtering URL attributes are provided. The browse endpoint requires the page, limit, orderby, and order attributes (else default values are used). The search parameters are simply name and state. Since both results are similar, a basic (paginated) response for a search of 'burwood (with just two results)' is shown. Had we included '&nsw=nsw' only a single result would be returned.
The search feature is usually used for partial name matches.
Conclusion
Property widgets have the option of showing a small rail icon with a distance to the nearest rail station, and it's this function that is the primary purpose of this API. That said, we do include a rail search engine on your website simply because we can.
Related Property API FAQs
Article relating to the Property API.
The Property Streets API is a means to access registered street and address data from Yabber. For most users, this information isn't necessary nor relevant, but many have technical skills that permits them to integrate various types of data with their existing applications. Other Property FAQs show how to assign property widgets and video to… [ Learn More ]
The Property Emergency Services API is a means to access location information for Australian police stations, ambulance stations, fire stations, and SES facilities. For most users, this API information isn't necessary nor relevant, but many have technical skills that permits them to integrate various types of data with their existing applications. The API itself is… [ Learn More ]
The Property Railway Station API is a means to access the location of Australian railway stations. For most users, this information isn't necessary nor relevant, but many have technical skills that permits them to integrate various types of data with their existing applications. The API itself is used extensively by the Yabber property modules.
Related Property FAQs
Article relating to the Yabber and Website Property modules.
One of the marketing magnets any Property or Finance operation will use to engage organic traffic and convert warmer traffic in higher numbers is the inclusion of a Property Report form that will result in a report provided to the user. This FAQ will introduce the Property Report and how it is applied on pages… [ Learn More ]
This FAQ details the methods necessary to create a parent Property API Key. While the Property modules are intrinsically connected with all our modules, it operates autonomously via a standalone API-centric system that connects with multiple external applications. In order to use the Property module, you must first be assigned to the module (which is… [ Learn More ]
In a previous FAQ we looked at how to include an address validation field into a form on your website. This FAQ will introduce the same style of field that will automatically direct the user to the single page associated with each registered address in Australia. This feature is part of the broader Property… [ Learn More ]
The Property Property Streets API, and the Validation Endpoint in particular, is a means to access registered street and registered address location from Yabber via a form input field. The Validation (or Autocomplete) endpoints are useful for searching property on user keystrokes. The validation may be used to ensure pinpoint accuracy is assured by way… [ Learn More ]
SMS Subscription forms may be used in any number of ways, but the primary purpose is to support text message alerts for various types of property opportunities. When the form was first introduced, the form was part of our supporting partner modules, but more and more brokers are becoming affiliate directly with property groups, and… [ Learn More ]
