canonical: https://jentic.com/apis/pluggy.ai/pluggy

# Pluggy Open Finance API

Pluggy open finance API for connecting to financial institutions, managing items, accounts, transactions, investments, and webhooks. The API exposes 36 endpoints secured with bearer authentication.

## For AI agents

Programmatically create API key, create connect token. Covers 36 operations with bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Create API key
- List available connectors
- Retrieve a specific connector
- Validate connector credentials

## Use cases

### Payments Operations

Use the Pluggy Open Finance API to perform payments operations programmatically. The API provides 36 endpoints covering core functionality including create API key, create connect token, list available connectors.

Example prompt: Call POST /auth to create API key

### Automated Auth Management

Automate auth operations by combining multiple Pluggy Open Finance API endpoints. Agents can create connect token and then list available connectors in a single workflow.

Example prompt: Call POST /connect-token to create connect token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pluggy Open Finance API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create API key', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth` | Create API key |
| POST | `/connect-token` | Create connect token |
| GET | `/connectors` | List available connectors |
| GET | `/connectors/{id}` | Retrieve a specific connector |
| POST | `/connectors/validate` | Validate connector credentials |
| POST | `/items` | Create a connection item |
| GET | `/items/{id}` | Retrieve an item |
| PATCH | `/items/{id}` | Update an item |

## Key resources

- **Auth** — Authentication operations
- **Connectors** — Financial institution connector operations
- **Items** — Connection item management
- **Accounts** — Account retrieval
- **Transactions** — Transaction retrieval

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/pluggy.ai/pluggy/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Pluggy Open Finance API by hand means exchanging your keys for a bearer token at /auth, managing connect tokens, and tracking each connection item yourself. Through Jentic you install once, import the Pluggy Open Finance API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Pluggy puts the item and connector id in the URL path (`/items/{id}`, `/connectors/{id}`), so a rule can pin your agent to one item: it can read and update that connection and nothing else. You choose the operations it may call, so creating new items is included only if you add the POST /items operation.
- **Credential handling:** Your Pluggy credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list available connectors' or 'read an item', and Jentic returns the matching Pluggy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Pluggy Open Finance API use?

The Pluggy Open Finance API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create API key with the Pluggy Open Finance API?

Yes. Use the POST /auth endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pluggy Open Finance API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create API key through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create API key'. Jentic returns the matching Pluggy Open Finance API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Pluggy Open Finance API have?

The Pluggy Open Finance API exposes 36 endpoints covering auth, connectors, items operations.

### Can I limit what my agent is allowed to do with the Pluggy Open Finance API?

Yes. Because Jentic One is self-hosted, you decide which Pluggy operations your agent may call and which credential it uses, so you can allow read and update on a connection while withholding creation. Since Pluggy carries the item and connector id in the URL path, such as `/items/{id}` and `/connectors/{id}`, a rule can pin the agent to a single item so it reads and updates that connection and nothing else. Creating new connections through POST /items is available only if you explicitly add that operation to the agent's allowed set.