# Instagram Place Finder & Details (`data-slayer/instagram-place-finder`) Actor

Find Instagram places by name or coordinates, or enrich known place IDs with normalized location details.

- **URL**: https://apify.com/data-slayer/instagram-place-finder.md
- **Developed by:** [Data Slayer](https://apify.com/data-slayer) (community)
- **Categories:** Social media, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.75 / 1,000 completed places

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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.

```json
{
  "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:

```json
{
  "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.

# Actor input Schema

## `nameQueries` (type: `array`):

Names or keywords to search, one per line. Example: Taj Mahal or specialty coffee Mumbai.

## `coordinates` (type: `array`):

Latitude and longitude pairs for finding nearby Instagram places. Coverage is based on places returned for the coordinate, not a guaranteed radius.

## `placeIds` (type: `array`):

Known numeric Instagram place IDs to enrich directly.

## `maxPlacesPerLookup` (type: `integer`):

Maximum unique places saved for each name or coordinate lookup.

## `includeDetails` (type: `boolean`):

Fetch available category, address, postal code, and media count for discovered places.

## `maxDetailEnrichments` (type: `integer`):

Maximum discovered places enriched in this run. Remaining places are still saved with discovery fields.

## Actor input object example

```json
{
  "nameQueries": [
    "Taj Mahal"
  ],
  "maxPlacesPerLookup": 20,
  "includeDetails": true,
  "maxDetailEnrichments": 25
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "nameQueries": [
        "Taj Mahal"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("data-slayer/instagram-place-finder").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "nameQueries": ["Taj Mahal"] }

# Run the Actor and wait for it to finish
run = client.actor("data-slayer/instagram-place-finder").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "nameQueries": [
    "Taj Mahal"
  ]
}' |
apify call data-slayer/instagram-place-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,data-slayer/instagram-place-finder"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/w6PESKJOQUAv7iyj2/builds/czwjo0EQw7udLagu2/openapi.json