Introduction
Welcome to the Technified API documentation. This API allows you to seamlessly connect Discord and Roblox profiles, enabling verification and synchronization between the two platforms. With our robust set of endpoints, you can build powerful integrations that enhance user experience across your Discord servers and Roblox games.
Technified is currently a private system being developed by Alex Tech Incorporated, there is currently no exact date when Technified will be used commercially.
The documentation is a work in progress, but covers the basic functionality of the API.
Base URL
All API requests should be made to the following base URL:
https://technified.xyz/api
API Version
The current version of the API is v1. We recommend specifying the version in your requests to ensure compatibility with future updates.
Quick Start Guide
Learn how to integrate Technified API into your applications with our step-by-step tutorial.
Get StartedExample Projects
Explore sample implementations and projects that showcase the power of Technified integration.
View ExamplesAuthentication
All API requests require authentication using an API key. This key must be included in the headers of each request to identify your application and apply appropriate rate limits.
API Key
Include your API key in the Api-Key
header with every request:
Api-Key: your_api_key_here
Never expose your API key in client-side code or public repositories. Always make API calls from your server-side code.
Obtaining an API Key
API keys are issued to verified partners. To request an API key, please reach out to our team through the Technified Discord server.
Error Handling
The API uses conventional HTTP response codes to indicate the success or failure of requests. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that resulted from the provided information, and codes in the 5xx range indicate an error with our servers.
HTTP Status Codes
Code | Description |
---|---|
200 - OK | The request was successful. |
201 - Created | The resource was successfully created. |
400 - Bad Request | The request was invalid or cannot be served. The exact error is specified in the response body. |
401 - Unauthorized | The API key is missing or invalid. |
403 - Forbidden | The request is understood but has been refused or access is not allowed. |
404 - Not Found | The requested resource could not be found. |
429 - Too Many Requests | You have exceeded the rate limit. |
500 - Internal Server Error | Something went wrong on our end. |
Error Response Format
When an error occurs, the API returns a JSON object with an error
field containing
a human-readable message:
{
"error": "Invalid API key"
}
Always implement proper error handling in your application to gracefully manage API errors and provide appropriate feedback to users.
Rate Limits
To ensure the stability and availability of the API for all users, rate limits are applied based on your API key.
If you exceed these limits, you'll receive a 429 Too Many Requests
response.
Default Limits
The default rate limits are:
- 100 requests per minute
- 5,000 requests per day
Headers
Each response includes headers that provide information about your current rate limit status:
Header | Description |
---|---|
X-RateLimit-Limit | The maximum number of requests allowed in the current time window |
X-RateLimit-Remaining | The number of requests remaining in the current time window |
X-RateLimit-Reset | The time when the current rate limit window resets (Unix timestamp) |
Implement exponential backoff when you receive a 429 response. Wait for the duration specified in the
Retry-After
header before making additional requests.
Users
The Users endpoints allow you to manage user verification between Discord and Roblox platforms.
List All Users
Returns a paginated list of all verified users.
Query Parameters
Parameter | Type | Required | Description |
---|---|---|---|
page |
integer | Optional | Page number (default: 1) |
limit |
integer | Optional | Number of results per page (default: 100, max: 500) |
sort |
string | Optional | Field to sort by (default: verified_at) |
order |
string | Optional | Sort order: "asc" or "desc" (default: desc) |
Response
{
"users": [
{
"id": 123,
"roblox_id": "12345678",
"roblox_username": "RobloxUser123",
"discord_id": "123456789012345678",
"discord_username": "DiscordUser#1234",
"verified_at": "2025-04-01T12:34:56.789Z",
"metadata": { "role": "member" }
},
// More users...
],
"pagination": {
"total": 250,
"page": 1,
"limit": 100,
"pages": 3,
"hasNext": true,
"hasPrev": false
}
}
Get a Specific User
Returns details for a specific user by their ID.
Path Parameters
Parameter | Type | Required | Description |
---|---|---|---|
id |
integer | Required | The unique ID of the user |
Response
{
"user": {
"id": 123,
"roblox_id": "12345678",
"roblox_username": "RobloxUser123",
"discord_id": "123456789012345678",
"discord_username": "DiscordUser#1234",
"verified_at": "2025-04-01T12:34:56.789Z",
"metadata": { "role": "member" }
}
}
Delete a User
Deletes a user by their ID.
Path Parameters
Parameter | Type | Required | Description |
---|---|---|---|
id |
integer | Required | The unique ID of the user to delete |
Response
{
"success": true,
"message": "User deleted",
"changes": 1
}
Verification
The Verification endpoints allow you to create and verify connections between Discord and Roblox accounts.
Verify a User
Creates a new verified user connecting a Discord account with a Roblox account.
Request Body
Parameter | Type | Required | Description |
---|---|---|---|
robloxId |
string | Required | The Roblox ID of the user |
robloxUsername |
string | Optional | The Roblox username of the user |
discordId |
string | Optional | The Discord ID of the user |
discordUsername |
string | Optional | The Discord username of the user |
metadata |
object | Optional | Additional metadata to store with the verification |
{
"robloxId": "12345678",
"robloxUsername": "RobloxUser123",
"discordId": "123456789012345678",
"discordUsername": "DiscordUser#1234",
"metadata": {
"role": "member",
"group": "developers",
"notes": "Joined through website referral"
}
}
Response
{
"success": true,
"message": "Verification successful",
"userId": 123
}
Check Verification Status
Checks if a user is verified by their Roblox ID or Discord ID.
Query Parameters
Parameter | Type | Required | Description |
---|---|---|---|
robloxId |
string | Optional* | The Roblox ID to check |
discordId |
string | Optional* | The Discord ID to check |
* At least one of robloxId or discordId must be provided
Response
{
"verified": true,
"user": {
"id": 123,
"robloxId": "12345678",
"robloxUsername": "RobloxUser123",
"discordId": "123456789012345678",
"discordUsername": "DiscordUser#1234",
"verifiedAt": "2025-04-01T12:34:56.789Z",
"metadata": {
"role": "member"
}
}
}
Statistics
The Statistics endpoints provide insights into the verification system's usage and trends.
Get System Statistics
Returns key statistics about the verification system.
Response
{
"totalUsers": 1257,
"last24Hours": 42,
"last7Days": 189,
"last30Days": 563,
"verificationsByDay": [
{
"date": "2025-04-05",
"count": 23
},
{
"date": "2025-04-06",
"count": 31
},
{
"date": "2025-04-07",
"count": 27
},
{
"date": "2025-04-08",
"count": 19
},
{
"date": "2025-04-09",
"count": 35
},
{
"date": "2025-04-10",
"count": 29
},
{
"date": "2025-04-11",
"count": 25
}
],
"generatedAt": "2025-04-11T15:23:47.123Z"
}
The statistics endpoints only provide aggregated, anonymized data and do not expose any personally identifiable information about users.
Statistics Fields
Field | Type | Description |
---|---|---|
totalUsers |
integer | Total number of verified users in the system |
last24Hours |
integer | Number of users verified in the last 24 hours |
last7Days |
integer | Number of users verified in the last 7 days |
last30Days |
integer | Number of users verified in the last 30 days |
verificationsByDay |
array | Daily verification counts for the last 7 days |
generatedAt |
string | Timestamp when the statistics were generated |
Audit Logs
The Audit Logs feature allows you to track all important actions performed within the system for security and compliance purposes.
Audit log endpoints are only accessible with administrator API keys. Regular API keys do not have permission to view audit logs.
Get Audit Logs
Returns a paginated list of audit log entries.
Query Parameters
Parameter | Type | Required | Description |
---|---|---|---|
page |
integer | Optional | Page number (default: 1) |
limit |
integer | Optional | Number of results per page (default: 100, max: 500) |
event_type |
string | Optional | Filter by event type (e.g., "user_verified", "user_deleted") |
user_id |
integer | Optional | Filter by user ID |
from_date |
string | Optional | Filter events after this date (ISO 8601 format) |
to_date |
string | Optional | Filter events before this date (ISO 8601 format) |
Response
{
"logs": [
{
"id": 456,
"event_type": "user_verified",
"user_id": 123,
"roblox_id": "12345678",
"discord_id": "123456789012345678",
"details": "{"robloxUsername":"RobloxUser123","discordUsername":"DiscordUser#1234"}",
"ip_address": "192.168.1.1",
"created_at": "2025-04-11T14:32:17.123Z"
},
{
"id": 455,
"event_type": "user_deleted",
"user_id": 122,
"roblox_id": "87654321",
"discord_id": "876543210987654321",
"details": "{"robloxUsername":"DeletedUser","discordUsername":"FormerUser#5678"}",
"ip_address": "192.168.1.2",
"created_at": "2025-04-11T13:45:21.456Z"
},
// More logs...
],
"pagination": {
"total": 1250,
"page": 1,
"limit": 100,
"pages": 13,
"hasNext": true,
"hasPrev": false
}
}
Audit Event Types
The system logs various event types to track different actions in the system:
Event Type | Description |
---|---|
user_verified |
A new user verification was created |
user_deleted |
A user was deleted from the system |
user_updated |
A user's information was updated |
login_attempt |
An admin login attempt (successful or failed) |
api_key_created |
A new API key was generated |
api_key_revoked |
An API key was revoked |
settings_changed |
System settings were modified |
Data Retention
Audit logs are kept for a period of 365 days, after which they are automatically purged from the system. If you need to retain audit logs for longer periods, we recommend implementing a process to export and archive these logs on a regular basis.
Discord Integration
Learn how to integrate the Technified API with your Discord bot for seamless verification between Discord and Roblox.
This section is currently being developed and will be available soon.
Roblox Integration
Learn how to integrate the Technified API with your Roblox game to verify users and sync roles.
This section is currently being developed and will be available soon.
Webhooks
Learn how to set up webhooks to receive real-time notifications for verification events.
This section is currently being developed and will be available soon.
Quick Start Guides
Learn from a quick starter guide how to use Technified.
This section is currently being developed and will be available soon.
Example Projects
Learn from Example Projects how to use Technified.
This section is currently being developed and will be available soon.