Skip to content
Fluxer API

Instance

The Instance resource describes how one Fluxer deployment is set up. It publishes the discovery document, the client geolocation lookup, and the served OpenAPI document, and it owns the limit key registry that every other page cites.

Get instance discovery is the entry point of the API. A client that knows only a Fluxer origin reads /.well-known/fluxer first, and that one unauthenticated response has every field of the instance discovery object. Those values include the API base URLs, the main Gateway WebSocket URL, and the Media Proxy base URL, and they override the endpoint path defaults a deployment would otherwise serve from its canonical public origin.

Every route here is unauthenticated. A credential changes no response body. One that resolves to an account moves the rate limit bucket from the client IP address onto that account.

Each of the three routes answers with Access-Control-Allow-Origin: *, replaced by the request Origin when the deployment-wide cross-origin policy allows that origin. The Admin Instance API defines the operator side of the same configuration.

The discovery document is the complete public description of one deployment. Every field is always present.

FieldTypeDescription
api_code_version1integerThe version of the API server code this deployment runs
endpointsinstance endpoints objectPublic service endpoints for this deployment
captchacaptcha configuration objectPublic CAPTCHA configuration
featuresinstance features objectPublic deployment feature state
gifGIF provider objectThe active GIF provider and its attribution requirement
ssoSSO status objectPublic single sign-on state
registrationregistration policy objectPublic registration policy
communitycommunity policy objectCommunity defaults and direct message policy
servicesservice availability objectResolved third-party integration availability
limitslimit configuration objectOrdered limit rules and the trait names the deployment declares
pushpush configuration objectPublic Web Push identity
app_publicpublic application configuration objectPublic client configuration

1 The value is a plain integer that increases when the API introduces a change a client is expected to notice, and the current value is 1

Each value is an absolute URL supplied by the operator. A value can be a bare origin or an origin with a path prefix, because a deployment can serve several roles from one canonical public origin. A client accepts two endpoints that share an origin and MUST NOT infer a separate host, scheme, or port for any of them.

FieldTypeDescription
api1stringBase URL for authenticated API requests
api_client1stringBase URL for client API requests
api_publicstringBase URL for public API requests
gateway2stringThe main Gateway WebSocket URL
mediastringMedia Proxy base URL, also used as the attachment upload relay base
static_cdn3stringStatic asset base URL
marketingstringMarketing site base URL
adminstringAdmin application base URL
invitestringInvite link base URL
giftstringGift link base URL
webappstringWeb application base URL

1 Both fields are the same configured client API endpoint, which the first-party web application reads. api_public is the separately configured public API endpoint, which a bot, a library, or any other third-party client reads. A deployment can point the two at one origin, and the instance Fluxer hosts does not

2 The value is the configured Gateway endpoint and its scheme is ws or wss as the operator configured it

3 A deployment that configures a separate static asset domain derives that value over https on the configured domain and without the port the other endpoints have

Every value is the exact origin the deployment advertises, including its scheme and any explicit port, and a deliberately plain HTTP deployment publishes http and ws values here.

The operator configures one canonical public origin with an exact http or https scheme, a host, and an optional explicit port. The web application is served at that origin itself, and the other endpoints default to a path under it:

EndpointDefault path
HTTP API/api
Media Proxy/media
Admin application/admin
Marketing site/marketing
Invite links/invite
Gift links/gift
Gateway/gateway

The Gateway scheme is ws or wss. A port that equals the default for its scheme is omitted.

A deployment can configure a separate static asset domain, invite domain, and gift domain, and it can replace any single endpoint with an exact override.

{
"api": "https://api.example.com",
"api_client": "https://api.example.com",
"api_public": "https://public.example.com",
"gateway": "wss://gateway.example.com",
"media": "https://media.example.com",
"static_cdn": "https://cdn.example.com",
"marketing": "https://example.com",
"admin": "https://admin.example.com",
"invite": "https://example.com/invite",
"gift": "https://example.com/gift",
"webapp": "https://app.example.com"
}

Which CAPTCHA provider this deployment uses, and the site keys a client needs to render its challenge.

FieldTypeDescription
provider1stringThe selected CAPTCHA provider
hcaptcha_site_key2?stringThe configured hCaptcha site key, or null when none is configured
turnstile_site_key2?stringThe configured Turnstile site key, or null when none is configured

1 The value is none when the configured provider’s site key or secret key is missing

2 Only the key that matches provider is non-null, so both are null while provider is none

ValueDescription
noneThe deployment requires no CAPTCHA
hcaptchahCaptcha challenges gate the operations that demand one
turnstileCloudflare Turnstile challenges gate the operations that demand one

