HrFlow background
HR-Native Location Services & Geofencing

Geocoding API

The Geocoding API converts raw, messy text locations into structured GeoJSON (street addresses, cities, postal codes), exact Geopoints (lat/lng), and GeoFences (GPS boundaries). Powered by Hiring Superintelligence, it standardizes addresses across 108+ countries to power your maps, geospatial search, matching, and territory analytics.

183+ languages
108+ countries
400M+ POIs
GDPR & EU AI Act
99.99% uptime
output.json
{
  "parsing": {
    "model": "hrflow-file-v2.1",
    "confidence": 0.92,
  },
  "profile": {
    "name": "John Smith",
    "title": "Data Scientist",
    "skills": ["ML", "Python"]
  }
}

Trusted by Customers, Partners & the AI Ecosystem

ManpowerLogo
CritLogo
EuropeanUnionLogo
SanofiLogo
EnhanceCVLogo
TeamtailorLogo
API RESPONSE

Structured GeoJSON & Exact Geofences

Get clean, normalized location data you can store and index. Turn any location text into structured address components, exact coordinates, or polygons to power your maps, search engines, recommender systems, and business analytics tools.

Select Geocoding Type

Upload a raw location → returns GeoJSON.

Top Extracted Fields

Address

house number, street name, city, postcode, country

GeoPoint

latitude, longitude, Google Maps URL

GeoFence

Circle, Polygon, MultiPolygon

response.json
 1{
 2  "code": 200,
 3  "message": "Geocoding Text finished in 0.12 seconds.",
 4  "data": [
 5    {
 6      "fields": {
 7        "category": null,
 8        "city": "Neuilly-sur-Seine",
 9        "city_district": null,
10        "country": "FRA",
11        "country_region": null,
12        "entrance": null,
13        "house": null,
14        "house_number": "112",
15        "island": null,
16        "level": null,
17        "near": null,
18        "po_box": null,
19        "postcode": "92200",
20        "road": "Avenue Charles de Gaulle",
21        "staircase": null,
22        "state": "Île-de-France",
23        "state_district": "Hauts-de-Seine",
24        "suburb": null,
25        "text": "112 Avenue Charles de Gaulle, 92200, Neuilly-sur-Seine, Hauts-de-Seine, Île-de-France, FRA",
26        "unit": null,
27        "world_region": null
28      },
29      "gmaps": "https://www.google.com/maps/place/48.882640986183,2.268224974288",
30      "is_correct": true,
31      "lat": 48.882640986183,
32      "lng": 2.268224974288,
33      "text": "112 avenue charles de gale 92200 neuilly-sur-seine"
34    }
35  ]
36}
CUSTOMER STORIES

Don't take our word for it!

Teams use geocoding to stabilize location data for search and matching

One vendor instead of five

vs. Amazon
Before HrFlow.ai

We were juggling Amazon for geo, another vendor for parsing, and another for search. Integration time exploded and the product felt incoherent.

After HrFlow.ai

HrFlow.ai collapsed it into one HR-native stack: parsing + geocoding + searching + scoring. Integration time dropped, and the product is finally coherent.

Indonesia-ready geofencing

vs. Google
Before HrFlow.ai

Indonesia broke every location setup we tried—thousands of islands, overlapping areas, inconsistent city labels, and "nearby" searches that returned the wrong region.

After HrFlow.ai

HrFlow.ai generates accurate geofence polygons for cities and islands, stores them once, and runs "within area" search reliably across the archipelago.

Finally: real commute search

vs. Mapbox
Before HrFlow.ai

In recruitment, straight-line distance isn’t enough. "5 minutes from the office" has to mean real routes, not Euclidean distance. Our internal scripts couldn’t keep up.

After HrFlow.ai

HrFlow.ai lets us search using waypoints and travel-time logic, so recruiters can filter candidates by true proximity.

One vendor instead of five

vs. Amazon
Before HrFlow.ai

We were juggling Amazon for geo, another vendor for parsing, and another for search. Integration time exploded and the product felt incoherent.

After HrFlow.ai

