/fandom/categories/members

POST /api/fandom/categories/members

Price: 1 credit

List the pages, subcategories and files in a Fandom wiki category

How to use it

List the members of a category on a Fandom (Wikia) wiki. Pick the wiki by subdomain or URL and an optional language path segment, and the category by name (with or without the 'Category:' prefix). Optionally filter by member kind (pages, subcategories or files) or by page kind / namespace, and order members alphabetically or by the time they were added. Returns each member's page id, title, namespace, member type, the timestamp it was added to the category, and its URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• wiki string required — Wiki subdomain (e.g. harrypotter, minecraft) or a full wiki URL (examples: "harrypotter", "minecraft", "https://elderscrolls.fandom.com"; minLength: 1)
• lang string — Language path segment for multilingual wikis (e.g. de, es, pl); empty for the default (default: ""; maxLength: 8)
• category string required — Category name (with or without the 'Category:' prefix) (examples: "Spells", "Category:Mobs"; minLength: 1)
• type string nullable — Filter members by kind (pages, subcategories or files); all kinds by default (one of: "page", "subcat", "file")
• namespace string nullable — Filter members to a single page kind / namespace; all namespaces by default (one of: "article", "talk", "user", "project", "file", "template", "help", "category", "forum", "user_blog", "blog")
• sort string — Order members alphabetically by sort key or by the time they were added (default: "sortkey"; one of: "sortkey", "timestamp")
• count integer required — Number of category members to return (min: 1)

Response

• @type string (default: "FandomCategoryMember")
• id integer required
• alias string (default: "")
• namespace integer nullable
• type string nullable
• added_at string nullable
• web_url string (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 — The entity was not found, or a precondition failed 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.