Instance

Discover a deployment’s endpoints, available features, and limits, look up the client’s approximate location, download its OpenAPI document, or choose how members of a new deployment sign in.

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. 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 GET route 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.

Instance discovery object

The discovery document is the complete public description of one deployment. Every field without a ? is always present. This server never sends codename or age_policy, and domain_migration and endpoints.upload_relay are absent only from a server older than this version.

Structure

Field	Type	Description
codename?	string	The protocol generation the deployment speaks
api_code_version1	integer	The version of the API server code this deployment runs
endpoints	instance endpoints object	Public service endpoints for this deployment
captcha	captcha configuration object	Public CAPTCHA configuration
features	instance features object	Public deployment feature state
gif	GIF provider object	The active GIF provider and its attribution requirement
sso	SSO status object	Public single sign-on state
registration	registration policy object	Public registration policy
community	community policy object	Community defaults and direct message policy
services	service availability object	Resolved third-party integration availability
limits	limit configuration object	Ordered limit rules and the trait names the deployment declares
push	push configuration object	Public Web Push identity
app_public	public application configuration object	Public client configuration
age_policy?	age policy object	Regional age policy for the deployment
domain_migration?	domain migration object	Web domain migration switch and logged-out rollout

¹ 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

Instance endpoints object

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.

Structure

Field	Type	Description
api1	string	Base URL for authenticated API requests
api_client1	string	Base URL for client API requests
api_public	string	Base URL for public API requests
gateway2	string	The main Gateway WebSocket URL
media	string	Media Proxy base URL
upload_relay?	string	Attachment upload relay base URL
static_cdn3	string	Static asset base URL
marketing	string	Marketing site base URL
admin	string	Admin application base URL
invite	string	Invite link base URL
gift	string	Gift link base URL
webapp	string	Web application base URL
docs?	string	Documentation website base URL

¹ 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

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

³ When a deployment configures a separate static asset domain, the value is https:// followed by that domain, with no port

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:

Endpoint	Default 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.

Use a published endpoint exactly as published

A client MUST NOT upgrade a published http value to https, downgrade a published https value after a failure, discard a port, or assume a DNS suffix.

Example

{
  "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"
}

CAPTCHA configuration object

Whether this deployment asks for a CAPTCHA on gated operations.

Structure

Field	Type	Description
provider	string	The CAPTCHA provider in use

CAPTCHA providers

Value	Description
altcha	An ALTCHA proof-of-work challenge gates the operations that require one
none	The deployment requires no CAPTCHA

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

Instance features object

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

Structure

Field	Type	Description
voice_enabled	boolean	Whether voice and video calling is enabled
stripe_enabled2	boolean	Whether premium purchases through Stripe billing are available
premium_enabled3	boolean	Whether the deployment has a premium tier, so premium state, gifts and perks apply
stripe_serviceable4	boolean	Whether existing Stripe subscriptions can be managed, cancelled and billed
self_hosted	boolean	Whether this deployment identifies itself as self-hosted
presigned_attachment_uploads	boolean	Whether a client can request presigned attachment upload URLs
emails_enabled1	boolean	Whether the deployment sends email
phone_verification_enabled	boolean	Deprecated. Always false
account_identity5	string	How members sign in, one of the account identity modes
tag_style6	string	How usernames are tagged, one of the tag styles
desktop_modules_enabled?	boolean	Whether desktop clients may load downloadable modules
account_deletion_grace_period_hours?	integer	Hours between a deletion request and the permanent deletion of the account (1-8,760)
max_background_gateway_connections?	integer	Maximum Gateway connections a client may keep open for background accounts (0-64)

¹ The value is true only when email is switched on and the transport is completely configured. It is always false on a username deployment

² True only when billing is switched on, a Stripe secret key is set, at least one currency has both a monthly and a yearly price, and premium_enabled is true. It is computed on each request

³ Always true on a hosted deployment. A self-hosted deployment reports true only while its premium mode is mirror

