/instagram/user/tagged

POST /api/instagram/user/tagged

Price: 1 credit

Instagram Web — get posts a user is tagged in, by alias, URL or numeric ID

How to use it

Instagram posts a user is tagged in, 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: "nasa"; minLength: 1)
• count integer required — Max number of tagged posts to return (min: 1)

Response

• @type string (default: "InstagramPost")
• id string required
• code string required
• url string required
• image string required
• text string nullable
• type string nullable
• created_at integer nullable
• like_count integer (default: 0)
• comment_count integer (default: 0)
• reshare_count integer (default: 0)
• carousel_media_count integer (default: 0)
• is_paid_partnership boolean (default: false)
• user object nullable
  • @type string (default: "InstagramPostUser")
  • id string required
  • alias string required
  • name string required
  • url string required
  • image string nullable
  • is_verified boolean (default: false)
  • is_private boolean (default: false)
  • fbid string nullable
• location object nullable
  • @type string (default: "InstagramPostLocation")
  • id string required
  • name string required
  • lat number nullable
  • lng number nullable
• media array (default: [])
  • @type string (default: "InstagramPostMedia")
  • pk string nullable
  • type string required
  • url string required
  • width integer (default: 0)
  • height integer (default: 0)
  • duration number nullable
  • usertags array (default: [])
    • @type string (default: "InstagramPostTag")
    • id string required
    • alias string required
    • name string required
    • url string required
    • is_verified boolean (default: false)
    • position array (default: [])

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. 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.