Instagram Data API | API Docs

Read Instagram profiles, posts, Reels, stories, comments, followers, locations, and search results through 93 authenticated endpoints.

Authentication

Use your RequestBeam API key in the authorization header. Availability depends on enabled gateways and API key permissions; documentation alone does not confirm production availability.

http

Authorization: Bearer YOUR_API_KEY

All operations use GET query parameters without a request body. The version segment selects the Instagram interface version. Unknown or duplicate fields are rejected. Keep identifiers and pagination cursors as strings, including values larger than JavaScript can safely represent as numbers.

bash

curl --get "https://api.apihop.ai/v1/instagram/v1/users/profile/by-username" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "username=instagram"

Responses

The native JSON response is preserved, including its code/data envelope and numeric precision. Shapes differ by operation. Empty successful results can be billable; an error is not an empty result. The following example is illustrative, not a live response.

json

{"code":200,"data":{"user":{"id":"25025320","username":"instagram"}}}

Billing and pagination

Prices are per successful request, not per returned item. Every page is a separate request. V1 costs $0.001; V2 costs $0.002; V3 costs $0.008 except its three shortcode utilities, which cost $0.002. Account-specific prices take precedence. Supplier volume discounts are not automatically passed through. Failed upstream calls release the reservation; settlement failures return an error and do not trigger a second upstream request.

Reference

Select an endpoint and send only its documented fields. When alternatives are listed, provide at least one field from each group. Pagination values must come from the preceding response; there is no automatic pagination.

Complete reference

Errors

Platform errors use HTTP 400 for invalid parameters, 401 for invalid authentication, 402 for insufficient credit, 403 for denied gateway access, 429 for rate limits, and 5xx for service or supplier failures. Keep X-Request-Id for troubleshooting. Do not treat an upstream HTTP 200 with a failed business code as success.

Sources

The endpoint list and prices were checked against the official schema and live price metadata on 2026-10-31. Live metadata takes precedence over conflicting prose prices.

TikHub · OpenAPI · Prices