Whereis® is powered by its own API, known as the Enhanced Mapping Service (EMS).
It's EMS that enables you to embed interactive maps (and aerial images) in webpages and to perform other spatial and location-related functions, such as:
- geocoding, (getting a latitude/longitude for a street address)
- address validation (searching for an address to make sure it's real)
- routing (generating instructions for getting from one place to another).
- state, region, suburb and postcode detail services (return extra information about geocoded areas, such as boundary geometry)
There are two ways to access EMS, depending on your needs:
- a JavaScript Library which is mainly used for embedding interactive maps in webpages but which you can also use to access all the utility functions.
- an HTTP JSON API which the JavaScript Library uses behind the scenes and which you would typically use from a server-side application. The most obvious difference between the two is that the JavaScript Library gives you access to draggable interactive maps, whereas the JSON API provides static map images only.
New Users - Where do I start?
The Whereis® API is a subscriber service. If you are interested in getting access to the API, you will need to contact Sensis Data Solutions Customer Care to get a token and password.
Important information:
- Tell us how much traffic you estimate you'll use by filling in this template. This information will help us make sure that everyone gets fair use of the service.
- Undertake not to obscure our brand: so if you plan to do anything unusual with your user-interface, you must let us know.
Upgrading from Whereis API v1?
If you are upgrading to v2 from v1, your existing token and password will still work, but your code will require some modification. For users of the v1 SOAP API, this service has been completely replaced with an RESTful HTTP JSON API. You will need to rewrite your application to use the new endpoints. For users of the v1 JSON API, there are some minor changes to request and response data types. For users of the JavaScript Library, there are some interface changes that will require you to modify your code.
For details read Upgrading from Whereis API v1
Access URLs
You will usually work against our Production environment, even if you're doing development and staging. This is because the Production endpoint always points to the current stable release.
You only need to work against the Staging endpoint if:
- you've made an arrangement with us to access up-and-coming features
- you're doing performance testing, in which case email our Performance Tester via ems-support@ems.sensis.com.au to book a performance testing slot.
Environment | URL | Examples | Tutorials | JavaScript Reference | Status Page | Health Check |
|---|---|---|---|---|---|---|
Production | Examples | Tutorials | JavaScript Reference | |||
Staging | Examples | Tutorials | JavaScript Reference |
Site Map
- EMS JSON API
- EMS JavaScript API
- Glossary
- Appendices
- Appendix 1 - JavaScript Command Reference
- Appendix 2 - Examples and Tutorials
- Appendix 3 - Zoom Levels
- Appendix 4 - Street Suffixes
- Appendix 5 - Street Types
- Appendix 6 - v1 SOAP to v2 JSON Operations
- Appendix 7 - v1 SOAP to v2 JSON Data Types
- Appendix 8 - v1 JSON to v2 JSON Operations
- Appendix 9 - v1 JSON to v2 JSON Data Types
- Appendix 10 - POI categories
- Upgrading from WhereIs API v1
HTTP JSON API
- EMS JSON API - for developers and users of the JSON API
JavaScript Library
For developers and users of the JavaScript API:
Glossary
- Definitions of mapping-related and other terms we've used in the APIs
Appendix
