Qwil · Authentication Profile

Qwil Authentication

Authentication

Authentication profile for the Qwil API. Derived from live probing rather than a published OpenAPI (Qwil publishes no public specification). The production API host at https://api.qwil.co is a Django REST Framework service that answers unauthenticated requests with HTTP 401 and `WWW-Authenticate: Bearer realm="api"`, indicating bearer-token authorization. The Qwil web application (app.qwil.com) authenticates end users through Firebase Authentication (Google Identity Platform) on the multi-tenant project `qwil-1149` / tenant `qwil-prod-*`; the resulting identity token is presented to the API as a bearer token. No public OAuth authorization-server or OpenID Connect discovery document is exposed (see well-known/qwil-well-known.yml). Access to the API is private/partner-gated.

Qwil secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyFintechFinancial-ServicesPaymentsBankingPlaid
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

qwil-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: live probe of https://api.qwil.co (WWW-Authenticate header) + app.qwil.com
  client configuration
description: >-
  Authentication profile for the Qwil API. Derived from live probing rather than
  a published OpenAPI (Qwil publishes no public specification). The production API
  host at https://api.qwil.co is a Django REST Framework service that answers
  unauthenticated requests with HTTP 401 and `WWW-Authenticate: Bearer realm="api"`,
  indicating bearer-token authorization. The Qwil web application (app.qwil.com)
  authenticates end users through Firebase Authentication (Google Identity
  Platform) on the multi-tenant project `qwil-1149` / tenant `qwil-prod-*`; the
  resulting identity token is presented to the API as a bearer token. No public
  OAuth authorization-server or OpenID Connect discovery document is exposed
  (see well-known/qwil-well-known.yml). Access to the API is private/partner-gated.
summary:
  types:
  - http
  http_schemes:
  - bearer
  identity_provider: Firebase Authentication (Google Identity Platform), multi-tenant
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    Bearer token presented in the Authorization header. Observed live via the
    `WWW-Authenticate: Bearer realm="api"` challenge returned by
    https://api.qwil.co for unauthenticated requests.
  sources:
  - live-probe:https://api.qwil.co

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.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/qwil-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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.