HrFlow.ai collapsed it into one HR-native stack: parsing + geocoding + searching + scoring. Integration time dropped, and the product is finally coherent.

Indonesia-ready geofencing

vs. Google
Before HrFlow.ai

Indonesia broke every location setup we tried—thousands of islands, overlapping areas, inconsistent city labels, and "nearby" searches that returned the wrong region.

After HrFlow.ai

HrFlow.ai generates accurate geofence polygons for cities and islands, stores them once, and runs "within area" search reliably across the archipelago.

Finally: real commute search

vs. Mapbox
Before HrFlow.ai

In recruitment, straight-line distance isn’t enough. "5 minutes from the office" has to mean real routes, not Euclidean distance. Our internal scripts couldn’t keep up.

After HrFlow.ai

HrFlow.ai lets us search using waypoints and travel-time logic, so recruiters can filter candidates by true proximity.

One vendor instead of five

vs. Amazon
Before HrFlow.ai

We were juggling Amazon for geo, another vendor for parsing, and another for search. Integration time exploded and the product felt incoherent.

After HrFlow.ai

HrFlow.ai collapsed it into one HR-native stack: parsing + geocoding + searching + scoring. Integration time dropped, and the product is finally coherent.

Indonesia-ready geofencing

vs. Google
Before HrFlow.ai

Indonesia broke every location setup we tried—thousands of islands, overlapping areas, inconsistent city labels, and "nearby" searches that returned the wrong region.

After HrFlow.ai

HrFlow.ai generates accurate geofence polygons for cities and islands, stores them once, and runs "within area" search reliably across the archipelago.

Finally: real commute search

vs. Mapbox
Before HrFlow.ai

In recruitment, straight-line distance isn’t enough. "5 minutes from the office" has to mean real routes, not Euclidean distance. Our internal scripts couldn’t keep up.

After HrFlow.ai

HrFlow.ai lets us search using waypoints and travel-time logic, so recruiters can filter candidates by true proximity.

One vendor instead of five

vs. Amazon
Before HrFlow.ai

We were juggling Amazon for geo, another vendor for parsing, and another for search. Integration time exploded and the product felt incoherent.

After HrFlow.ai

HrFlow.ai collapsed it into one HR-native stack: parsing + geocoding + searching + scoring. Integration time dropped, and the product is finally coherent.

Indonesia-ready geofencing

vs. Google
Before HrFlow.ai

Indonesia broke every location setup we tried—thousands of islands, overlapping areas, inconsistent city labels, and "nearby" searches that returned the wrong region.

After HrFlow.ai

HrFlow.ai generates accurate geofence polygons for cities and islands, stores them once, and runs "within area" search reliably across the archipelago.

Finally: real commute search

vs. Mapbox
Before HrFlow.ai

In recruitment, straight-line distance isn’t enough. "5 minutes from the office" has to mean real routes, not Euclidean distance. Our internal scripts couldn’t keep up.

After HrFlow.ai

HrFlow.ai lets us search using waypoints and travel-time logic, so recruiters can filter candidates by true proximity.

Autocomplete eliminated dirty data

vs. Keywords
Before HrFlow.ai

Our recruiters type locations in many ways, and our filters were useless. Dirty data everywhere.

After HrFlow.ai

HrFlow.ai autocomplete & typeahead standardized address entry at the source—fewer errors, fewer duplicates, and much cleaner geo filters across jobs, offices, and profiles.

GeoJSON components for clean filters

vs. Regex
Before HrFlow.ai

We used to regex addresses into fields, and it never held up internationally.

After HrFlow.ai

HrFlow.ai returns structured address components (street, postcode, city, region, country), so our geo dashboards and filters became reliable overnight.

Territory planning for field recruiters

vs. Internal DB
Before HrFlow.ai

We assign recruiters by territory, but our ‘regions’ were just text. Routing and coverage gaps were pure guesswork.

After HrFlow.ai

HrFlow.ai turned locations into GeoPoints + geofences, so routing, coverage gaps, and territory balancing became data-driven instead of guesswork.

Autocomplete eliminated dirty data

