List an Instagram user's posts

Run job:instagram.user.posts through the looot API: 2 providers, from $0.00188 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.

List an Instagram user’s posts.

Job id instagram.user.posts, in Social data (Instagram). As of 2026-10-01, 2 providers serve it through 2 tools. Run job:instagram.user.posts and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.

Inputs

Fields the job’s tools take, most shared first. Any key you send passes through unchanged.

Providers and prices

A call that fails at the provider costs $0. See What’s free.

Output

Each provider answers in its own shape. Shape of the run’s result from scrapecreators-instagram-user-posts, the expected shape, not yet checked against real answers:

{ user: { id, pk, pk_id, username, full_name, is_private, is_verified, strong_id__, profile_pic_id, profile_pic_url, profile_grid_display_type, is_active_on_text_post_app }, items: { id, pk, fbid, media_type, mezql_token, strong_id__, is_quiet_post, deleted_reason, original_width, image_versions2: { candidates: unknown[] }, original_height, client_cache_key, should_request_ads, has_privately_liked, has_delayed_metadata, share_count_disabled, organic_tracking_token, subtype_name_for_REST__, integrity_review_decision, collaborator_edit_eligibility, has_views_fetching_on_search_grid, profile_grid... ...

The shape is cut here. Signed in, looot inspect scrapecreators-instagram-user-posts prints all of it.

Run it

Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.

Example input with placeholder values:

curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"job:instagram.user.posts","input":{"handle":"<handle>"},"wait":30}'

const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "job:instagram.user.posts",
    input: {
      handle: "<handle>",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);

import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "job:instagram.user.posts",
        "input": {
            "handle": "<handle>",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))

To pin one provider, send its tool id as endpointId instead of job:instagram.user.posts.