Instagram Location Scraper - Places, Coordinates and Posts

This Instagram location scraper turns an Instagram location ID or location URL into structured place data: name, coordinates, category, phone, the total number of posts tagged there and a sample of recent post shortcodes. Use it for venue research, tourism analysis and local marketing. No login, no cookies and no API key.

It does one thing, takes one input and returns one clean row per location, ready to export as JSON, CSV or Excel or to pull through the Apify API.

What the Instagram location scraper returns

• name and location_name - the place as Instagram names it
• latitude, longitude, lat, lng - coordinates as numbers, for mapping and joins
• media_count - total posts tagged at the location, the popularity signal
• category - the type of place, for example City or Landmark & Historical Place
• phone - the venue phone number when the place lists one
• street, city, city_name, zip - address parts when Instagram publishes them
• recent_post_count and recent_post_shortcodes - a sample of what is being posted there now
• location_id, slug and url - the canonical id, the name slug and the public URL for joining back

Why scrape Instagram location pages

Instagram location pages are a geographic dataset hiding in plain sight. Every venue, landmark and city that has ever been geotagged has a page with coordinates and a running post count, which together make a decent proxy for foot traffic and cultural relevance. None of it is exposed through an official API, and the pages are built for browsing rather than extraction.

This actor accepts either a bare location ID or a full location URL, detects which you gave it, and returns the page as a row. Coordinates come back as numbers, so the output joins directly against your own venue list or drops into a mapping tool without cleanup.

Input

Field	Type	Required	Default	Description
search	array	yes	none (prefill: ['213385402'])	Instagram location IDs or full location URLs, one per line.

Example input:

{
  "search": [
    "213385402",
    "https://www.instagram.com/explore/locations/212988663/",
    "26056"
  ]
}

An ID and the URL of the same place count as one location, so duplicates in your list return one row.

Output

One row per location. This is a real row returned for location 26056, Leake Street Tunnel in London:

{
  "record_type": "location",
  "location_id": "26056",
  "place_id": "26056",
  "url": "https://www.instagram.com/explore/locations/26056/",
  "name": "Leake Street Tunnel",
  "location_name": "Leake Street Tunnel",
  "latitude": 51.502,
  "longitude": -0.1157,
  "lat": 51.502,
  "lng": -0.1157,
  "media_count": 139088,
  "street": null,
  "city": null,
  "city_name": null,
  "zip": null,
  "postal_code": null,
  "category": "Landmark & Historical Place",
  "phone": "+44 20 7401 9603",
  "website": null,
  "meta_description": null,
  "slug": "leake-street-tunnel",
  "price_range": 1,
  "recent_post_shortcodes": [
    "DeCRxrYjq5i",
    "DeCKtsViP7d",
    "DdaetmvjcYz",
    "Ddaea3hDVPE",
    "Dcy9lQpNj40",
    "Dcy9Y9ht8YW",
    "Db3ecSNI2IV",
    "Das-Ky_p8rz",
    "Das91xcpbwQ",
    "Das9mn1p18h",
    "DeBv8fQDPo4",
    "Dcd_fWCs95g",
    "Da7nV-vDtv9",
    "DbbsdbQjM_i",
    "Dbbr_3OjMK1",
    "Dcly3RfkwOW",
    "DeCK4cvEd0M",
    "DaekmGtTQHR"
  ],
  "recent_post_count": 18,
  "_type": "place",
  "source": "instagram-location-scraper",
  "fetched_at": "2026-10-03T15:17:23.182Z",
  "platform": "instagram",
  "result_count": 1
}

