Overview

herascrape reads Instagram's public data through 37 REST endpoints. One call fetches one Instagram page. Responses are Instagram's own JSON, passed through untouched.

Start here

The basics

Base URL is https://api.herascrape.com. Every endpoint is a GET.

Authentication is the X-Api-Key header. Keys come from the dashboard. See Authentication.

Responses are Instagram's own JSON, in full. Fields are not renamed or trimmed. Every reference page shows a real example under What comes back.

So the shape follows Instagram, not us. Most endpoints read from Instagram's REST API and look alike. A few read from a different internal source and look different: one post's data can arrive split across two parts of a single response, and the token that turns the page is not always called the same thing. Nothing is missing when that happens — but reading one key and assuming the rest matches the last endpoint will quietly lose data. Skim the endpoint's own What comes back before you map it, and treat that page as authoritative over any pattern you inferred elsewhere.

Most lists paginate on one opaque cursor. These endpoints return the same envelope:

{
  "items": [],
  "next_cursor": "eyJtYXhfaWQiOiIyNSJ9",
  "has_more": true
}

Pass next_cursor back as ?cursor= and stop when has_more is false. A few endpoints answer in Instagram's own envelope instead and name their own paging token; each says so on its page. See Pagination.

Endpoint groups

Two surfaces, one API

These pages are the reference. The API also serves a generated OpenAPI (Swagger) UI at api.herascrape.com/docs — the same endpoints with no prose, useful for poking the live service.