Emoji and Stickers

Copy an emoji into a community by its source ID, using Fluxer's server-side copy

Source metadata is preserved. Fluxer enforces source copying restrictions

Upload one community emoji and return its metadata

Inputs are copied when execution starts. No image URL is fetched automatically. Fluxer checks image format, dimensions, permissions and capacity. A write with an unknown outcome is not replayed

Upload 1–50 community emojis in one batch and return separate successes and failures

The input array is copied by index, then its entries are copied when execution starts. Some uploads can succeed while others fail. No rollback or automatic chunking is performed. Failures named by duplicate emoji names cannot be matched reliably to input positions. After an unknown outcome, fetch fresh remote data rather than blindly replaying the batch

Remove an emoji, succeeding with no value after HTTP 204

Retained metadata is invalidated. A missing target is an error, not proof of an earlier deletion. The purge option defaults to false. Setting it to true also queues irreversible media removal, subject to Fluxer's restrictions

Rename a community emoji without changing its image or fetching its old metadata first

Fetch a community's emoji list in Fluxer's order, without pagination

The list can change after the response and is not an ongoing completeness guarantee. An enabled metadata cache can retain results, but not image bytes or creator accounts

Fetch minimal emoji metadata by decimal ID, without requiring source-community membership

This read does not populate the cache

Fetch the public presentation of the community that owns a custom emoji with this decimal ID: Its ID, name, icon hash and badges

Fluxer answers when the source community is discoverable or the bot is a member of it. A private source community the bot is not in, an unavailable community or an unknown emoji fails with GuildOperationError whose apiError.code is unknownResource, without revealing which case applies. This read does not populate the cache, and the result does not update when the community changes

Look up cached emoji metadata using decimal guildId and id, without an HTTP request

The result is undefined when caching is disabled or the entry is absent, expired or invalidated by a conflicting change. A hit becomes more recently used without extending expiry. An invalid ID is misuse: The default API throws GuildOperationError with reason input and the native API dies with it. A closing or closed client has no cache, so the result is undefined

Copy a sticker into a community by its source ID, using Fluxer's server-side copy

Source metadata is preserved. Fluxer enforces source copying restrictions

Upload one community sticker and return its metadata

Inputs are copied when execution starts. No image URL is fetched automatically. Fluxer checks image format, dimensions, permissions and capacity. A write with an unknown outcome is not replayed

Upload 1–50 community stickers in one batch and return separate successes and failures

The input array is copied by index, then its entries are copied when execution starts. Some uploads can succeed while others fail. No rollback or automatic chunking is performed. Failures named by duplicate sticker names cannot be matched reliably to input positions. After an unknown outcome, fetch fresh remote data rather than blindly replaying the batch

Remove a sticker, succeeding with no value after HTTP 204

Retained metadata is invalidated. A missing target is an error, not proof of an earlier deletion. The purge option defaults to false. Setting it to true also queues irreversible media removal, subject to Fluxer's restrictions

Replace a sticker's name, description and tags without changing its image or fetching it first

A fetched sticker can be spread into input if its identity matches the target. Unknown fields fail locally. An empty or null description clears it, and [] clears tags. The namespace's write, failure and cancellation rules apply

Fetch a community's sticker list in Fluxer's order, without pagination

The list can change after the response and is not an ongoing completeness guarantee. An enabled metadata cache can retain results, but not image bytes or creator accounts

Fetch minimal sticker metadata by decimal ID, without requiring source-community membership

This read does not populate the cache

Fetch the public presentation of the community that owns a custom sticker with this decimal ID: Its ID, name, icon hash and badges

Fluxer answers when the source community is discoverable or the bot is a member of it. A private source community the bot is not in, an unavailable community or an unknown sticker fails with GuildOperationError whose apiError.code is unknownResource, without revealing which case applies. This read does not populate the cache, and the result does not update when the community changes

Look up cached sticker metadata using decimal guildId and id, without an HTTP request

The result is undefined when caching is disabled or the entry is absent, expired or invalidated by a conflicting change. A hit becomes more recently used without extending expiry. An invalid ID is misuse: The default API throws GuildOperationError with reason input and the native API dies with it. A closing or closed client has no cache, so the result is undefined