Foursquare’s legacy Places v3 API sunset on May 15, 2026. If your product used it for rich venue profiles, photos, tips, hours, ratings, or popularity, the closest path is still Foursquare’s current platform. Open Places API is not a drop-in replacement for that.

If your product used Foursquare for the narrower job of “find places near this coordinate and return JSON,” the migration can be much smaller.

What maps cleanly

Open Places API has one public endpoint:

GET https://api.openplacesapi.com/v1/places
Authorization: Bearer opa_live_...

For text search, send q, lat, lon, and optional radius_mi, mode, limit, min_confidence, and layer parameters.

curl -G "https://api.openplacesapi.com/v1/places" \
  --data-urlencode "q=coffee" \
  --data-urlencode "lat=40.7128" \
  --data-urlencode "lon=-74.0060" \
  --data-urlencode "radius_mi=25" \
  --data-urlencode "min_confidence=0.85" \
  -H "Authorization: Bearer $OPEN_PLACES_API_KEY"

For area lists, omit q and send category:

curl -G "https://api.openplacesapi.com/v1/places" \
  --data-urlencode "category=cafe" \
  --data-urlencode "lat=40.7128" \
  --data-urlencode "lon=-74.0060" \
  --data-urlencode "radius_mi=25" \
  --data-urlencode "limit=50" \
  --data-urlencode "offset=0" \
  -H "Authorization: Bearer $OPEN_PLACES_API_KEY"

Each page is one search against your monthly quota. meta.next_offset tells you when another page is available.

Field mapping

Foursquare-style need	Open Places API field
Stable place identifier	`place_id`
Name	`name`
Latitude / longitude	`lat`, `lon`
Distance	`distance_mi`
Category	`categories`
Address	`address`
Phone	`phone` when Overture has it
Website	`website` when Overture has it
Quality signal	`confidence` and request `min_confidence`
Status	`operating_status` when Overture has it

Open Places API does not return ratings, reviews, tips, photos, rich hours, popularity, or Foursquare venue intelligence.

The open-data angle

Foursquare’s open FSQ OS Places dataset is partly inside Overture Places. Overture added Foursquare-sourced records in its September 2025 release, and Overture’s current Places documentation lists Foursquare as one of the source contributors.

That matters for migration language: the open half of Foursquare is already part of the base data we serve, alongside other Overture contributors. The hosted API value is not exclusive ownership of that data; it is the serving stack, quota gate, confidence exposure, category browse, and account-owned layer merge.

Migration checklist

Identify which Foursquare fields your product actually uses.
If the product depends on ratings, photos, tips, hours, popularity, or Foursquare-specific venue intelligence, stay with Foursquare or use it alongside Open Places API.
If the product only needs backend nearby search or area lists, prototype GET /v1/places.
Add min_confidence=0.85 for production list-building, then lower or omit it only after sampling.
Store returned place_id values and any cached facts you need. Open Places API results are built from permissive open-data licenses.
Put curated corrections, suppressions, or private records in account-owned layers instead of forking the base data.

For a broader provider comparison, read Open Places API vs Foursquare Places API.