The complete challenge handshake, including the X-Captcha-Token and X-Captcha-Type request headers, is defined in CAPTCHA handling.

Deployment-wide switches a client reads before it offers a feature, plus whether the deployment calls itself self-hosted.

FieldTypeDescription
voice_enabledbooleanWhether voice and video calling is enabled
stripe_enabledbooleanWhether Stripe billing is enabled
self_hostedbooleanWhether this deployment identifies itself as self-hosted
presigned_attachment_uploadsbooleanWhether a client can request presigned attachment upload URLs
emails_enabled1booleanWhether the deployment sends email

1 The value is true only when email is switched on and the transport is completely configured

A deployment that reports emails_enabled as false sends no verification, password recovery, or IP authorisation message, and the flows that depend on one are unusable there. Deployment availability states which routes a self-hosted deployment does not serve at all.

The GIF provider this deployment has bound, and whether a client shows its attribution mark.

FieldTypeDescription
providerstringStable machine name of the active GIF provider
display_namestringHuman-readable provider name a client shows
attribution_required1booleanWhether a client shows the provider attribution

1 A client that renders GIF results displays the provider’s attribution mark alongside them when this value is true

The fields describe the provider a deployment has bound even when service availability reports gif_enabled as false. A client reads gif_enabled to decide whether to offer the picker at all. A deployment that has bound no GIF provider still publishes the stock values klipy, Klipy, and false.

Who can register an account on this deployment.

FieldTypeDescription
modestringThe registration mode
admin_registration_urls_enabled1booleanWhether an administrator-issued registration URL code is accepted

1 When true, Register an account accepts registration_url_code, a valid code admits registration even while mode is closed, and the code’s own approval requirement replaces the one the mode would impose

ValueDescription
openAnyone can register and receives a session immediately
approvalRegistration succeeds but the account waits for administrator approval before it can sign in
closedPublic registration is refused

Whether this deployment runs as one community, and whether direct messages exist on it at all.

FieldTypeDescription
single_communitybooleanWhether this deployment runs as one community that every account joins
single_community_guild_id1?snowflakeThe stock community guild ID, or null
direct_messages_disabledbooleanWhether direct messages and friend requests are disabled for the whole deployment

1 The identifier is published only while single_community is true and a stock community has been chosen

Each field reports whether one optional integration is available on this deployment.

FieldTypeDescription
gif_enabledbooleanWhether the GIF picker is available
youtube_enabledbooleanWhether YouTube link enrichment is available
bluesky_enabledbooleanWhether Bluesky connections are available

This deployment’s public Web Push identity.

FieldTypeDescription
public_vapid_key1?stringThe deployment’s Web Push VAPID public key, or null

1 Null when the deployment has configured no Web Push identity

The ordered rules a client evaluates to work out the limits that apply to an account or a guild.

FieldTypeDescription
versionintegerThe wire format version, always 2
traitDefinitions1array[string]The trait names this deployment declares
rulesarray[limit rule object]The rules to evaluate
defaultsHash2stringA hash of the release’s built-in default limit values

1 A stock hosted configuration publishes the single name premium, which is computed from the account’s premium state

2 The value is computed from the release’s default limit values alone, so an operator editing a rule leaves it unchanged. It changes when a release changes the defaults, which invalidates a resolution a client cached against the older ones

Each rule publishes only the keys whose values differ from the release defaults. The defaults themselves are not published in this document, so a client MUST hold its own copy of them. A client MUST also rebuild every rule into a full limit map before it resolves anything, taking the default value of every limit key and overlaying that rule’s overrides on it.

A client starts from the default value of every key. It evaluates the rules from least specific to most specific, where specificity is the total number of trait and guild feature names in a rule’s filters. Two rules of equal specificity keep their published order. A rule matches when every trait it names is present in the evaluation context and every guild feature it names is present.

A rule that names no trait and no guild feature replaces the current value for each key it has. A rule that names at least one raises the current value to its own value when that is higher. Because a rebuilt rule has every key, an unfiltered rule returns each key it did not override to the default. A matching filtered rule raises each key it did not override to at least the default.

Two evaluation contexts exist. A user evaluation applies only keys whose scope is user or is both. A guild evaluation applies every key whose scope is both. It applies a user-scoped key only when the rule has no guild feature filter. It applies a guild-scoped key when the rule has a guild feature filter, or when the rule has no trait filter at all. The limit key registry states the scope of each key.

