# Instagram Location Posts API (https://www.socialcrawl.dev/platforms/instagram/location-posts)

> Returns the posts tagged at an Instagram location, newest first, about 60 per page. Each post includes shortcode, URL, caption, media URLs, engagement counts, and the author. Pass `location_id` as `location.pk` from /v1/instagram/search/location, then page back in time with `cursor` until `has_more` is false. If the source that served page 1 fails on a later page, a backup source continues the walk and the page carries `continuation_rescued` in `data._warnings`: a few posts nearest the page boundary can be missing from that page. A busy place fills a page in about a day and a quiet one covers months or years, and the grid goes back to the location's oldest posts. Instagram orders the grid by when each post was created, so a scheduled post that went live later sits among older posts while its published_at shows the real publish time (about 1 post in 75, up to 13 days apart, measured 13/09/2026). To collect a time window, keep paging until a whole page is older than the window's start and filter on published_at; do not stop at the first older post. Each page is a separate call at the listed price. A location grid mixes photos and reels, so engagement.views is a number on the video rows and null on the photo rows. This is the region-scoped Instagram route: /v1/instagram/reels/trending and /v1/instagram/music/trending take no region, because Instagram ties both to the account viewing them. Note: post.author.display_name is not available on this endpoint, because the Instagram surface behind it withholds creator display names. Join on post.author.username, or pass it to /v1/instagram/profile?handle= for the name.

TL;DR: `GET /v1/instagram/location/posts` costs 5 credits per page. `include=country` holds 63 more credits a page and keeps 1 per creator whose declared country came back, refunding a creator who publishes none or cannot be found, so a page with it costs 5 to 68. A page that fails is refunded in full and looks no creator up. With `max_pages`, `max_items` or `max_credits`, each page walked is billed at this price (a cached page is free), and `max_credits` caps the total. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `location_id` | yes | Instagram location id. Use location.pk from /v1/instagram/search/location. |
| `cursor` | no | Pagination cursor. Use the `next_cursor` from the previous response to fetch the next, older page. |
| `safe_url` | no | When true, returns URL-safe media links suitable for embedding. |
| `include` | no | Send `country` to add each post's creator country as `post.ext.author_country`: the country the creator declares on Instagram's About this account panel, not the place the post is tagged at, and null when the creator publishes none. Every row carries the creator's numeric id as `post.ext.author_id`, which is what it is read by. 1 extra credit per creator whose country came back; two posts by one creator cost one lookup, a creator looked up in the last 30 days is free, and a creator who publishes none or cannot be found is refunded. A typo is a free 400. (country) |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/instagram/location/posts" \
  --data-urlencode "location_id=331004901" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I get Instagram posts by location with an API?

Send a GET request to /v1/instagram/location/posts with the location_id parameter. SocialCrawl returns a JSON array of recent posts tagged at that location including shortcode, url, caption, media URLs, engagement counts, and author.

### Where do I get the location_id to pass in?

Call /v1/instagram/search/location first with a place name. Pass that result's location.pk as location_id. The search response has no location.id.

### How do I page through more location posts?

Each response includes a cursor. Pass it back as the cursor parameter to fetch the next, older page of posts for the same location, until has_more is false. Pages run newest first, so to collect a time window keep paging until a whole page is older than the window's start.

### Can I get CDN-safe media URLs?

Yes. Add the optional safe_url parameter and the response returns proxied media URLs that stay reachable, which is useful when you cache or re-host thumbnails.

### How much does the Instagram Location Posts API cost?

This is an advanced endpoint at 5 credits per page returned. New accounts get 100 free credits, so you can pull around 20 pages before topping up.

See the full Instagram API: https://www.socialcrawl.dev/platforms/instagram

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to pull recent Instagram posts tagged at a location with an API
- Instagram location posts API for local marketing and venue research