⁴ On a hosted deployment, true while billing is switched on and a Stripe secret key is set. A self-hosted deployment reports true while a Stripe secret key is set and premium_enabled is true, even after billing is switched off

⁵ Always email on a hosted deployment. A client treats a missing value as email, which is what a deployment from before the field existed means

⁶ Always none on a username deployment. Always random on a hosted deployment and on an instance that existed before the field. A client treats a missing value as random

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.

Account identity modes

Value	Description
email	Members register and sign in with an email address
username	Members register and sign in with a username, and the deployment collects no email address

Tag styles

Value	Description
none	Usernames are unique and shown without a tag. Every account that is not a bot has the discriminator 0000
random	Every account gets a random tag. Tags are shown and can be changed

A username deployment answers its email routes with 400 EMAIL_UNAVAILABLE_ON_INSTANCE. Authentication and Email and password changes list them. Routes that exist only for username sign-in, such as recover an account, answer 400 USERNAME_SIGN_IN_ONLY on an email deployment.

GIF provider object

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

Structure

Field	Type	Description
provider	string	Stable machine name of the active GIF provider
display_name	string	Human-readable provider name a client shows
attribution_required1	boolean	Whether a client shows the provider attribution

¹ 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.

Registration policy object

Who can register an account on this deployment.

Structure

Field	Type	Description
mode	string	The registration mode
admin_registration_urls_enabled1	boolean	Whether an administrator-issued registration URL code is accepted

¹ 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 set

Registration modes

Value	Description
open	Anyone can register and receives a session immediately
approval	Registration succeeds but the account waits for administrator approval before it can sign in
closed	Public registration is refused

Community policy object

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

Structure

Field	Type	Description
single_community	boolean	Whether this deployment runs as one community that every account joins
single_community_guild_id1	?snowflake	The ID of the guild every account joins in single-community mode, or null
direct_messages_disabled	boolean	Whether direct messages and friend requests are disabled for the whole deployment
guild_create_access	boolean	Whether every account can create communities, or only admins and holders of the feature_guild_create limit

¹ The identifier is published only while single_community is true and the deployment has designated a community guild

Service availability object

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

Structure

Field	Type	Description
gif_enabled	boolean	Whether the GIF picker is available
youtube_enabled	boolean	Whether YouTube link enrichment is available
bluesky_enabled	boolean	Whether Bluesky connections are available

Push configuration object

This deployment’s public Web Push identity.

Structure

Field	Type	Description
public_vapid_key1	?string	The deployment’s Web Push VAPID public key, or null
delivery_mode?	string	How push notifications reach devices, one of direct, external_relay, or hybrid
event_resolution_path?	string	API path a client calls to resolve the payload of a push event
external_relay_url?	?string	URL of the external push relay, or null when there is none
relay_signing_key_hashes?	?array[string]	Hashes of the keys the external push relay signs with, or null

¹ Null when the deployment has configured no Web Push identity

Limit configuration object

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

Structure

Field	Type	Description
version	integer	The wire format version, always 2
traitDefinitions1	array[string]	The trait names this deployment declares
rules	array[limit rule object]	The rules to evaluate
defaultsHash2	string	A hash of the release’s built-in default limit values

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

² 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. Before it resolves anything, a client MUST also rebuild every rule into a full limit map, taking the default value of every limit key and overlaying that rule’s overrides on it.

The 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.

The evaluation contexts are listed below. A client reads the key’s scope and the rule’s filters to decide which keys an evaluation applies. The limit key registry states the scope of each key.

Scope	User evaluation	Guild evaluation
user	Applied	Applied only when the rule has no guild feature filter
guild	Not applied	Applied when the rule has a guild feature filter, or when the rule has no trait filter at all
both	Applied	Applied

The operation applies its own authoritative bound

The document lets a client present the correct bounds before it attempts an operation. A request that exceeds the resolved value still fails with the operation’s own documented error.

