Skip to main content
The Technified API lets you wire your own services into a guild’s data: Roblox game servers, custom dashboards, or internal tools. This reference covers the endpoints you can call with a guild API key. Dashboard-only routes that require a logged-in session are not listed here.
If you run the Adonis plugin, you do not need to call this API yourself. The plugin already handles verification lookups, ban and mute checks, and sync. This API is for builders wiring Technified into their own systems.

​
Base URL

https://api.technified.xyz/api/v1
Every path in this reference is appended to that prefix.

​
Authentication

You authenticate with a guild API key. A key is bound to one guild, so it can only read and write that guild’s data.

​
Get a key

1

Open the dashboard

Go to technified.xyz/dashboard and pick your server.
2

Create a key

Open Settings > API Keys, click Create API Key, and copy it right away. It is shown only once.
A key looks like technified_<guildId>_<random>. You can have up to 3 active keys per guild. Keep keys server-side. Never embed them in Roblox client scripts, browser code, or git. See API Keys for management.

​
Send the key

The API accepts the key in any of three header formats. Use whichever your HTTP client makes easiest. 
X-API-Key: technified_xxx_yyy

Authorization: ApiKey technified_xxx_yyy

Authorization: Bearer technified_xxx_yyy

​
Which guild the call targets

Your key has a guild ID baked into it. How you point a request at that guild depends on the endpoint:
Endpoint shapeHow to set the guild
Path contains :guildId (for example /moderation/:guildId/...)Put your guild ID in the path. It must match the key’s guild.
No :guildId in the path (for example /lookup/..., /bindings/list)Send the X-Guild-ID header.
If the guild in your key does not match the guild you are targeting, the API returns 403.

​
Response shape

Every successful response uses this envelope: 
{
  "status": "success",
  "code": 200,
  "message": "User is not banned",
  "data": { "banned": false }
}
Errors use a matching shape, with optional details: 
{
  "status": "error",
  "code": 401,
  "message": "Invalid API key for this guild"
}
See Errors for the full list of status codes.

​
Quick example

Check whether a Roblox user is banned in your guild. 
curl "https://api.technified.xyz/api/v1/moderation/$GUILD_ID/ban-status/$ROBLOX_ID" \
  -H "X-API-Key: $TECHNIFIED_API_KEY"
Response
{
  "status": "success",
  "code": 200,
  "message": "User is not banned",
  "data": { "banned": false }
}

​
Conventions

  • Request and response bodies are JSON.
  • Discord IDs are stringified snowflakes, for example "123456789012345678".
  • Roblox user and group IDs are numbers.
  • Timestamps in stored records are Unix seconds unless noted otherwise.
  • :identifier in moderation paths accepts a Roblox user ID.

​
Where to go next

Lookup

Resolve verification links between Discord and Roblox.

Moderation

Check ban and mute status, and manage Roblox punishments.

Bindings

Read and manage role bindings.

Shield

Check users against the Shield flagged list.

Rate limits

Per-category quotas and the 429 response.

Errors

Status codes and how to recover.