traitDefinitions names the traits the deployment advertises. Nothing validates a rule’s traits filter against it, so a rule can filter on a name the collection omits. A self-hosted deployment whose premium mode grants every account the stock limits publishes an empty collection and has no rule that filters on premium.

One rule of the limit configuration, with the filters that select it and the values it sets.

FieldTypeDescription
idstringThe stable rule identifier
filters?limit filters objectThe traits and guild features that select the rule, omitted when the rule always matches
overrides1map[string, integer]Integer values keyed by limit key

1 An entry whose value is negative or is not a finite number is ignored when the rule is applied

{
"id": "premium",
"filters": {"traits": ["premium"]},
"overrides": {
"max_message_length": 4000,
"max_guild_emojis": 250
}
}

The traits and guild features a limit rule requires before it matches.

FieldTypeDescription
traits?array[string]Trait names that must all be present for the rule to match
guildFeatures?array[string]Guild feature names that must all be present for the rule to match

An empty or omitted collection imposes no condition. A rule whose filters object has neither collection always matches, and it replaces each key’s current value exactly as a rule that omits filters does.

Each key names one limit. A key whose name begins with feature_ is a feature gate whose value is 0 when the feature is unavailable and 1 when it is available. Every other key’s value is a bound in the unit named by its description.

ValueDescription
avatar_max_sizeMaximum file size for avatar uploads in bytes, in user scope
emoji_max_sizeMaximum file size for emoji uploads in bytes, in guild scope
feature_animated_avatarAllow animated avatar uploads, in user scope
feature_animated_bannerAllow animated banner uploads, in user scope
feature_custom_discriminatorAllow custom discriminator selection, in user scope
feature_custom_notification_soundsAllow custom notification sounds, in user scope
feature_early_accessAccess to beta features, in user scope
feature_global_expressionsUse expressions across all guilds, in user scope
feature_higher_video_qualityAccess to higher video streaming quality, in user scope
feature_per_guild_profilesDifferent profile per guild, in user scope
feature_voice_entrance_soundsPlay a sound when joining voice, in user scope
max_attachment_file_sizeMaximum size of each attachment file in bytes, in user and guild scope
max_attachments_per_messageMaximum number of file attachments per message, in user and guild scope
max_bio_lengthMaximum characters in a user biography, in user scope
max_bookmarksMaximum bookmarked messages, in user scope
max_channels_per_categoryMaximum channels per category, in guild scope
max_custom_backgroundsMaximum custom profile backgrounds, in user scope
max_embeds_per_messageMaximum number of embeds per message, in user and guild scope
max_favorite_meme_tagsMaximum meme tags to track, in user scope
max_favorite_memesMaximum favourited memes, in user scope
max_group_dm_recipientsMaximum members per group direct message, in user scope
max_group_dms_per_userMaximum group direct messages a user can own, in user scope
max_guild_channelsMaximum channels per guild, in guild scope
max_guild_emojisMaximum total emojis per guild, in guild scope
max_guild_emojis_animated1Compatibility alias for older clients, in guild scope
max_guild_emojis_animated_more1Compatibility alias for older clients, in guild scope
max_guild_emojis_static1Compatibility alias for older clients, in guild scope
max_guild_emojis_static_more1Compatibility alias for older clients, in guild scope
max_guild_invitesMaximum active invites per guild, in guild scope
max_guild_membersMaximum members per guild, in guild scope
max_guild_rolesMaximum roles per guild, in guild scope
max_guild_stickersMaximum stickers per guild, in guild scope
max_guild_stickers_more2Compatibility alias for older clients, in guild scope
max_guildsMaximum number of guilds a user can join, in user scope
max_message_lengthMaximum number of characters per message, in user and guild scope
max_private_channels_per_userMaximum direct message channels per user, in user scope
max_reactions_per_messageMaximum distinct reactions per message, in guild scope
max_relationshipsMaximum friend and blocked relationships, in user scope
max_users_per_message_reactionMaximum users who can use the same reaction on a message, in guild scope
max_voice_message_durationMaximum voice message duration in seconds, in user and guild scope
max_webhooks_per_channelMaximum webhooks per channel, in guild scope
max_webhooks_per_guildMaximum webhooks per guild, in guild scope
sticker_max_sizeMaximum file size for sticker uploads in bytes, in guild scope

1 Emoji limits are enforced as one shared total against max_guild_emojis, and the four aliases exist only so an older client reads a plausible value

2 Sticker limits are enforced as one shared total against max_guild_stickers

Where a rule sets max_guild_emojis, max_guild_stickers, or one of the five compatibility aliases, it republishes that key in its own overrides even when the value matches the default.

