Pluggy · Authentication Profile

Pluggy Authentication

Authentication

Pluggy uses API keys for server-side requests and Connect Tokens for client-side applications. API keys provide full access to all endpoints, while Connect Tokens have limited scope to specific Item and Account data.

Pluggy declares 2 security scheme(s) across its OpenAPI definitions.

CompanyOpen FinanceBankingFinancial DataPaymentsBrazilFintech

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

API Key apiKey

Connect Token other

Source

Authentication Profile

generated: '2026-10-18'
method: searched
generator: extract-docs-artifacts.py (deepseek)
source: https://docs.pluggy.ai/en/docs/authentication.md
sources:
- https://docs.pluggy.ai/en/docs/authentication.md
- https://docs.pluggy.ai/en/docs/connect-widget/authentication.md
- https://docs.pluggy.ai/en/docs/connect-widget/oauth-support.md
- https://docs.pluggy.ai/en/docs/developer-tools/authentication-failures.md
description: Pluggy uses API keys for server-side requests and Connect Tokens for client-side applications. API keys provide full access to all
  endpoints, while Connect Tokens have limited scope to specific Item and Account data.
schemes:
- type: apiKey
  name: API Key
  evidence: 'Pluggy uses two kinds of credentials, depending on where the request is made from: - **API Key** -- used for server-side requests.'
  header: X-API-KEY
  location: header
  how_to_obtain: First, you'll need to authenticate with the Pluggy API, using your `CLIENT_ID` and `CLIENT_SECRET`, to [create an API Key](/reference/auth-create)
    via `POST /auth`.
- type: other
  name: Connect Token
  evidence: '- **Connect Token** -- used from client-side applications (i.e. the [Connect Widget](/docs/connect-widget/introduction)).'
  location: header
  how_to_obtain: Then, with your API Key, you'll have to make a call to [POST /connect_token](/reference/connect-token-create).
docs: https://docs.pluggy.ai/en/docs/authentication.md
note: The pages mention CLIENT_ID and CLIENT_SECRET credentials but don't specify a specific authentication scheme for them. They are used to
  obtain API keys via POST /auth.

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