POST /api/mastodon/accounts/followers
Price: 5 credits
Get Mastodon Account Followers
Get accounts following a Mastodon account. Accepts a handle, profile URL, or numeric id. Returns an empty list when the account hides its social graph.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)instance string — Host instance domain to query (default: "mastodon.social"; examples: "mastodon.social", "fosstodon.org")account string required — Account handle (user or user@home_instance), profile URL, or numeric account id (examples: "Gargron", "https://mastodon.social/@Gargron"; minLength: 1)count integer required — Max result count (examples: 80; min: 1)@type string (default: "MastodonAccount")id string requiredusername string nullableacct string nullabledisplay_name string nullablenote string nullableurl string nullableuri string nullableimage string nullableavatar_static string nullableavatar_description string nullableheader string nullableheader_static string nullableheader_description string nullablecreated_at string nullablelast_status_at string nullablefollower_count integer nullablefollowing_count integer nullablestatus_count integer nullableis_locked boolean (default: false)is_bot boolean (default: false)is_group boolean (default: false)is_discoverable boolean (default: false)is_indexable boolean (default: false)noindex boolean (default: false)hide_collections boolean (default: false)fields array (default: [])@type string (default: "MastodonField")name string nullablevalue string nullableverified_at string nullableemojis array (default: [])@type string (default: "MastodonEmoji")shortcode string nullableurl string nullablestatic_url string nullablevisible_in_picker boolean (default: false)roles array (default: [])@type string (default: "MastodonRole")id string nullablename string nullablecolor string nullable422 — 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 — Account not found. Verify the handle, URL, or id and instance. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.