Zipline Ai · Authentication Profile
Zipline Ai Authentication
Authentication
Zipline Ai secures its APIs with http, oauth2, and openIdConnect across 1 declared security scheme, as derived from its OpenAPI definitions.
Company
Methods: http, oauth2, openIdConnect
Schemes: 1
OAuth flows:
API key in:
Security Schemes
bearerAuth http
scheme: bearer
Source
Authentication Profile
generated: '2026-07-21'
method: searched
source: https://zipline.ai/docs/running_on_zipline_hub/Auth
docs: https://zipline.ai/docs/running_on_zipline_hub/Auth
summary:
types:
- http
- oauth2
- openIdConnect
overview: >-
Zipline supports optional authentication to secure access to the platform.
Users authenticate through the frontend (OAuth or SSO); backend services
(Orchestration, Eval) validate requests using signed JWTs verified
statelessly via JWKS. The CLI authenticates with the device authorization
flow (RFC 8628).
human_login: [OAuth 2.0, SSO (OIDC), SSO (SAML)]
service_auth: [Bearer JWT verified via JWKS]
cli_auth: [RFC 8628 device authorization flow]
providers:
- name: Google OAuth
type: oauth2
env: [GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET]
redirect_uri: "{AUTH_URL}/api/auth/callback/google"
- name: GitHub OAuth
type: oauth2
env: [GITHUB_OAUTH_CLIENT_ID, GITHUB_OAUTH_CLIENT_SECRET]
- name: SSO (OIDC / SAML)
type: openIdConnect
notes: Enterprise SSO via OIDC or SAML; SAML post-login redirect honors AUTH_EXTERNAL_URL behind a reverse proxy.
schemes:
- name: bearerAuth
type: http
scheme: bearer
bearerFormat: JWT
description: >-
Short-lived JWT minted by `zipline auth get-access-token` (or issued to the
frontend after OAuth/SSO login). Backend services validate it statelessly
against the JWKS endpoint (AUTH_JWKS_URL, e.g. /api/auth/jwks). When
AUTH_ENABLED=true but the JWKS endpoint is unreachable, protected routes
return 503 rather than allowing unauthenticated access.
sources:
- openapi/zipline-ai-workflow-status-openapi.yml
- https://zipline.ai/docs/running_on_zipline_hub/Auth
authorization:
model: role-based (RBAC)
notes: Workflow Status API requires viewer access when role-based authorization is enabled.
allowlist: AUTH_ALLOWED_PRINCIPALS restricts sign-in to specific domains or exact emails.
config_env:
- AUTH_ENABLED
- AUTH_URL
- AUTH_EXTERNAL_URL
- AUTH_SECRET
- AUTH_ALLOWED_HOSTS
- AUTH_ALLOWED_PRINCIPALS
- AUTH_JWKS_URL
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/zipline-ai-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.