/instagram/user

POST /api/instagram/user

Price: 1 credit

Instagram Web — get user profile by alias, URL or numeric ID (browser-faithful GraphQL)

How to use it

Instagram user profile via the www.instagram.com web path. Accepts username, URL, or numeric ID.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — User alias, URL or numeric ID (examples: "zuck"; minLength: 1)
• with_creation_date boolean — Include the account creation date (default: false)

Response

• @type string (default: "service__parsers__instagram__user__user__InstagramUser")
• id string required
• alias string required
• name string required
• url string required
• image string nullable
• description string nullable
• follower_count integer (default: 0)
• following_count integer (default: 0)
• media_count integer (default: 0)
• clip_count integer (default: 0)
• is_private boolean (default: false)
• is_verified boolean (default: false)
• is_business boolean (default: false)
• account_type integer nullable
• category string nullable
• external_url string nullable
• email string nullable
• phone string nullable
• whatsapp_number string nullable
• created_at integer nullable
• fbid string nullable
• pronouns array (default: [])
• location object nullable
  • @type string (default: "InstagramUserLocation")
  • street string nullable
  • city string nullable
  • city_id integer required
  • zip string nullable
  • latitude number nullable
  • longitude number nullable
• links array (default: [])
  • @type string (default: "InstagramUserLink")
  • url string required
  • type string nullable
• mentions array (default: [])
  • @type string (default: "InstagramUserMention")
  • id string required
  • alias string required
  • url string required
• hashtags array (default: [])
  • @type string (default: "InstagramUserHashtag")
  • id string required
  • name string required

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — User not found. Verify the username, URL or ID. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.