Branding, setup state, legal documents, and registration fields a client reads before an account signs in.

FieldTypeDescription
brandingpublic branding objectPublic instance identity
setuppublic setup state objectInitial configuration state
legalpublic legal configuration objectRegistration legal document URLs
registrationpublic registration fields objectRegistration field collection policy

The instance identity a client renders: its name, its images, and its theme colour. The image URLs customise browser metadata, install metadata, and link previews.

FieldTypeDescription
product_namestringThe configured instance name a client displays
icon_url?stringFull application icon URL, or null
symbol_url?stringCompact application symbol URL, or null
logo_url?stringApplication logo URL, or null
wordmark_url?stringApplication wordmark URL, or null
favicon_url?stringBrowser favicon URL, or null
theme_color?stringBrowser theme colour, or null

Whether the deployment has finished its initial configuration, and where an operator goes to continue it.

FieldTypeDescription
configuredbooleanWhether initial deployment configuration is complete
admin_url1?stringThe admin application URL used to continue setup, or null

1 The value is the deployment’s configured admin endpoint, and it is null when no admin endpoint is configured

Two public URLs a client links from its registration form.

FieldTypeDescription
terms_url?stringPublic terms of service URL, or null
privacy_url?stringPublic privacy policy URL, or null

Which extra fields public registration collects.

FieldTypeDescription
collect_date_of_birthbooleanWhether public registration collects and validates a date of birth

The approximate location Fluxer resolved for the request, together with the regions where mature content is gated behind an age check or is unavailable.

FieldTypeDescription
countryCode1 2?stringThe detected ISO 3166-1 alpha-2 country code, or null
regionCode1 2?stringThe detected ISO 3166-2 subdivision code within the country, or null
latitude1 3?stringThe approximate latitude, or null
longitude1 3?stringThe approximate longitude, or null
ageRestrictedGeosarray[geo entry object]Locations where mature content requires an age check
ageBlockedGeosarray[geo entry object]Locations where mature content is unavailable

1 Every detected field is null when the deployment has configured no geolocation database, when the client address is not a valid IP address, when the database holds no record for it, or when the lookup fails. A record that resolves can still omit the subdivision code or the coordinate pair

2 The value is upper case

3 The value is a decimal string

The two geo collections are fixed by the release, so they are identical in every response. A client resolves its own country and subdivision from the detected fields and then selects the matching entry itself.

{
"countryCode": "GB",
"regionCode": "ENG",
"latitude": "51.5074",
"longitude": "-0.1278",
"ageRestrictedGeos": [{"countryCode": "US", "regionCode": "TX"}],
"ageBlockedGeos": []
}

A geo entry names a whole country when its regionCode is null and names one subdivision otherwise.

FieldTypeDescription
countryCodestringThe ISO 3166-1 alpha-2 country code
regionCode?stringThe ISO 3166-2 subdivision code within the country, or null when the entry covers the whole country
GET/.well-known/fluxerUnauthenticated

Returns the instance discovery object describing this deployment.

The path has no /v1 prefix.

StatusBodyCondition
200instance discovery objectThe discovery document was returned

60 requests per minute for each authenticated user, or for each client IP address when the request has no credential, on the instance:info bucket. Get OpenAPI document draws on the same bucket, so the two operations share one allowance.

GET/v1/ipUnauthenticated

Returns the geolocation object for the request’s client address.

The client address is the first hop of the deployment’s configured client IP header, which defaults to x-forwarded-for. A lookup that resolves nothing still returns 200 with countryCode, regionCode, latitude, and longitude all null. A client MUST treat an all-null result as an unknown location.

A resolved result is cached for ten minutes against the address. An IPv4 address is cached individually and an IPv6 address is cached by its /64.

StatusBodyCondition
200geolocation objectThe location was resolved, wholly, partly, or not at all

30 requests per minute for each authenticated user, or for each client IP address when the request has no credential, on the ip:geo_lookup bucket.

GET/v1/openapi.jsonUnauthenticated

Returns the deployment’s OpenAPI 3.1 document as JSON with Content-Type: application/json; charset=utf-8.

The document has no ETag. It declares one server entry, the deployment’s api_client value from the instance endpoints object followed by /v1. Every path key is relative to that entry. The server entry is the only part that varies by deployment, and the rest is fixed when the document is generated.

StatusBodyCondition
200OpenAPI 3.1 documentThe document was returned

60 requests per minute for each authenticated user, or for each client IP address when the request has no credential, on the instance:info bucket. The allowance is shared with Get instance discovery.