An unauthenticated reader resolves only the unfiltered outcome

The document publishes neither the requesting account’s traits nor any guild feature set. A client supplies the account’s traits and the guild’s feature names itself, from data it received while authenticated.

Nothing validates a rule’s traits filter against traitDefinitions, so a rule can filter on a name that collection omits. A self-hosted deployment whose premium mode is everyone publishes an empty collection and has no rule that filters on premium.

Limit rule object

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

Structure

Field	Type	Description
id	string	The stable rule identifier
filters?	limit filters object	The traits and guild features that select the rule, omitted when the rule always matches
overrides1	map[string, integer]	Integer values keyed by limit key

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

Example

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

Limit filters object

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

Structure

Field	Type	Description
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.

Limit keys

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.

Value	Description
avatar_max_size	Maximum file size for avatar uploads in bytes, effective up to 104857600, in user scope
emoji_max_size	Maximum file size for emoji uploads in bytes, effective up to 104857600, in guild scope
feature_animated_avatar	Allow animated avatar uploads, in user scope
feature_animated_banner	Allow animated banner uploads, in user scope
feature_custom_discriminator	Allow custom discriminator selection, in user scope. Ignored for people on an instance with the none tag style
feature_custom_notification_sounds	Allow custom notification sounds, in user scope
feature_early_access	Access to beta features, in user scope
feature_global_expressions	Use expressions across all guilds, in user scope
feature_guild_create	Create communities while the instance restricts community creation, in user scope
feature_higher_video_quality	Access to higher video streaming quality, in user scope
feature_per_guild_profiles	Different profile per guild, in user scope
feature_voice_entrance_sounds	Play a sound when joining voice, in user scope
max_attachment_file_size	Maximum size of each attachment file in bytes, in user and guild scope
max_attachments_per_message	Maximum number of file attachments per message, in user and guild scope
max_bio_length	Maximum characters in a user biography, in user scope. At most 320
max_bookmarks	Maximum bookmarked messages, in user scope
max_channels_per_category	Maximum channels per category, in guild scope
max_custom_backgrounds	Maximum custom profile backgrounds, in user scope
max_embeds_per_message	Maximum number of embeds per message, in user and guild scope
max_favorite_meme_tags	Maximum meme tags to track, in user scope
max_favorite_memes	Maximum favourited memes, in user scope
max_group_dm_recipients	Maximum members per group direct message, in user scope
max_group_dms_per_user	Maximum group direct messages a user can own, in user scope
max_guild_channels	Maximum channels per guild, in guild scope
max_guild_emojis	Maximum total emojis per guild, in guild scope
max_guild_emojis_animated1	Compatibility alias for older clients, in guild scope
max_guild_emojis_animated_more1	Compatibility alias for older clients, in guild scope
max_guild_emojis_static1	Compatibility alias for older clients, in guild scope
max_guild_emojis_static_more1	Compatibility alias for older clients, in guild scope
max_guild_invites	Maximum active invites per guild, in guild scope
max_guild_members	Maximum members per guild, in guild scope
max_guild_roles	Maximum roles per guild, in guild scope
max_guild_stickers	Maximum stickers per guild, in guild scope
max_guild_stickers_more2	Compatibility alias for older clients, in guild scope
max_guilds	Maximum number of guilds a user can join, in user scope
max_message_length	Maximum number of characters per message, in user and guild scope
max_private_channels_per_user	Maximum direct message channels per user, in user scope
max_reactions_per_message	Maximum distinct reactions per message, in guild scope
max_relationships	Maximum friend and blocked relationships, in user scope
max_screen_share_bitrate	Highest screen share video bitrate in bits per second, from 1000000 to 50000000, in user scope
max_users_per_message_reaction	Maximum users who can use the same reaction on a message, in guild scope
max_voice_message_duration	Maximum voice message duration in seconds, in user and guild scope
max_webhooks_per_channel	Maximum webhooks per channel, in guild scope
max_webhooks_per_guild	Maximum webhooks per guild, in guild scope
sticker_max_size	Maximum file size for sticker uploads in bytes, effective up to 104857600, in guild scope

