Geocoding

  1. Home
  2. API Library
  3. Geocoding
From street addresses to geographical coordinates (and vice versa) in just a second

The Geocoding Service is available for 196 countries, with high-precision mapping

All the knowledge you need

Here you can find some advice to consider to approach this API. If you prefer, we provide code samples, OAS3 documentation, the ability to try the API live via the Swagger UI or import the entire collection into Postman. We also offer a Sandbox environment where you can experiment with all kinds of requests completely free of charge.

Useful tips to start with Geocoding

Get the token in the appropriate section before you start.

Use the the online tool or generate it via API. Set the expire date, a usefull name and now add a bunch of scopes to limit the possible actions your token can do.
Read more on oauth API Manage my tokens

Start Geocoding!

Choose if you want to start from an address and convert it to coordinates or the reverse.
API docs by Redocly

Geocoding Api (1.0.0)

URL: https://openapi.it/en/support License: Apache 2.0 Terms of Service

Geocoding Api Documentation

First time here? Generate a new access token

geocode

Retrieve informations about a place supplying address

Authorizations:
bearerAuth
Request Body schema: application/json

To improve success of results, please specify an address conforming to the following format: [street], [city] [postal code] [country]

address
required
string

Responses

Response Schema: application/json
success
string
object

Request samples

Content type
application/json
{
  • "address": "Via Cristoforo Colombo, Roma RM"
}

Response samples

Content type
application/json
{
  • "success": "true",
  • "elements": {
    }
}

reverse

Get place information from ID or latitude/longitude

Authorizations:
bearerAuth
Request Body schema: application/json

Get place information from ID or latitude/longitude:

  • To obtain infos via ID make sure to pass the following format: 
    {"type": "id", "id": "<id>"}
  • To obtain infos via lat/long, make sure to provide the following format: 
    {"type": "coordinates", "lat": "<lat>", "long": "<long>"}

id
string
type
required
string
lat
number <float>
long
number <float>

Responses

Response Schema: application/json
success
string
object

Request samples

Content type
application/json
{
  • "id": "v442c6653ee93a5733e8a9ea2f842cd5c250d2b6ab",
  • "type": "id | coordinates",
  • "lat": 41.289294,
  • "long": 13.2349029
}

Response samples

Content type
application/json
{
  • "success": "true",
  • "elements": {
    }
}
Web Service Revision: 2.0.0