Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zulip authentication API

The authentication API from Zulip — 4 operation(s) for authentication.

Zulip authentication API is one of 17 APIs that Zulip publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include authentication. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against 5 base URLs: https://{subdomain}.zulipchat.com/api/v1, {server}/api/v1, https://chat.zulip.org/api/v1, http://localhost:9991/api/v1, http://{subdomain}.testserver/json.

4 operations 4 paths 5 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Servers
https://{subdomain}.zulipchat.com/api/v1
{server}/api/v1
https://chat.zulip.org/api/v1
http://localhost:9991/api/v1
http://{subdomain}.testserver/json
Authentication
HTTP Basic
License
Resource Areas
1

Authentication & Security 1

Zulip authentication API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

  • BasicAuth — Basic authentication, with the user's email as the username, and the API key as the password. The API key can be fetched using the /fetchapikey or /devfetchapi…

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

authentication 4
POST
/fetch_api_key
Fetch an API key (production)
fetch-api-key body → 200
POST
/jwt/fetch_api_key
Fetch an API key (JWT)
jwt-fetch-api-key body → 200
POST
/dev_fetch_api_key
Fetch an API key (development only)
dev-fetch-api-key body → 200
GET
/dev_list_users
List users (development only)
dev-list-users → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are UserBase (18 properties), JsonResponseBase (1 property). Each schema is shown below with its type and property counts.

JsonSuccessBase
Changes: As of Zulip 7.0 (feature level 167), if any parameters sent in the request are not supported by this endpoint, a successful JSON response will include…
IgnoredParametersUnsupported
array
An array of any parameters sent in the request that are not supported by the endpoint. See [error handling](/api/rest-error-handlingignored-parameters) documen…
JsonResponseBase
object
1 property
UserBase
object
A dictionary containing basic data on a given Zulip user. Changes: Removed isbillingadmin field in Zulip 10.0 (feature level 363), as it was replaced by the ca…
18 properties
ApiKeyResponse

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zulip-authentication-api-openapi.yml Raw ↑

Other APIs Zulip publishes across the network.

Zulip REST API
Zulip Events API
Zulip Webhooks
Zulip bots API
Zulip channels API
Zulip drafts API
Zulip invites API
Zulip messages API
Zulip mobile API
Zulip navigation_views API
Zulip real_time_events API
Zulip reminders API