Intercept the request
Send your stable account ID with a credential scoped to your integration. The API checks existing links and active bans.
For apps, communities, and game servers
Discord login.
On your terms.
Connect your users’ accounts to Discord. Your backend checks access through one API, with scoped credentials and a record of each decision.
Create your workspaceRead the API documentationConnection traceChoose a stage
01Your backend sends a verified account ID to the access check.
02plexsur.net checks your workspace policy and any existing account link.
03An unlinked user chooses whether to connect their Discord identity.
Your application owns the account. Discord verifies the identity. plexsur.net connects the two.
A clear exchange before entry.
Users see which account they are linking, who requested it, and what Discord shares. A short-lived URL carries the challenge; your integration secret stays on your backend.
Read the login flowExample accountAccount ID 8667ba71…c4a2f2
Requested byExample Community / Member portalDiscord permissionIdentify your account
Continue with Discord
Connect the places your community uses.
Group integrations in a network to share account links, or keep them scoped to one application. You choose where a verified account can be recognized.
01WorkspaceShared policy
02Member portalCustom API integration
03Community appCustom API integration
04Game serverMinecraft integration
Every request, one clear decision.
Your backend requests a check. plexsur.net handles Discord consent and linking. Your application decides when to grant access.
Ask for Discord consent
An unlinked user receives a single-use URL. They review the request and choose whether to connect their Discord account.
Return one accountable decision
Check again after consent. Read the allow decision and verified Discord ID on your backend, then continue in your application.
Control every connection.
Stable identity
Links use your application’s stable UUID and the Discord user ID. Display names can change without changing the account.
Your stack, your flow
Call the HTTP API from your backend. Use the returned decision, consent URL, and cache duration in your own access flow.
Scoped credentials
Each integration receives its own credential. Rotate or revoke it independently from the rest of your workspace.
Decisions with a trail
Policies, bans, and authentication events stay searchable in your tenant audit log.
An API for your app.
Plugins for your server.
Build a custom integration for your website or service, or use a ready-made Minecraft plugin. Both use the same account linking flow.
Dashboard preview
See the workspace in context.
This is a static preview. Your workspace shows its integrations, links, policy decisions, and audit events after setup.
WORKSPACE / OVERVIEWSTATIC PREVIEW
Your workspace, at a glance.Live counts and activity appear here once an integration sends its first heartbeat.
IntegrationsHeartbeat statusPolicy decisions
Keep credentials behind the scenes.
Your backend holds the integration secret. plexsur.net handles OAuth state validation and short-lived challenges, then checks workspace bans before recording a link.
Read the security model- CSRF-safe Discord OAuth
- Cryptographically random challenges
- Fail-open or fail-closed, explicitly configured
- Signed webhooks with replay guidance