¹ Emoji limits are enforced as one shared total against max_guild_emojis, and the aliases exist only for older clients. The default of each alias equals the max_guild_emojis default

² Sticker limits are enforced as one shared total against max_guild_stickers

No key sets a thread or forum limit. Thread lifecycle, Thread members, and Forum channel fields state those fixed bounds. max_guild_channels counts forum and media channels and counts no thread.

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

Public application configuration object

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

Structure

Field	Type	Description
branding	public branding object	Public instance identity
setup	public setup state object	Initial configuration state
legal	public legal configuration object	Legal and policy document URLs
registration	public registration fields object	Registration field collection policy

Public branding object

The instance identity a client renders: its name, its images, its theme colour, its status page links, and the name of its premium tier. The image URLs customise browser metadata, install metadata, and link previews.

Structure

Field	Type	Description
product_name	string	The configured instance name a client displays
icon_url	?string	Full application icon URL, or null
symbol_url	?string	Compact application symbol URL, or null
logo_url	?string	Application logo URL, or null
wordmark_url	?string	Application wordmark URL, or null
favicon_url	?string	Browser favicon URL, or null
theme_color	?string	Brand and browser theme colour as lowercase #rrggbb, or null
status_page_url	?string	Public status page URL, or null
status_page_incident_history_url	?string	Status page incident history URL, or null
premium_product_name	string	Name of the premium tier a client displays. A self-hosted deployment reports Premium until the operator sets a name
premium_info_url	?string	Absolute URL of a page describing the premium tier, or null

Public setup state object

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

Structure

Field	Type	Description
configured	boolean	Whether initial deployment configuration is complete
admin_url1	?string	The admin application URL used to continue setup, or null
account_identity_locked?	boolean	Whether the sign-in method can no longer change, sent only while a self-hosted deployment is not configured

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

account_identity_locked is true once the first account exists, and on a deployment stored as already in use. Set the setup sign-in method returns 409 there.

Public legal configuration object

The public document URLs a client links from its registration form and its report flows.

Structure

Field	Type	Description
terms_url	?string	Public terms of service URL, or null
privacy_url	?string	Public privacy policy URL, or null
guidelines_url1	?string	Public community guidelines URL, or null

¹ The URL the operator set. A report flow and the account enforcement emails link it. When it is null, a hosted instance links its own guidelines page, and a self-hosted instance hides every guidelines link

Public registration fields object

Which extra fields public registration collects.

Structure

Field	Type	Description
collect_date_of_birth	boolean	Whether public registration collects and validates a date of birth

Domain migration object

The public part of the instance domain migration configuration. The official web client reads it before sign-in to decide whether its legacy origin forwards to the new one. Every instance publishes it, and only the official web client acts on it.

Structure

Field	Type	Description
enabled	boolean	Whether the migration runs at all
anonymous_rollout_basis_points	integer	Share of logged-out devices moved to the new origin, in basis points (0-10000)
rollout_salt	string	Salt of the sampling hash, shared by accounts and devices
standalone_forwarding	boolean	Whether installed desktop web apps forward to the new origin once their data has moved

enabled is the instance-wide switch. While it is false, no client starts a migration and a client that already migrated stops forwarding from the legacy origin. No passkey update opens, and the passkey bridge keeps working for people already on a new origin.

A logged-out device draws its own random ID once and keeps it. The device moves when its bucket over that ID and rollout_salt falls below anonymous_rollout_basis_points. Signed-in accounts use the domain migration assignment instead.

While standalone_forwarding is false, an installed desktop web app moves its data and stays on the legacy origin. Browser tabs forward either way.

Age policy object

The regions where the deployment gates access behind an age check or blocks it.

Structure

Field	Type	Description
geos	array[age policy region object]	Regions with an age policy

Age policy region object

