# Instagram Tagged API (https://www.socialcrawl.dev/platforms/instagram/tagged)

> Returns a paginated list of the posts that tag an Instagram user. Each post includes shortcode, URL, caption, media URLs, engagement counts, and the author. Pass either `handle` or `user_id`, and page through with `cursor`. Note: post.author.display_name is usually null on this endpoint, because the Instagram surface behind it withholds creator display names; it carries the real name on the calls a second source answers. Join on post.author.username, or pass it to /v1/instagram/profile?handle= for the name.

TL;DR: `GET /v1/instagram/tagged` costs 5 credits per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `handle` | no | Instagram username without the @ symbol. |
| `user_id` | no | Instagram numeric user ID. Use this for faster responses. |
| `cursor` | no | Pagination cursor. Use the `next_cursor` from the previous response to fetch the next page. |
| `safe_url` | no | When true, returns URL-safe media links suitable for embedding. |
| `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/tagged" \
  --data-urlencode "handle=mrbeast" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I get posts that tag an Instagram user via API?

Send a GET request to /v1/instagram/tagged with a handle or user_id. SocialCrawl returns a paginated JSON array of posts that tag that account, each with shortcode, url, caption, media URLs, engagement counts, and author.

### Can I query tagged posts by user ID?

Yes. Pass user_id instead of handle. Using user_id is faster because SocialCrawl skips resolving the username to an ID before fetching tagged posts.

### How do I paginate tagged posts, and what is safe_url?

Send the returned cursor back as the cursor parameter for the next page. Pass optional safe_url to receive proxied, CDN-safe media URLs that are stable to embed.

### How much does the tagged posts API cost?

Each request costs 5 credits on the advanced tier for one page of tagged posts. New accounts get 100 free credits with no credit card required to start.

### What is tagged post data useful for?

Tagged posts track brand mentions and UGC: monitor who tags your brand, measure influencer campaign deliverables, or surface user-generated content for reuse.

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 find Instagram posts that tag a specific user with an API
- API to monitor brand mentions and tagged posts on Instagram