Flic · Authentication Profile

Flic Authentication

Authentication

Flic secures its APIs with jwt-signed-webhook and ble-pairing across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanySmart ButtonsIoTSmart HomeBluetoothWebhookSDKHardware

Methods: jwt-signed-webhook, ble-pairing Schemes: 2 OAuth flows: API key in:

Security Schemes

cloud-buttons-jwt jws

scheme: JWT

ble-pairing device-pairing

scheme: Bluetooth Low Energy

Source

Authentication Profile

generated: '2026-07-19'
method: searched
source: https://github.com/50ButtonsEach/flic-cloud-buttons-documentation
docs: https://github.com/50ButtonsEach/flic2-documentation
summary:
  types: [jwt-signed-webhook, ble-pairing]
  note: >-
    Flic has no OAuth/REST API-key surface. Two authentication models are in
    play: (1) SDK/protocol access to buttons is authenticated via Bluetooth Low
    Energy pairing between the Flic 2 button and the host app/hub (the pairing
    identity is what the flic2lib SDKs establish); (2) Cloud Buttons webhook
    deliveries are authenticated to the receiver by a signed JWT.
schemes:
  - name: cloud-buttons-jwt
    type: jws
    scheme: JWT
    algorithm: ES256
    key_type: ECDSA P-256
    direction: inbound-webhook
    verification: >-
      The receiving endpoint verifies the ES256-signed JWT using Flic's public
      key (published in JWK/PEM/DER/raw). Claims carry the button uuid, serial,
      battery, pressedAt, and click type.
    sources: [asyncapi/flic-cloud-buttons-webhooks.yml]
  - name: ble-pairing
    type: device-pairing
    scheme: Bluetooth Low Energy
    direction: sdk-to-button
    verification: >-
      flic2lib (iOS/Android/C/Linux/Windows) establishes a paired, encrypted BLE
      session with the button; there is no server-side token exchange.
    sources: [packages/flic-packages.yml]

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/flic-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.