curl --request POST \
  --url https://api.reprompt.io/v2/placematch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "place": {
    "name": "central park nyc"
  }
}'

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          -122.4195,
          37.775
        ]
      },
      "properties": {
        "name": "Blue Bottle Coffee",
        "address": "315 Linden St, San Francisco, CA 94102",
        "category": "coffee_shop",
        "phone": "+14158964500",
        "source": "byod",
        "is_match": true,
        "confidence": "VERY_HIGH",
        "reasoning": "High confidence match: very close location (12m away) with precise GPS coordinates"
      }
    }
  ],
  "metadata": {
    "total_results": 1,
    "sources_searched": [
      "byod"
    ],
    "search_radius_meters": 100
  }
}

Places

Placematch

Match a place against multiple geospatial data sources using AI-powered conflation algorithms.

Given information about a place (address, name, coordinates) we will find the right place. This is also called entity resolution.

Reprompt supports multiple backends for matching against:

Our own database of places we picked up from crawling the web
Foursquare OS Places - amazing open data project with 100M+ global POIs (Apache 2.0 license)
Overture Places - open map data from the Overture Maps Foundation with 64M+ places (CDLA Permissive 2.0)
Your own data - supply your own candidates to match against

Input Modes (all automatically geocoded if coordinates missing):

Name-only: Provide place.name (e.g., “central park nyc”) - automatically resolved and geocoded
Name + Address: Provide place.name + place.address - automatically geocoded to get coordinates
Precise matching: Provide place.name + place.address + coordinates (best accuracy, no geocoding needed)

Note: Coordinates-only searches (without name) are not yet supported but on the roadmap.

Supported Sources:

reprompt: Reprompt’s proprietary place database (default if not specified)
overture: Overture Maps Foundation open data
foursquare: Foursquare Places API data
byod: Match against your own data candidates

Key Use Cases:

Data cleaning: Clean messy/inconsistent place data against authoritative sources
Location matching: Match user coordinates against your proprietary POI database
Deduplication: Find duplicate places across different datasets

Matching considers:

Name similarity and normalization
Geographic proximity and distance
Category/type alignment
Address components
Geographic context when minimal info provided

Response includes:

Matched places as GeoJSON features
Confidence scores and match explanations
Detailed conflation metadata
Search operation metadata

POST

placematch

curl --request POST \
  --url https://api.reprompt.io/v2/placematch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "place": {
    "name": "central park nyc"
  },
  "match_sources": [
    "reprompt"
  ],
  "max_matches": 3
}'

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [
          -122.4195,
          37.775
        ]
      },
      "properties": {
        "name": "Blue Bottle Coffee",
        "address": "315 Linden St, San Francisco, CA 94102",
        "category": "coffee_shop",
        "phone": "+14158964500",
        "source": "byod",
        "is_match": true,
        "confidence": "VERY_HIGH",
        "reasoning": "High confidence match: very close location (12m away) with precise GPS coordinates"
      }
    }
  ],
  "metadata": {
    "total_results": 1,
    "sources_searched": [
      "byod"
    ],
    "search_radius_meters": 100
  }
}

Authorizations

Authorization

string

header

required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

apiKey

string | null

Body

application/json

Request model for placematch endpoint.

place

object

required

Place to match (name-only, coordinates-only, or name+address+coordinates for most precise matching)

Show child attributes

match_sources

enum<string>[] | null

Sources to search for matches. Defaults to reprompt if not specified.

Show child attributes

match_byod_candidates

PlaceInput · object[] | null

Your own data candidates for matching (max 50)

Show child attributes

max_matches

integer | null

default:3

Maximum matches per source

Required range: 1 <= x <= 10

radius

number | null

default:900

Search radius in meters

Required range: 50 <= x <= 5000

Response

Successfully matched places

Response model for placematch endpoint.

features

PlacematchFeature · object[]

required

Array of matched place features

Show child attributes

metadata

object

required

Operation metadata

Show child attributes

type

string

default:FeatureCollection

Allowed value: "FeatureCollection"

⌘I

List Attributes

Find Places

V2 API Reference

Authorizations

Headers

Body

Response