Get server settings
Fetch global settings for a Zulip server.
Note: this endpoint does not require any authentication at all, and you can use it to check:
- If this is a Zulip server, and if so, what version of Zulip it's running.
- What a Zulip client (e.g. a mobile app or
zulip-terminal) needs to
know in order to display a login prompt for the server (e.g. what
authentication methods are available).
# Pass the path to your zuliprc file here.
client = zulip.Client(config_file="~/zuliprc")
# Fetch the settings for this server
result = client.get_server_settings()
curl -sSX GET -G https://oscafrica.zulipchat.com/api/v1/server_settings \
This endpoint does not accept any parameters.
authentication_methods: Each key-value pair in the object indicates whether the authentication
method is enabled on this server.
Changes: Deprecated in Zulip 2.1, in favor of the more expressive
password: Whether the user can authenticate using password.
dev: Whether the user can authenticate using development api key.
email: Whether the user can authenticate using email.
ldap: Whether the user can authenticate using ldap.
remoteuser: Whether the user can authenticate using remoteuser.
github: Whether the user can authenticate using their github account.
azuread: Whether the user can authenticate using their azuread account.
gitlab: Whether the user can authenticate using their gitlab account.
apple: Whether the user can authenticate using their apple account.
google: Whether the user can authenticate using their google account.
saml: Whether the user can authenticate using saml.
external_authentication_methods: A list of dictionaries describing the available external
authentication methods (E.g. Google, GitHub, or SAML)
enabled for this organization.
The list is sorted in the order in which these
authentication methods should be displayed.
Changes: New in Zulip 2.1.
name: A unique, table, machine-readable name for the authentication method,
intended to be used by clients with special behavior for specific
authentication methods to correctly identify the method.
display_name: Display name of the authentication method, to be used in all buttons
for the authentication method.
display_icon: URL for an image to be displayed as an icon in all buttons for
the external authentication method.
When null, no icon should be displayed.
login_url: URL to be used to initiate authentication using this method.
signup_url: URL to be used to initiate account registration using this method.
zulip_version: The version of Zulip running in the server.
zulip_feature_level: An integer indicating what features are
available on the server. The feature level increases monotonically;
a value of N means the server supports all API features introduced
before feature level N. This is designed to provide a simple way
for client apps to decide whether the server supports a given
feature or API change. See the changelog for
details on what each feature level means.
Changes. New in Zulip 3.0. We recommend using an implied value
of 0 for Zulip servers that do not send this field.
push_notifications_enabled: Whether mobile/push notifications are enabled.
is_incompatible: Whether the Zulip client that has sent a request to this endpoint is
deemed incompatible with the server.
email_auth_enabled: Setting for allowing users authenticate with an email-password
require_email_format_usernames: Whether all valid usernames for authentication to this
organization will be email addresses. This is important
for clients to know whether to do client side validation
of email address format in a login prompt.
This value will be false if the server has LDAP
authentication enabled with a username and
realm_uri: The organization's canonical URL.
realm_name: The organization's name (for display purposes).
realm_icon: The URL for the organization's logo formatted as a square image,
used for identifying the organization in small locations in the
mobile and desktop apps.
realm_description: HTML description of the organization, as configured by the organization
Please note that not all of these attributes are guaranteed to appear in a
response, for two reasons:
- This endpoint has evolved over time, so responses from older Zulip servers
might be missing some keys (in which case a client should assume the
- If a
/server_settings request is made to the root domain of a
multi-subdomain server, like the root domain of zulip.com, the settings
that are realm-specific are not known and thus not provided.
A typical successful JSON response for a single-organization server may look like:
"realm_description": "<p>The Zulip development environment default organization. It's great for testing!</p>",
"realm_name": "Zulip Dev",