Instagram Location Posts & Local Creator Finder

Find Instagram places by name, URL, numeric ID, or GPS coordinates, then export their public geo-tagged posts without Instagram cookies or login credentials.

The Actor resolves ambiguous place searches, paginates automatically, applies filters before saving results, removes duplicates, and returns clean rows ready for Excel, Google Sheets, databases, maps, CRM enrichment, and AI workflows.

What you can do

• Monitor posts from stores, hotels, restaurants, venues, events, landmarks, and neighborhoods.
• Discover creators who publish at specific places.
• Compare content and engagement across multiple locations.
• Track user-generated content around a business or campaign.
• Filter by date, media type, likes, comments, plays, and verified creators.
• Run scheduled monitoring without downloading the same post twice inside a run.

Input

Use names, IDs, and URLs together:

{
  "locations": [
    "Mall del Sol Guayaquil",
    "51492242",
    "https://www.instagram.com/explore/locations/213131048/berlin-germany/"
  ],
  "coordinates": ["-2.1552,-79.8916"],
  "resultsPerLocation": 100,
  "matchStrategy": "best",
  "maximumLocationsPerQuery": 1,
  "maximumPagesPerLocation": 10,
  "onlyPostsNewerThan": "2026-07-01",
  "minimumLikes": 0,
  "minimumComments": 0,
  "minimumPlays": 0,
  "includeImages": true,
  "includeReels": true,
  "includeCarousels": true,
  "verifiedCreatorsOnly": false,
  "includeLocationInfo": true,
  "maxConcurrency": 3
}

Matching strategies

• best: selects the strongest name, city, and address match.
• exact: processes only exact place-name matches.
• all: processes up to maximumLocationsPerQuery candidates.

IDs and Instagram location URLs skip search and go directly to extraction.

Output

Every dataset row represents one saved Instagram post:

{
  "input": "Mall del Sol Guayaquil",
  "inputType": "name",
  "matchedLocationId": "123456789",
  "locationName": "Mall del Sol",
  "locationAddress": "Guayaquil, Ecuador",
  "locationCity": "Guayaquil",
  "latitude": -2.1552,
  "longitude": -79.8916,
  "postId": "3913133928818931888",
  "shortcode": "DZOPpNZx_iw",
  "postUrl": "https://www.instagram.com/p/DZOPpNZx_iw/",
  "mediaType": "video",
  "caption": "A public location-tagged post",
  "publishedAt": "2026-08-10T14:20:00Z",
  "likeCount": 530,
  "commentCount": 21,
  "playCount": 10400,
  "engagementRate": 0.052981,
  "username": "example_creator",
  "creatorVerified": false
}

Pricing behavior

The Actor uses two transparent events:

• apify-default-dataset-item is charged once after a post passes every filter and is saved successfully.
• search-page is charged once after a non-empty Instagram location-post page is retrieved and processed successfully.

Place lookups, failed requests, retries, duplicates, and empty pages are not charged. A page can still be billable when every candidate on it is rejected by the selected filters, because the upstream data was successfully retrieved and evaluated.

Filters are applied after each page is downloaded. A restrictive date, engagement, media, or verification filter can therefore require more billed pages and produce fewer saved posts than requested. Use maximumPagesPerLocation to set a predictable cost ceiling before the run begins.

Suggested Store prices per 1,000 saved posts: Free $0.70, Starter $0.65, Scale $0.60, Business $0.55.

Reliability and budget protection

• Provider failures are retried after 3, 9, and 27 seconds.
• Repeated pagination cursors stop safely.
• Duplicate posts are not saved twice.
• The Actor checks the Apify run charge limit before provider work and before each saved batch.
• maximumPagesPerLocation prevents an open-ended search when filters are too restrictive.
• RUN_PROGRESS is refreshed during the run, while OUTPUT stores the final matching, filtering, pagination, billing, provider-request, and error summary.
• Partial dataset results remain available when a later page or location fails.
• If Instagram's provider rejects a cursor it previously returned, the Actor retries after 3, 9, and 27 seconds. If the cursor remains invalid, it treats that point as the natural end of the location's pagination, preserves all prior results, and does not charge any rejected attempt.

Limits and expected behavior

• Instagram can return fewer posts than the number shown publicly on a place page.
• Place-name searches can be ambiguous. Use an Instagram location URL or numeric ID for deterministic matching.
• The maximum configured depth is 100 non-empty pages per matched location.
• Posts without a publication timestamp are excluded when a date filter is active.
• Engagement counters and location metadata depend on what Instagram exposes at extraction time.
• The Actor does not access private accounts, private posts, or content that requires an Instagram login.

Environment variable

Add SOCIALAPI_KEY as a secret environment variable in the Actor settings. Never place the provider key in source files or the input.

Responsible use

Use this Actor only for lawful analysis of publicly available information. Respect applicable privacy, data-protection, intellectual-property, advertising, and platform rules. Do not use the output for harassment, sensitive profiling, unlawful surveillance, spam, or attempts to identify private individuals. You are responsible for your inputs, retention policy, and downstream use of the data.

Support

For reproducible support, open an issue on the Actor page with the run ID, input with sensitive values removed, expected behavior, and the relevant log lines. Never include API keys, authorization headers, private continuation tokens, or another customer's data.