Resources Overview
Fluxer’s API is built around several core resources that represent the building blocks of the platform. This section documents the structure and relationships between these resources.Core Resources
User Resources
- Users - User accounts, profiles, and authentication
- Relationships - Friend connections and blocks
- Settings - User preferences and configuration
Guild Resources
- Guilds - Server communities and their settings
- Members - Guild membership and roles
- Roles - Permission sets and hierarchy
- Emojis & Stickers - Custom expressions
Channel Resources
- Channels - Text, voice, and category channels
- Messages - Message content and metadata
- Invites - Invitation codes and links
Integration Resources
- Webhooks - Automated message posting
- OAuth2 - Third-party authorization
- Applications - Bot and OAuth2 apps
Premium Resources
- Premium - Premium subscriptions and features
- Billing - Payments and transactions
- Gift Codes - Premium gifts
Resource Identifiers
All resources use Snowflake IDs - unique 64-bit integers that encode timestamp information:Common Patterns
Timestamps
All timestamps are ISO 8601 formatted strings:Nullable Fields
Fields may benull or omitted entirely depending on context. Check individual resource documentation for specifics.
Version Fields
Most resources include aversion field for optimistic concurrency control:
Asset URLs
Resources with images (avatars, icons, banners) store hashes. Use the CDN endpoints to construct full URLs:Relationships
Next Steps
Explore the individual resource pages to learn about:- Field definitions and types
- Available endpoints
- Example responses
- Common use cases