Skip to content

Getting Started

Create your bot, get a token, and send your first API request.

1

Create a Bot Application #

Bots are created through the Argon Developer Console.

  1. Go to console.argon.gl and sign in with your Argon account.
  2. Select your team (or create one).
  3. Navigate to Apps and click Create Application.
  4. Choose the Bot App tab.
  5. Enter an App Name (e.g., "My Music Bot") and a Bot Username.

Bot usernames must end with bot (e.g., music_bot). The system will validate this.

2

Get Your Bot Token #

After creating the bot, you'll be taken to the App Details page. Find the Authentication & Keys section.

Your bot token looks like this:

Bot Token:
a1b2c3d4e5f6...:aBC-_DeF_GhIjKlMnOpQr...

Format: {hex}:{base64url} — the first part identifies the bot, the second is the secret.

Keep your token secret

Never commit tokens to source control or share them publicly. If compromised, regenerate immediately from the Developer Console.

3

Authenticate Your Requests #

Include your token in the Authorization header on every request:

Authorization: Bot YOUR_TOKEN_HERE

All API endpoints require this header. Requests without it receive a 401 Unauthorized response.

4

API Structure #

The Bot API is organized into interfaces, each independently versioned. Every endpoint follows this pattern:

Base URL:
https://gateway.argon.zone/{Interface}/v{Version}/{Method}

Example:
https://gateway.argon.zone/IBotSelf/v1/GetMe
Segment Description
InterfaceThe API group name, e.g. IBotSelf, IMessages
VersionInterface version, starting at 1
MethodThe specific endpoint, e.g. GetMe, Send
5

Your First Request #

Verify your bot is authenticated by calling GetMe:

Request
$ curl -H "Authorization: Bot YOUR_TOKEN" \
     https://gateway.argon.zone/IBotSelf/v1/GetMe
Response
{
  "botId": "550e8400-e29b-41d4-a716-446655440000",
  "userId": "6ba7b810-9dad-11d1-80b4-00c04fd430c8",
  "username": "music_bot",
  "displayName": "Music Bot",
  "avatarUrl": null,
  "email": "550e8400...+music_bot@noreply.argon.gl"
}

If you receive a 200 OK with your bot info, you're all set.

Rate Limits #

Each interface has its own sliding window rate limit. When you hit the limit, the API returns 429 Too Many Requests with a Retry-After header indicating how many seconds to wait.

Interface Limit
IBotSelf 15 requests / minute
ICalls 20 requests / minute
IChannels 60 requests / minute
ICommands 60 requests / minute
IEvents 5 requests / minute
IInteractions 120 requests / minute
IMembers 30 requests / minute
IMessages 120 requests / minute
ISpaces 30 requests / minute
IVoice 20 requests / minute
IVoiceEgress 10 requests / minute

These are default limits. Verified bots receive higher rate limits automatically. If you need a further increase, contact support.

Error Responses #

All errors follow this format:

{
  "code": "not_found",
  "message": "The requested resource was not found."
}
HTTP Status Meaning
400Bad request — invalid parameters or body
401Missing or invalid bot token
403Bot lacks permission (e.g., not a member of the space)
404Resource not found
429Rate limited — check Retry-After header

Next Steps