vs. Keywords
Before HrFlow.ai

Our recruiters type locations in many ways, and our filters were useless. Dirty data everywhere.

After HrFlow.ai

HrFlow.ai autocomplete & typeahead standardized address entry at the source—fewer errors, fewer duplicates, and much cleaner geo filters across jobs, offices, and profiles.

GeoJSON components for clean filters

vs. Regex
Before HrFlow.ai

We used to regex addresses into fields, and it never held up internationally.

After HrFlow.ai

HrFlow.ai returns structured address components (street, postcode, city, region, country), so our geo dashboards and filters became reliable overnight.

Territory planning for field recruiters

vs. Internal DB
Before HrFlow.ai

We assign recruiters by territory, but our ‘regions’ were just text. Routing and coverage gaps were pure guesswork.

After HrFlow.ai

HrFlow.ai turned locations into GeoPoints + geofences, so routing, coverage gaps, and territory balancing became data-driven instead of guesswork.

Autocomplete eliminated dirty data

vs. Keywords
Before HrFlow.ai

Our recruiters type locations in many ways, and our filters were useless. Dirty data everywhere.

After HrFlow.ai

HrFlow.ai autocomplete & typeahead standardized address entry at the source—fewer errors, fewer duplicates, and much cleaner geo filters across jobs, offices, and profiles.

GeoJSON components for clean filters

vs. Regex
Before HrFlow.ai

We used to regex addresses into fields, and it never held up internationally.

After HrFlow.ai

HrFlow.ai returns structured address components (street, postcode, city, region, country), so our geo dashboards and filters became reliable overnight.

Territory planning for field recruiters

vs. Internal DB
Before HrFlow.ai

We assign recruiters by territory, but our ‘regions’ were just text. Routing and coverage gaps were pure guesswork.

After HrFlow.ai

HrFlow.ai turned locations into GeoPoints + geofences, so routing, coverage gaps, and territory balancing became data-driven instead of guesswork.

Autocomplete eliminated dirty data

vs. Keywords
Before HrFlow.ai

Our recruiters type locations in many ways, and our filters were useless. Dirty data everywhere.

After HrFlow.ai

HrFlow.ai autocomplete & typeahead standardized address entry at the source—fewer errors, fewer duplicates, and much cleaner geo filters across jobs, offices, and profiles.

GeoJSON components for clean filters

vs. Regex
Before HrFlow.ai

We used to regex addresses into fields, and it never held up internationally.

After HrFlow.ai

HrFlow.ai returns structured address components (street, postcode, city, region, country), so our geo dashboards and filters became reliable overnight.

Territory planning for field recruiters

vs. Internal DB
Before HrFlow.ai

We assign recruiters by territory, but our ‘regions’ were just text. Routing and coverage gaps were pure guesswork.

After HrFlow.ai

HrFlow.ai turned locations into GeoPoints + geofences, so routing, coverage gaps, and territory balancing became data-driven instead of guesswork.

🔗 INTEGRATIONS

Works with the tools you use

Integrate 200+ tools with the flip of a switch.

Integration 0
Integration 1
Integration 2
Integration 3
Integration 4
Integration 5
Integration 6
Integration 7
Integration 8
Integration 9
Integration 10
Integration 11
Integration 0
Integration 1
Integration 2
Integration 3
Integration 4
Integration 5
Integration 6
Integration 7
Integration 8
Integration 9
Integration 10
Integration 11
Integration 0
Integration 1
Integration 2
Integration 3
Integration 4
Integration 5
Integration 6
Integration 7
Integration 8
Integration 9
Integration 10
Integration 11
Integration 0
Integration 1
Integration 2
Integration 3
Integration 4
Integration 5
Integration 6
Integration 7
Integration 8
Integration 9
Integration 10
Integration 11
HrFlow.ai Data Studio

HrFlow.ai Data Studio

HR-native ETL with 200+ connectors plus Webhooks to ingest, normalize, and sync jobs & profiles across your stack, reliable pipelines with unified schemas.

Zapier ETL

Zapier ETL

