Instagram Place Finder & Details

Find Instagram places from names or coordinates, or enrich place IDs you already have. Each saved row has a stable place ID, canonical Instagram place URL, normalized location fields, and the lookup that produced it.

Watch the demo

YouTube video coming soon.

What this Actor does

• Search one or many place names and keywords.
• Find places returned around latitude and longitude pairs.
• Look up known numeric place IDs directly.
• Optionally enrich discovered places with available category, address, postal code, coordinates, and media count.
• Deduplicate the same place across multiple inputs.

This Actor finds places and place metadata. It does not download posts from those places. Use the place IDs with a location-post workflow when you need content.

Input

Use any combination of nameQueries, coordinates, and placeIds. At least one lookup is required, with at most 100 total lookups per run.

{
  "nameQueries": ["Taj Mahal", "specialty coffee Mumbai"],
  "coordinates": [{"latitude": 27.1751, "longitude": 78.0421}],
  "placeIds": ["234712543"],
  "maxPlacesPerLookup": 20,
  "includeDetails": true,
  "maxDetailEnrichments": 25
}

Coordinate search returns the places available for that point. It does not promise an exhaustive radius or fixed distance boundary. Detail fields are nullable because some places publish less information than others.

Output

Each dataset row is one unique place:

{
  "placeId": "234712543",
  "name": "The Taj Mahal Palace, Mumbai",
  "shortName": "The Taj Mahal Palace",
  "category": "Hotel",
  "address": "The Taj Mahal Palace, Mumbai, Apollo Bunder, Colaba",
  "city": null,
  "postalCode": "400001",
  "latitude": 18.92219416,
  "longitude": 72.83339439,
  "mediaCount": 372040,
  "placeUrl": "https://www.instagram.com/explore/locations/234712543/",
  "sourceMode": "name",
  "sourceQuery": "Taj Mahal",
  "sourceLatitude": null,
  "sourceLongitude": null,
  "detailsIncluded": true
}

The run summary is stored under the OUTPUT key. It distinguishes completed places, empty lookups, failed lookups, duplicates, detail requests, and plan, failure, or charge limits. Empty and failed lookups do not produce billable place rows.

Billing and limits

Billing uses one processed-lookup event after each lookup returns a valid response, including a valid response with no matching place. Failed, rejected, and skipped lookups are not charged. One completed-place event applies to each unique place record successfully saved, and a small start charge applies once per run. Detail enrichment is bounded by maxDetailEnrichments so you can control extra work.

Free-plan runs process up to two lookups, save up to ten places per lookup, and enrich up to five discovered places. Paid-plan runs use the limits in the input form. The run summary reports any skipped lookups.

Runs stop after three consecutive data failures so repeated unavailable lookups cannot consume an open-ended request budget.

Common uses

• Resolve venue names into stable Instagram place IDs.
• Build a deduplicated place list around known coordinates.
• Enrich place IDs before a local content or monitoring workflow.
• Normalize place exports for spreadsheets, databases, Make, Zapier, or n8n.

Data notes

Place names, categories, addresses, coordinates, and counts can change. Missing fields remain null; the Actor does not guess coordinates, addresses, categories, or business contacts. Verify important location details before using them for operational decisions.