Instagram API Postman Collection

Import the document

The OpenAPI 3.1 document is served at /openapi.json and is generated from the same endpoint catalogue that drives the API itself, so it cannot describe an endpoint that does not exist or omit one that does. In Postman, use Import, choose Link, and paste the URL. Insomnia takes the same URL under Import From, URL. Both produce a collection containing one GET request per endpoint.

https://socialscrape.dev/openapi.json

# Or save it locally first
curl -s https://socialscrape.dev/openapi.json -o inscrape-openapi.json

Set the key as a collection variable

The document declares an apiKey security scheme named x-api-key in the header, applied to every operation, so Postman creates an API Key auth entry on the collection. Set the value to a variable rather than pasting the key into it: open the collection, add a variable called apiKey with your key as the current value, and reference it as a template in the auth block. Keep the key in the current value column, which is local to you, rather than the initial value, which is what gets shared when you export or sync the collection.

Collection > Variables
  apiKey    (initial value: empty)    (current value: sk_YOUR_KEY_HERE)

Collection > Authorization
  Type:  API Key
  Key:   x-api-key
  Value: {{apiKey}}
  Add to: Header

Request > Authorization
  Type:  Inherit auth from parent

What the import actually gives you

Sixteen GET requests, grouped under an instagram tag, each named after the endpoint and carrying its one-line description together with its credit cost. Every query parameter arrives with its description, type and default where one exists, including handle, cursor, next_cursor, url, keyword, tag and highlight_id. Response schemas are attached for 200 and for the declared error statuses, so Postman can validate both successful and failed calls.

One thing to fix after importing

The servers entry in the document points at the site origin, so if you call the API on api.socialscrape.dev, change the collection's base URL variable to https://api.socialscrape.dev after importing. The requests themselves are generated from the live endpoint catalogue.

Collection > Variables
  baseUrl   (current value: https://api.socialscrape.dev)

Generating client code from the collection

Once a request works in Postman, its code generator will produce a working snippet in most languages, and because the authentication is a single header the generated code needs no editing beyond moving the key into an environment variable. The same document also feeds openapi-generator and similar tools if you would rather have a typed client than a collection.

For agents rather than humans

The same document is what an AI agent reads to discover the API without a wrapper you have to write, and there is a plain-text catalogue at /llms.txt covering endpoints, pricing and the error contract in a form a model can consume in one read.