Skip to main content

​
API Keys Management

API keys allow you to integrate Technified with external tools, scripts, and applications.
In Development: External integrations are currently in development. API keys can be created but have limited functionality at this time. Stay tuned for upcoming features!

​
What are API Keys?

API keys are authentication tokens that allow external applications to access Technified’s API on behalf of your server.

​
Use Cases

Custom Dashboards

Build your own analytics dashboard with staff activity data

Automation Scripts

Automate verification, role management, or activity tracking

Third-Party Tools

Integrate with existing moderation or management tools

Data Export

Export activity logs or verification data for analysis

​
Creating an API Key

1

Navigate to API Keys

Go to the Dashboard, select your server, and click Server Settings → API Keys
2

Click Create Key

Click the + Create Key button in the top right
3

Configure the Key

Fill in the following information:
  • Key Name: A descriptive name (e.g., “Analytics Dashboard”, “Automation Script”)
  • Scopes: Select which permissions this key should have
4

Generate and Copy

Click Generate and immediately copy the API key. This is the only time you’ll see it!
5

Store Securely

Save the key in a secure location (password manager, environment variables, etc.)
Save Your Key Immediately!API keys are only shown once during creation. If you lose a key, you’ll need to revoke it and create a new one. There’s no way to retrieve a lost key.

​
Managing API Keys

​
View Active Keys

All your active API keys are listed in the API Keys section. For each key, you can see:
  • Key Name: The name you assigned
  • Scopes: Which permissions it has
  • Created: When the key was created
  • Last Used: When it was last accessed (coming soon)

​
Revoke a Key

If a key is compromised, no longer needed, or you want to rotate keys:
1

Find the Key

Locate the key in your API Keys list
2

Click Revoke

Click the Revoke button next to the key
3

Confirm

Confirm the revocation. This action is immediate and irreversible.
Revoking a key immediately invalidates it. Any applications using that key will stop working instantly. Make sure to update your applications with a new key before revoking the old one if you need continuity.

​
Key Limits

  • Maximum Keys per Server: 3
  • Key Expiration: API keys do not expire automatically

​
Using API Keys

​
Authentication

Include your API key in the Authorization header of HTTP requests: 
curl -H "Authorization: Bearer technified_xxxxxxxxxxxxxx" \
     https://api.technified.xyz/v1/guilds/{guild_id}/staff

​
Security Best Practices

DON’T:
const API_KEY = "technified_abc123..."; // ❌ Hardcoded in source
DO:
const API_KEY = process.env.TECHNIFIED_API_KEY; // ✅ From environment
Always store API keys in environment variables or secret management systems, never in your source code.
For high-security applications:
  • Rotate keys every 90 days
  • Rotate immediately if a team member with API key leaves
  • Rotate if you suspect a key may have been exposed
Regularly review:
  • Which keys are active
  • When they were last used
  • What they’re being used for
  • Delete unused keys
When using API keys in scripts:
  • Don’t spam the API with rapid requests this may lead in Blacklist from our Service
  • Implement exponential backoff for retries
  • Cache responses when possible
  • Respect any rate limit headers

​
Troubleshooting

Possible causes:
  • Invalid API key
  • Key has been revoked
  • Key not included in request header
  • Incorrect header format
Solution:
  • Verify your key is correct
  • Check that it hasn’t been revoked in the dashboard
  • Ensure header format: Authorization: Bearer technified_xxx
  • Regenerate key if necessary
Possible causes:
  • Key doesn’t have the required scope
  • Trying to access a resource outside your server
  • Feature not yet available
Solution:
  • Check the key has the necessary scopes
  • Verify you’re accessing the correct guild_id
  • Review API documentation for scope requirements
Cause: You’ve reached the 3-key limit per serverSolution:
  • Revoke an unused key
  • Consolidate applications to use fewer keys
  • Consider which keys are actually needed
Solution: Unfortunately, lost keys cannot be recovered. You must:
  1. Revoke the lost key (if you remember which one it was)
  2. Create a new key
  3. Update your applications with the new key
This is by design for security—keys are never stored in plain text.

​
Coming Soon

Planned features for API keys:

Webhook Integration

Receive real-time events via webhooks

Usage Analytics

Track API key usage and request patterns

IP Whitelisting

Restrict keys to specific IP addresses

Key Expiration

Set automatic expiration dates for keys

Audit Logs

See exactly what each key has accessed

​
API Documentation

For complete API reference documentation, endpoints, and parameters:

API Reference (Coming Soon)

Full documentation for Technified’s REST API

​
Next Steps

Staff Tracking

Use API keys to access staff activity data

Best Practices

Security guidelines and recommendations

Troubleshooting

Solutions to common API issues

Command Permissions

Control access to bot commands
API keys are powerful tools. Keep them secure, grant minimal permissions, and rotate them regularly to maintain a secure integration.