Structure

Field	Type	Description
country_code	string	The ISO 3166-1 alpha-2 country code
region_code	?string	The ISO 3166-2 subdivision code, or null when the entry covers the whole country
action	string	restrict to require an age check, or block to refuse access
card_verification_available	boolean	Whether card age verification is available in the region

Geolocation object

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

Structure

Field	Type	Description
countryCode1 2	?string	The detected ISO 3166-1 alpha-2 country code, or null
regionCode1 2	?string	The detected ISO 3166-2 subdivision code within the country, or null
latitude1 3	?string	The approximate latitude, or null
longitude1 3	?string	The approximate longitude, or null
ageRestrictedGeos	array[geo entry object]	Locations where mature content requires an age check
ageBlockedGeos	array[geo entry object]	Locations where mature content is unavailable

¹ All detected fields are null when the location is unknown. A known location can still omit the subdivision code or coordinates

² The value is upper case

³ The value is a decimal string

The 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.

Example

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

Geo entry object

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

Structure

Field	Type	Description
countryCode	string	The ISO 3166-1 alpha-2 country code
regionCode	?string	The ISO 3166-2 subdivision code within the country, or null when the entry covers the whole country

Account identity object

The sign-in method a new deployment uses after set the setup sign-in method.

Structure

Field	Type	Description
mode	string	The account identity mode now in effect
tag_style	string	How usernames are tagged, one of the tag styles

Get instance discovery

GET/.well-known/fluxerUnauthenticated

Returns the instance discovery object describing this deployment.

The path has no /v1 prefix.

Response

Status	Body	Condition
200	instance discovery object	The discovery document was returned

Rate limit

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 shares this bucket.

Get client geolocation

GET/v1/ipUnauthenticated

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

A lookup that resolves nothing still returns 200 with countryCode, regionCode, latitude, and longitude all null. Treat this as an unknown location.

Response

Status	Body	Condition
200	geolocation object	The location was resolved, fully, partly, or not at all

Rate limit

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.

Set the setup sign-in method

PUT/v1/instance/setup/account-identityUnauthenticated

Chooses how members sign in on a new self-hosted deployment, and on an email deployment whether usernames have tags. Returns an account identity object with the choice now in effect.

The setup wizard calls this before the owner account exists. The choice stays open on a self-hosted deployment until setup is complete or the first account exists. After that, on a deployment that was already in use before username sign-in existed, and on every hosted deployment, the route returns 409 ACCOUNT_IDENTITY_LOCKED. The choice and the first registration take turns, so a choice never lands after the first account exists. A repeated call while the choice is open replaces the earlier one.

Anyone can call this before the first account exists

The route needs no credential, the same as the rule that makes the first registration the instance admin. An operator finishes setup in the same sitting that brings the deployment up.

JSON body

Field	Type	Description
mode	string	The account identity mode to use
tag_style?1	string	How usernames are tagged, one of the tag styles. Defaults to none

¹ A username instance always uses none. Sending random with username returns the field code TAG_STYLE_REQUIRES_EMAIL_SIGN_IN on tag_style

Response

Status	Body	Condition
200	account identity object	The mode was stored
400	error response	The body is invalid, or random tags were requested with username
409	error response	ACCOUNT_IDENTITY_LOCKED, because the sign-in method can no longer change
423	error response	GENERAL_ERROR, because a registration or another choice held the turn for more than 15 seconds
429	rate limit response	Route or global bucket denies the request

Side effects

The deployment stores the choice, and instance discovery reports it as account_identity and tag_style from then on. No Gateway Dispatch is emitted.

Rate limit

10 requests per minute for each authenticated user, or for each client IP address when the request has no credential, on the instance:setup:account_identity bucket.

Get OpenAPI document

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. Its server URL is the deployment’s api_client endpoint followed by /v1. Every path is relative to that URL.

Response

Status	Body	Condition
200	OpenAPI 3.1 document	The document was returned

Rate limit

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.