Curent Docs
Documentation

Verification API

Use Curent's custom, server-scoped API in your own verification tools.

API keys

Curent provides its own server-scoped Verification API. Open Settings → API and generate a key for the Discord server you want to connect. Keys begin with curent_live_ (older keys start with cv_live_ and keep working), are shown only once, and stop working immediately when replaced or revoked.

Keep the key in a server-side environment variable. Never place it in browser JavaScript, a public repository, or a Discord message.

If you run your own verification panel, send members to your server's public link instead of posting a Curent panel. It is shown under each server in Settings → API and looks like https://curentbot.xyz/verify/your_dashboard_id.

The member signs in with Discord, links their Roblox account, and returns to Discord. Your bot then calls the API below with their Discord ID and grants your own roles.

Usage

Open Settings → API to see requests used, requests remaining, and the reset time for every server you own. Each API key has its own rolling 24-hour window.

Daily limits are 50 requests on Free, 150 on Secure, and 1,000 on Pro. Secure and Pro limits apply only to the server where that plan is activated.

Discord to Roblox

Resolve the Roblox account linked to a Discord member. The member must be in your Discord server, and :serverID is your Discord server ID.

GET https://curentbot.xyz/api/v1/guilds/:serverID/discord-to-roblox/:userID

curl "https://curentbot.xyz/api/v1/guilds/789699000047370261/discord-to-roblox/214858075650260992" \
  -H "Authorization: Bearer curent_live_your_key"

200 { "robloxID": "146941966", "robloxUsername": "RobloxUser" }
404 { "error": "This member has not linked a Roblox account" }

Roblox to Discord

Find the Discord members in your server who linked a Roblox account. Only people currently in your server are returned.

GET https://curentbot.xyz/api/v1/guilds/:serverID/roblox-to-discord/:robloxID

curl "https://curentbot.xyz/api/v1/guilds/789699000047370261/roblox-to-discord/146941966" \
  -H "Authorization: Bearer curent_live_your_key"

200 { "discordIDs": ["214858075650260992"] }

Update a member

Do what happens when a member presses Verify: Curent gives them your server's verified role if they have linked Roblox. Set up verification and the role under Security → Verification first.

POST https://curentbot.xyz/api/v1/guilds/:serverID/update-user/:userID

curl -X POST "https://curentbot.xyz/api/v1/guilds/789699000047370261/update-user/214858075650260992" \
  -H "Authorization: Bearer curent_live_your_key"

200 { "addedRoles": ["Verified"], "removedRoles": [], "nickname": null }

If the member already has the role, addedRoles is empty. Curent needs Manage Roles and its role must sit above the verified role in Discord.

Legacy lookup

Send the Discord member ID as discord_user_id. Curent only returns a result if that member is currently in the Discord server attached to the key.

curl "https://curentbot.xyz/api/v1/verification/roblox?discord_user_id=123456789012345678" \
  -H "Authorization: Bearer curent_live_your_key"

You can also send the key in the X-API-Key header. Copy the complete key when it is generated; the shortened key shown later in Settings is only an identifier.

Legacy response

{
  "object": "roblox_verification",
  "server_id": "your_curent_server_id",
  "discord_user_id": "123456789012345678",
  "verified": true,
  "roblox": {
    "user_id": "987654321",
    "username": "RobloxUser"
  },
  "verified_at": "2026-08-12T20:00:00.000Z"
}

An unlinked member still returns 200 with verified: false and roblox: null.

Errors & limits

400 means the Discord ID is invalid. 401 means the key is missing, invalid, replaced, or revoked. 404 means the member is not in the key's Discord server. 429 means the key reached its daily limit. Curent may return 502 or 503 when Discord verification is temporarily unavailable.

Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Window headers.