/gab/posts/reposted_by

POST /api/gab/posts/reposted_by

Price: 5 credits

Get Gab Accounts That Reposted a Post

How to use it

List the accounts that reposted a Gab post, newest repost first, as full profiles rather than bare handles. This is the one keyless way into Gab's social graph: followers and following are closed, so reposters of a post are the reachable audience of an account. The list of accounts that favourited a post is not available.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• post string required — Gab post URL or numeric post id (examples: "https://gab.com/a/posts/117250539305495961", "117250539305495961"; minLength: 1)
• count integer required — Max result count (examples: 20; min: 1; max: 400)

Response

• @type string (default: "GabAccount")
• id string required
• alias string nullable
• display_name string nullable
• bio string nullable
• url string nullable
• image string nullable
• cover string nullable
• created_at string nullable
• follower_count integer nullable
• following_count integer nullable
• status_count integer nullable
• country_code string nullable
• is_verified boolean (default: false)
• is_pro boolean (default: false)
• is_donor boolean (default: false)
• is_investor boolean (default: false)
• is_parody boolean (default: false)
• is_spam boolean (default: false)
• is_locked boolean (default: false)
• is_discoverable boolean (default: false)
• has_pro_life_badge boolean (default: false)
• fields array (default: [])
  • @type string (default: "GabField")
  • name string nullable
  • value string nullable
  • verified_at string nullable
• emojis array (default: [])
  • @type string (default: "GabEmoji")
  • shortcode string nullable
  • url string nullable
  • static_url string nullable
  • is_visible_in_picker boolean (default: false)

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 — Post not found. Verify the URL or numeric 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.