The official Discord API is a low-level surface built for bots and clients — you speak gateway events, cache manually and juggle intents. The Noxyr Server API is a high-level HTTP API scoped to one server that returns finished analytics. They solve different problems. Here's when to reach for each.

What the Discord API gives you

The Discord API documentation (heavily searched — Google Trends shows queries for "discord api documentation" up 700% year-over-year) is the source of truth for anything Discord itself owns: messages, users, guilds, roles, channels, voice, threads, moderation. You get a REST API for actions and a WebSocket gateway for events. Building anything realtime requires opening a persistent connection, handling READY and heartbeats, cache invalidation and rate-limit buckets.

What the Noxyr Server API gives you

The Noxyr Server API is a much smaller surface: six read-only endpoints scoped to a single server via a bearer token. It answers questions like "how many tickets this month?" or "revenue per currency" that the Discord API cannot answer at all, because the underlying data lives in the Noxyr database, not in Discord.

Side-by-side

  • Auth: Discord uses OAuth2 or bot tokens with intents. Noxyr uses one bearer token per server.
  • Transport: Discord is REST + WebSocket gateway. Noxyr is plain HTTPS with CORS enabled for browsers.
  • Scope: Discord is global to your bot across every server it's in. Noxyr is bound to one specific server.
  • Data shape: Discord returns raw objects — guilds, members, messages. Noxyr returns aggregates — totals, averages, daily buckets.
  • Rate limits: Discord uses bucketed limits per route. Noxyr is a flat 60 req/min per key.
  • Setup effort: Discord needs a bot app, invite, intents, event handlers. Noxyr needs one click to generate a key.

Pick Discord when…

  • You need real-time events (a message arrived, a member joined, a voice channel changed).
  • You want to send messages, edit channels, ban users or manage roles from your app.
  • You're building a Discord bot or a third-party Discord client.

Pick Noxyr Server API when…

  • You want to display live server stats on a public website without maintaining a bot.
  • You need ticket analytics, sales data, review averages or giveaway participation — data Discord doesn't store.
  • You want CORS-friendly JSON you can call from a browser dashboard with no proxy.
  • You want a stable, versioned surface where scope toggles let you kill data exposure without redeploying anything.

Using both together

The two APIs pair well. Use the Discord API in your own bot to react to events, and the Noxyr Server API to read aggregated state on your website. That way your public dashboard doesn't need bot intents or gateway connections at all — a single HTTPS request is enough.

More: Server API tutorial, design principles, handling Discord API errors.