Overview of Urbi search APIs

Use Urbi search APIs to accomplish tasks related to finding objects on the map or collecting information about objects from the Urbi directory.

To determine object coordinates by its address or vice versa, use Geocoder API. Send requests to this API in scenarios when you need to determine an object address by clicking a map. Or the other way round: to show a known address on the map.

You can collect information about an object of interest or select objects by any criteria using Places API. Objects include companies, buildings, transport stops, sights, parking, intersections, and more.

Places API provides access to the full object directory that Urbi collects and uses in its own solutions. Send requests to this API when you need to create a set of objects by specific criteria and handle information on them.

You can implement the same mechanism of searching and displaying objects on the map as in Urbi:

If you want to implement a suggester that will complete user input in a search field, Suggest API is the right tool. Use it in web interfaces and mobile screens to help users select a proper address or an object on the city map faster.

For example, in the Urbi interface, the suggester works as follows:

When you need to determine which category an object belongs to, use Categories API. For example, you can learn which type of attractions are available in Dubai or what the type of the "H20" facility is: a restaurant, a cafe, or a cafeteria.

To get information about a region on the map, use Regions API. Requests to this API can help you determine which region a point on the map belongs to, get a list of settlements in the region, and also get the region ID to make other search requests more specific.

You can also display objects as markers on the map using Markers API.

For detailed examples of requests and parameter references, see the documentation of each search API.