Discord Servers Scraper
Under maintenancePricing
from $4.99 / 1,000 results
Discord Servers Scraper
Under maintenanceA robust, high-performance utility designed for developer automation, data integration, and AI training. Features built-in captcha bypass, headful/headless browser execution, and proxy support to scrape Discord Servers data seamlessly, reliably, and at scale.
Pricing
from $4.99 / 1,000 results
Rating
0.0
(0)
Developer
Coding Frontned
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
4 days ago
Last modified
Categories
Share
Collect real, publicly visible Discord server listings from Disboard. Search by keyword or browse a public tag/category, optionally apply a language filter, and receive normalized server identities, descriptions, counts, tags, icons, and listing links.
The Actor reads public listing pages only. It does not log in, solve CAPTCHAs, inspect protected state, or bypass access controls. A CAPTCHA, WAF, login, rate-limit, or changed-page failure is logged and fails the run; it is never stored as a Discord server dataset row.
Input
Provide either searchQuery or category.
| Field | Type | Default | Description |
|---|---|---|---|
searchQuery | string | — | Public listing keywords, up to 120 characters. |
category | string | — | Public Disboard tag/category, such as gaming or technology. |
language | string | — | Optional language or locale code. |
maxItems | integer | 40 | Result limit from 1 to 100. Pagination is bounded to four Load More actions. |
proxyConfiguration | object | {} | Standard Apify proxy configuration. Invalid requested settings fail closed. |
userAgent | string | — | Advanced override. When omitted, Playwright's platform-consistent browser identity is used. |
Example search:
{"searchQuery": "gaming","maxItems": 10}
Example category with ordinary Apify Proxy routing:
{"category": "technology","language": "en","maxItems": 10,"proxyConfiguration": { "useApifyProxy": true }}
Invalid inputs fail before browser startup. Direct HTTP access to Disboard may return 403, so the Actor uses one bounded Playwright browser with session/cookie persistence and strict retries.
Output
Every dataset row represents a real public Disboard listing. Required fields are position, serverId, name, serverUrl, sourceUrl, sourceDomain, and scrapedAt. Optional fields are omitted when the source does not display them.
{"position": 1,"serverId": "123456789","name": "Example Gaming Hub","description": "A public community for cooperative games and events.","memberCount": 12500,"onlineCount": 840,"category": "gaming","tags": ["gaming", "community"],"inviteUrl": "https://disboard.org/server/join/123456789","serverUrl": "https://disboard.org/server/123456789","thumbnailUrl": "https://disboard.org/images/server-icon.png","bumpTime": "5 minutes ago","searchQuery": "gaming","sourceUrl": "https://disboard.org/servers?query=gaming&sort=-bump","sourceDomain": "disboard.org","scrapedAt": "2026-08-31T00:00:00.000Z"}
Output is deduplicated by serverId, maxItems is enforced across pagination, compact counts such as 12.5K are normalized to integers, relative icon URLs become absolute, and empty optional values are omitted.
Responsible operation and limitations
- Use small limits and an appropriate interval; public listings change over time.
- Disboard may present access-control pages based on network reputation. The Actor retires the affected session and performs at most one crawler retry.
- Proxy access depends on the configuration available to the Apify account.
- The Actor stops at a missing or ambiguous public Load More control rather than guessing another interaction.
- No custom key-value records are created; entity data is stored in the default dataset.
For local testing, run apify run --purge --input-file qa-inputs/local-validation.json. For cloud validation, use the bounded cloud input and inspect the resulting dataset rather than relying only on run status.