Geocode.xyz Python API Docs | dltHub
Build a Geocode.xyz-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Geocode.xyz provides worldwide forward and reverse geocoding, batch geocoding, and geoparsing services. It converts addresses to coordinates and coordinates to addresses. The API requires an API key for access. The REST API base URL is https://geocode.xyz and All requests may use an API key passed as a query parameter; unauthenticated requests are allowed but throttled..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Geocode.xyz data in under 10 minutes.
What data can I load from Geocode.xyz?
Here are some of the endpoints you can load from Geocode.xyz:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| forward_geocode | /?locate={location}&json=1 | GET | Forward geocoding (address → coordinates) | |
| reverse_geocode | /?locate={lat},{lon}&json=1 | GET | Reverse geocoding (coordinates → address) | |
| geoparse | /?scantext={text}&json=1 | GET | Geoparsing (extract locations from free text) | |
| autocomplete | /?streetname={street}®ion={region}&json=1 | GET | Autocomplete for street names and postcodes | |
| autocomplete_city | /?cityname={city}®ion={region}&json=1 | GET | City‑level autocomplete | |
| batch_geocode | /batch (web interface) or CSV API via https://geocode.xyz?row={row}&json=1 | POST/GET | Batch geocoding (multiple locations) |
How do I authenticate with the Geocode.xyz API?
Authentication is performed with an API key passed as the auth query parameter in requests (e.g. &auth=YOUR_KEY). No additional headers are required.
1. Get your credentials
- Visit https://geocode.xyz/new_account or https://geocode.xyz and click register/new account.
- Complete registration and verify your email address.
- In your account/dashboard copy the provided authentication code (auth token).
- Use the token in requests via the auth query parameter.
2. Add them to .dlt/secrets.toml
[sources.geocode_xyz_source] auth = "your_api_key_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Geocode.xyz API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python geocode_xyz_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline geocode_xyz_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset geocode_xyz_data The duckdb destination used duckdb:/geocode_xyz.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline geocode_xyz_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads forward_geocode and reverse_geocode from the Geocode.xyz API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def geocode_xyz_source(auth=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://geocode.xyz", "auth": { "type": "api_key", "auth": auth, }, }, "resources": [ {"name": "forward_geocode", "endpoint": {"path": "?locate={location}&json=1"}}, {"name": "reverse_geocode", "endpoint": {"path": "?locate={lat},{lon}&json=1"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="geocode_xyz_pipeline", destination="duckdb", dataset_name="geocode_xyz_data", ) load_info = pipeline.run(geocode_xyz_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("geocode_xyz_pipeline").dataset() sessions_df = data.forward_geocode.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM geocode_xyz_data.forward_geocode LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("geocode_xyz_pipeline").dataset() data.forward_geocode.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Geocode.xyz data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Geocode.xyz?
Request dlt skills, commands, AGENT.md files, and AI-native context.