Discord Server Metadata Lookup

🎯 What this scrapes

Discord's public invite-resolution endpoint answers one invite code at a time with real guild metadata — name, description, icon, verification level, approximate member/presence counts — but there's no bulk form and no batch tooling around it. This Actor takes a list of invite codes or URLs (bare code or full discord.gg/discord.com/invite link), resolves each one against Discord's own keyless API, and returns one clean row per input item in order. It's a metadata lookup, not a crawl: no message history, no member rosters, no authenticated Discord API calls of any kind.

🔥 What we handle for you

• 🔍 Local format validation, free — every invite code or URL is normalized and validated before any network call, so a malformed entry never costs you a billed row.
• 🔁 Retries with exponential backoff on 408 / 429 / 5xx — up to 5 attempts, Discord's own retry_after and the Retry-After header both honoured.
• 🫠 One bad invite never fails the run — an expired, invalid, or unreachable invite is logged and rowed as not_found/transport_error; the rest of your list still ships.
• 🧊 Clean, typed dataset rows — Pydantic-validated, stable fields, JSON / CSV / Excel export straight from the Apify Console.
• 💰 Pay-Per-Event pricing — you only pay for invite codes that resolve to a real server. Invalid, not-found, and failed lookups are free.

💡 Use cases

• Track a competitor's Discord community size and growth over time from a list of invite links.
• Enrich a server directory or Web3/gaming project database with live member/presence counts and verification level.
• Screen a list of partner or sponsor Discord servers for legitimacy signals before outreach.
• Feed a growth-marketing dashboard with server metadata pulled from links shared across social channels.

⚙️ How to use it

1. Click Try for free at the top of the page.
2. Fill in the input form — most fields have sensible defaults.
3. Click Start. Output streams into the run's dataset.
4. Export from Storage → Dataset as JSON, CSV, or Excel — or fetch via the API.

📥 Input

Example input

{
  "invite_codes_or_urls": [
    "python",
    "discord-developers",
    "reactiflux"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

📤 Output

Every row is one dataset item.

Example output

{
  "input_value": "https://discord.gg/python",
  "invite_code": "python",
  "is_valid_input": true,
  "lookup_status": "resolved",
  "error_reason": null,
  "guild_id": "192485424653418496",
  "guild_name": "Python Discord",
  "guild_description": "The number one place on Discord for Python programmers.",
  "guild_icon_hash": "5cf0526...",
  "guild_icon_url": "https://cdn.discordapp.com/icons/192485424653418496/5cf0526....png",
  "verification_level": 3,
  "vanity_url_code": "python",
  "approximate_member_count": 431208,
  "approximate_presence_count": 76485,
  "invite_expires_at": null,
  "inviter_username": null,
  "channel_id": "267624335836053506",
  "channel_name": "welcome",
  "channel_type": 0,
  "looked_up_at": "2026-09-15T00:00:00Z"
}

💰 Pricing

Pay-Per-Event — you pay only when these events fire:

Example: 1 000 results at the rates above ≈ $5.20. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit.

🚧 Limitations

• Up to 500 invite codes/URLs per run, one lookup per item — there's no batch form on Discord's own endpoint.
• Only servers reachable through a live, unexpired invite code can be looked up — there's no server-directory search or discovery of codes you don't already have.
• Member-level data (rosters, roles, permissions) and channel contents (messages, threads, pins) are never returned — Discord's invite endpoint doesn't expose them.
• inviter_username is frequently null — many servers configure invites without an exposed creator.

❓ FAQ

Do I need a bot token or Discord login?

No. This Actor uses only Discord's public, keyless invite-resolution endpoint — no OAuth, no bot token, no login.

Does this scrape messages or member lists?

No. It returns aggregate server metadata only — name, description, icon, verification level, approximate member/presence counts. Discord's invite endpoint never exposes message history or a member roster, and this Actor doesn't use any authenticated API that would.

What if an invite code is expired or invalid?

It comes back as a normal row with lookup_status set to not_found or invalid_input and a short error_reason — the run still succeeds, and that row is never billed.

Can I pass a full discord.gg link instead of just the code?

Yes. Both discord.gg/ and discord.com/invite/ links are parsed locally into the bare code before any network call — paste whichever form you have.

[object Object]