No-code automation platform with 8,000+ app integrations to move data between tools using triggers + actions.

Make.com ETL

Make.com ETL

Visual automation platform to extract/transform/route data across 3,000+ apps (plus HTTP modules for any API).

Microsoft Flow ETL

Microsoft Flow ETL

Microsoft Power Automate, workflow automation with 1,000+ API connectors (and support for custom connectors).

Workato ETL

Workato ETL

Enterprise iPaaS/automation platform with 1,200+ pre-built connectors for orchestrating integrations and data workflows at scale.

Salesforce Flow Automation

Salesforce Flow Automation

Salesforce's low-code workflow automation tool; extended via AppExchange with 7,000+ apps to add integrations and capabilities.

🚀 KEY FEATURES

Global Geo Infrastructure for HR Apps

HrFlow.ai Geocoding turns messy location text into reliable geo data (GeoPoints, structured GeoJSON, and geofence polygons) powered by 400M+ addresses & POIs across 108+ countries. Built for global HR workflows with 183+ languages, typo-tolerant autocomplete.

Tutorial Video3:45

🔒 ENTERPRISE-READY

Trust & Security

Built for sensitive HR data, secure by default, enterprise-ready.

01

Encryption

TLS in transit + encryption at rest to protect documents and extracted data.

02

Retention control

Minimal storage by default, with configurable retention policies to match your compliance needs.

03

AI-Act / GDPR / DPA ready

AI-Act & GDPR-ready processing and Data Processing Agreement (DPA) are available on request.

04

Location / Region

Data processing and storage can be aligned with your required region (e.g., EU or US) depending on your deployment.

📊 FEATURE COMPARISON

HrFlow.ai Geocoding is the only HR-first Location Services API

Feature
HrFlow.ai Geocoding
HrFlow.ai Geocoding
Google Geocoding
Google Geocoding
Amazon Location Service
Amazon Location Service
HERE Geolocation
HERE Geolocation
Mapbox
Mapbox
Deployment & Trust
Headquarters
🇫🇷 France
🇺🇸 USA
🇺🇸 USA
🇳🇱 Netherlands
🇺🇸 USA
🇺🇸 USA & 🇪🇺 EU Servers
Built-in
Built-in
Built-in
Built-in
Built-in
GDPR / AI-Act
By design
By design
By design
By design
By design
HR Compliance (Safety & Guardrails)
Built-in
Built-in
Built-in
Built-in
Built-in
HR-Focused
Zero-config (HR)
HR Stack integrations (add-ons)
Resume, CV, Job parsers
Built-in (Parsing API)
Search Engine Add-on
Built-in (Searching API)
Recommender System Add-on
Built-in (Scoring API)
Jobboards / ATS / HCM / HRIS connectors
200+ HR connectors (Data Studio)
Candidate & Recruiter UI
Widgets (App Studio)
❓ COMMON QUESTIONS

Frequently Asked Questions

Everything you need to know about the Geocoding API

🧩 COMPLETE API SUITE

Go beyond the Geocoding API

Our APIs are designed to complement each other and unlock your data's full potential

Full Extraction API Suite

Transform HR documents into structured, enriched Talent & Workforce Data — powering every layer of Hiring Intelligence.

API Overview
94%82%71%58%

Ranking API Suite

Unlock Hiring Superintelligence at scale — with transparent, fair, and explainable ranking across every Talent signal.

API Overview

GET STARTED

Ready to transform your HR data?

Start parsing resumes and job postings in minutes with our powerful API.

HrFlow.ai is an API-first company and the leading AI-powered HR data automation platform.

The company helps +1000 customers (HR software vendors, Staffing agencies, large employers, and headhunting firms) to thrive in a high-volume and high-frequency labor market.

The platform provides a complete and fully integrated suite of HR data processing products based on the analysis of hundreds of millions of career paths worldwide -- such as Parsing API, Tagging API, Embedding API, Searching API, Scoring API, and Upskilling API. It also offers a catalog of +200 connectors to build custom scenarios that can automate any business logic.

GDPR Compliant badgeCapterra 4.8 rating badge