# Geocoding — Address to Coordinates & Reverse (`bgfc97/geocoding`) Actor

Convert addresses or place names to latitude/longitude with a structured address (forward), or coordinates back to an address (reverse). Powered by OpenStreetMap Nominatim. No API key.

- **URL**: https://apify.com/bgfc97/geocoding.md
- **Developed by:** [Bruno](https://apify.com/bgfc97) (community)
- **Categories:** Developer tools, Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 23 total users, 5 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 address resolveds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Geocoding — Address ⇄ Coordinates

Convert **addresses to coordinates** (forward) or **coordinates to addresses** (reverse), with a clean structured address for each. Powered by OpenStreetMap Nominatim — no API key.

### Forward (address → coordinates)

```json
{
  "mode": "forward",
  "queries": ["Eiffel Tower, Paris", "1600 Amphitheatre Parkway, Mountain View, CA"],
  "language": "en"
}
```

Returns `latitude`, `longitude`, `display_name`, structured `address` (road, city, state, postcode, country), `type`, `importance`, `boundingbox`.

### Reverse (coordinates → address)

```json
{
  "mode": "reverse",
  "coordinates": [{ "lat": 48.8584, "lon": 2.2945 }]
}
```

Returns `display_name` and the structured `address` for the point.

### Output example

```json
{
  "query": "Eiffel Tower, Paris",
  "display_name": "Eiffel Tower, Avenue Gustave Eiffel, Paris, France",
  "latitude": 48.8584,
  "longitude": 2.2945,
  "type": "attraction",
  "address": { "city": "Paris", "postcode": "75007", "country": "France", "country_code": "fr" }
}
```

### Use cases

Enrich CRM/lead addresses, map plotting, delivery/logistics, store locators, data cleaning, analytics.

Pay per address resolved. No key. (Respects the Nominatim usage policy: 1 request/second.)

### ⭐ Enjoying this Actor?

If it saved you time, a quick **rating/review** means a lot — it helps other people find it and keeps it actively maintained. Need an extra field or hit a snag? Open a ticket on the **Issues** tab and I'll take a look.

# Actor input Schema

## `mode` (type: `string`):

forward = address/place -> coordinates. reverse = coordinates -> address.

## `queries` (type: `array`):

Addresses or place names to geocode. Used when mode = forward.

## `coordinates` (type: `array`):

List of {lat, lon} objects to reverse-geocode. Used when mode = reverse.

## `language` (type: `string`):

Preferred language for results (en, es, pt-BR, fr, de, it, ja).

## Actor input object example

```json
{
  "mode": "forward",
  "queries": [
    "Eiffel Tower, Paris",
    "1600 Amphitheatre Parkway, Mountain View, CA"
  ],
  "coordinates": [
    {
      "lat": 48.8584,
      "lon": 2.2945
    }
  ],
  "language": "en"
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "Eiffel Tower, Paris",
        "1600 Amphitheatre Parkway, Mountain View, CA"
    ],
    "coordinates": [
        {
            "lat": 48.8584,
            "lon": 2.2945
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("bgfc97/geocoding").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "queries": [
        "Eiffel Tower, Paris",
        "1600 Amphitheatre Parkway, Mountain View, CA",
    ],
    "coordinates": [{
            "lat": 48.8584,
            "lon": 2.2945,
        }],
}

# Run the Actor and wait for it to finish
run = client.actor("bgfc97/geocoding").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "Eiffel Tower, Paris",
    "1600 Amphitheatre Parkway, Mountain View, CA"
  ],
  "coordinates": [
    {
      "lat": 48.8584,
      "lon": 2.2945
    }
  ]
}' |
apify call bgfc97/geocoding --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bgfc97/geocoding"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/K16bvi75mABgpE66r/builds/S9KsX6AfYRY0bOSmH/openapi.json