Pluggy Open Finance API

Name: Pluggy Open Finance API
Brand: Pluggy Open Finance API
Availability: InStock

✓ Official Vendor SpecPaymentsPayouts Transfersbearer36 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Pluggy Open Finance API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pluggy Open Finance API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pluggy Open Finance API.

Create API key

List available connectors

Retrieve a specific connector

Validate connector credentials

GET STARTED

Start building with Pluggy Open Finance API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Pluggy Open Finance API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'create api key', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

36 endpoints — pluggy open finance api for connecting to financial institutions, managing items, accounts, transactions, investments, and webhooks.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pluggy Open Finance API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create api key') and Jentic returns the matching Pluggy Open Finance API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Pluggy Open Finance API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Pluggy Open Finance API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Pluggy Open Finance API

Connect the Pluggy Open Finance API to your agent

Capabilities

Start building with Pluggy Open Finance API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs