Glossary
Key terms and concepts used throughout the Argon Bot API.
Core Concepts
Authentication & Security
Authorization: Bot <token> header or as a path segment: /<token>/.... Never share your token publicly.SendMessages, ManageChannels, KickMembers. Permissions are granted via archetypes assigned to the bot.Real-time
GET /IEvents/v1/Stream connection and receive JSON events in real time. Supports automatic reconnection via Last-Event-ID.Members (member join/leave/update) and Presence (online status changes). Requested during bot verification.Data & IDs
IFiles/Upload returns one for a sticker, emoji or attachment file, which IExpressions/AddItem or IMessages/Send takes for 24 hours; IFiles/Get describes a file and gives its download URL.int64 (snowflake) identifying a message within a channel. In JavaScript, use BigInt since these values exceed Number.MAX_SAFE_INTEGER.int64 used for message deduplication. If the server receives a message with the same random ID from the same bot, it returns the existing message instead of creating a duplicate.new Date(argonMs + 1735689600000) where 1735689600000 is the Unix timestamp of the Argon Epoch.Stickers & Emoji
sticker or emoji) in a space, with a title and a slug unique in the space. A space holds up to 10.:name: used in text.[a-z0-9_] name, unique in the space. Creating a pack again with the slug of one the bot made returns that pack.IReactions/AddCustom by its itemId. It reads :name: and carries the item ID as customEmojiId. Any bot may use an emoji of the space the message is in; an emoji of another space takes a verified bot. See Reactions.IExpressions/List returns it; passed back as known, the packs are left out while it is still current. expressionsUpdate events carry the token before and after each change.Files
IFiles/Upload with a purpose — sticker, emoji or attachment — and taken by its fileId for 24 hours. A bot holds at most 100 unused uploads.AttachFiles to send. Messages list them as attachments — fileId, url, fileName, size, contentType, width, height. See Files & Attachments.attach://<part> points a file field at another part of the same request. Only a multipart body has parts: in JSON it is refused with invalid_request.API Versioning
v20260401). No contract hash — may be modified or removed.