Field	Description
record_type	Which kind of row this is (location)
location_id	Instagram numeric location id
place_id	Same id, under the name used across our place datasets
name	Place name as Instagram shows it
location_name	Place name as Instagram shows it
city	City the place sits in, when published
city_name	City name as Instagram reports it, when published
street	Street address when published
zip	Postal code when published
postal_code	Same postal code, under the shared place field name
lat	Latitude
lng	Longitude
latitude	Latitude as returned upstream
longitude	Longitude as returned upstream
category	Place category, for example City
phone	Phone number when the place lists one
website	Website when the place lists one
meta_description	Page description when present
slug	Name slug Instagram uses in the location URL
price_range	Price range indicator Instagram stores for the place
media_count	Total posts tagged at this location
recent_post_count	Recent posts sampled
recent_post_shortcodes	Shortcodes of the recent posts
url	Public Instagram URL for this record
source, platform, fetched_at	Where and when the row was collected

Fields Instagram does not publish for a place come back as null rather than guessed.

Use cases

Retail and hospitality site analysis. Pull media_count for a set of candidate locations and compare. A venue with a high tagged-post count relative to its neighbours has organic visibility that does not show up in footfall data, which matters when the decision is between two addresses on the same street.

Tourism and destination research. Location pages reveal which spots visitors actually geotag, which frequently differs from the official attraction list. Coordinates plus post counts turn that into an Instagram location map of where attention concentrates in a city.

Competitive venue benchmarking. Track your own location against nearby competitors over time. Because media_count is cumulative, sampling it on a schedule gives you a growth rate rather than a single reading, and the rate is the interesting number.

Finding Instagram location posts. The recent post shortcodes point at what people are posting at a place right now. Feed them into an Instagram post scraper to get captions, likes and creators, for example to find local influencers around a venue.

Enriching a venue database. If you already hold a list of Instagram location IDs, this fills in name, category, phone and coordinates in one pass. Useful for cleaning a venue table where coordinates are missing.

How it compares

Most Instagram location tools on the Store are post scrapers: they page through every post tagged at a place and charge per post. That is the right tool when you need the full post history. This actor answers a different question, namely what the place is, where it is and how popular it is, at one result per location. If you track hundreds of venues, you pay for hundreds of rows instead of tens of thousands of posts, and the recent shortcodes still let you drill into posts when a place looks interesting. Location ID finders do the reverse job: they search a place name and return its ID, which you can then pass here.

Pricing

$0.0020 per location returned, which is $2.00 per 1,000 rows. All pricing is pay-per-event - you only pay for results you receive. No actor-start fee, no per-compute-unit charges. A location that does not exist returns no row and costs nothing.

Limits and gotchas

• Input is an ID or a location URL. There is no name search.
• Some locations publish no street, city or postal code; those fields come back empty rather than guessed.
• media_count is the count Instagram reports when the location is fetched; it can change between runs.
• Recent post shortcodes are a sample, not the full tagged history.
• Free Apify plans are capped at 10 rows per run. Paid plans have no cap.
• Locations that have been merged or removed return no dataset row; details appear in the errors record and the run completes successfully.

FAQ

How do I find an Instagram location ID?

It is the numeric segment in a location URL, for example the digits in instagram.com/explore/locations/213385402/. You can paste either the bare ID or the whole URL; the actor detects which you gave it.

Can I scrape Instagram locations without logging in?

Yes. Location pages are public and this actor reads them logged out, so no account, cookie or API key is involved.

Does it return the posts tagged at a location?

It returns a sample of recent post shortcodes plus the total tagged-post count. For full post detail, feed those shortcodes into an Instagram post scraper.

Are the coordinates accurate enough to map?

They are the coordinates Instagram holds for the venue, returned as numbers rather than strings, so they plot directly. Accuracy is whatever Instagram recorded when the place was created.

Can I search locations by name?

Not with this actor. It resolves known IDs and URLs rather than performing a place search.

What happens if I pass a word instead of an ID?

Free text that is not a location ID or location URL returns no row and is not charged; the run still succeeds and the errors record says which input was skipped.

Can I use it as an Instagram scraper API?

Yes. Start the actor through the Apify API with the same search input and read the dataset as JSON, CSV or Excel, or schedule it to track the same locations every day.

Related Actors

• Instagram Profile Scraper
• Instagram Post Scraper
• Instagram Keyword Scraper