Quickbase · OpenAPI Overlay 1.0.0

API Evangelist security overlay for Quickbase RESTful JSON API

3 actions 3 updates security extends ../openapi/_original/quickbase-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Quickbase's API. It is a proposal applied on top of the contract, not a document Quickbase publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

securitySchemessecurityx-apievangelist-docs

Targets 3

$.components
$
$.info

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist security overlay for Quickbase RESTful JSON API
  version: 1.0.0
extends: ../openapi/_original/quickbase-openapi.yml
x-generated: '2026-10-18'
x-method: generated
x-source: https://developer.quickbase.com/auth
x-rationale: >-
  The captured OpenAPI (openapi/_original/qb-openapi-v3.json, served at
  https://developer.quickbase.com/qb-openapi-v3.json) models authentication only
  as a required `Authorization` header PARAMETER (components.parameters.authorization)
  and declares no components.securitySchemes and no root security requirement.
  Quickbase's Authorization page documents three header forms:
  `QB-USER-TOKEN {TOKEN}` (permanent user token), `QB-TEMP-TOKEN {TOKEN}`
  (temporary token from getTempTokenDBID) and `QB-ACCESS-KEY {KEY}` (secure links,
  runQuery and runReport only). This overlay adds those as a declared security
  scheme and a root requirement WITHOUT mutating the original spec.
actions:
  - target: $.components
    description: Declare the Authorization-header token scheme documented at developer.quickbase.com/auth.
    update:
      securitySchemes:
        quickbaseToken:
          type: apiKey
          in: header
          name: Authorization
          description: >-
            Send `Authorization: QB-USER-TOKEN {TOKEN}` for a permanent user token,
            `QB-TEMP-TOKEN {TOKEN}` for a temporary token (see getTempTokenDBID), or
            `QB-ACCESS-KEY {KEY}` with secure links on runQuery and runReport. Every
            call also requires the `QB-Realm-Hostname` header (e.g. demo.quickbase.com).
            Never store a permanent user token client-side.
  - target: $
    description: Apply the token scheme to every operation by default.
    update:
      security:
        - quickbaseToken: []
  - target: $.info
    description: Point agents at the human docs for auth and headers.
    update:
      x-apievangelist-docs:
        authorization: https://developer.quickbase.com/auth
        headers: https://developer.quickbase.com/headers
        errors: https://developer.quickbase.com/errors
        pagination: https://developer.quickbase.com/pagination

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay 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 overlay
curl "https://apis.io/api/v1/overlays/quickbase-openapi-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?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.