fettle-sh · Authentication Profile

Fettle Sh Authentication

Authentication

Fettle uses API keys presented as Bearer tokens in the Authorization header.

fettle-sh declares 1 security scheme(s) across its OpenAPI definitions.

MonitoringUptimeDevelopersAI AgentsAPI
Methods: Schemes: 1 OAuth flows: API key in:

Security Schemes

Authorization http-bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-10-30'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://fettle.sh/docs/api-keys
sources:
- https://fettle.sh/docs/api-keys
- https://fettle.sh/docs/api-keys.md
- https://fettle.sh/docs/quickstart
- https://fettle.sh/docs/quickstart.md
description: Fettle uses API keys presented as Bearer tokens in the Authorization header.
schemes:
- type: http-bearer
  name: Authorization
  evidence: '-H "Authorization: Bearer fettle_your_key_here"'
  location: header
  header: Authorization
  how_to_obtain: Create an API key in Settings → API Keys; the secret is shown once at creation.
note: No other authentication schemes (apiKey, oauth2, http-basic, jwt, hmac, mtls, other) are documented.
docs: https://fettle.sh/docs/api-keys

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/fettle-sh-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.