canonical: https://jentic.com/apis/figfinance.io/fig-finance

# Fig Finance API

The Fig Finance API exposes a compact set of 5 endpoints for managing accounts and transactions inside the Fig Finance platform. Authentication is through an API key sent in the X-API-Key header, suitable for server-to-server integrations. The surface covers account creation and lookup plus transaction listing and creation under a single /v1 base path.

## For AI agents

Create and list financial accounts and transactions via 5 endpoints, authenticated with an X-API-Key header.

## Scope

Does not handle card processing, KYC verification, or invoicing - use for managing Fig Finance accounts and transactions only.

## Capabilities

- Create new financial accounts under a tenant
- Retrieve an account record by its identifier
- List all accounts visible to the calling key
- Record financial transactions against an account
- List transactions filtered by account and date range

## Use cases

### Account Provisioning

Provision financial accounts on demand when a new customer onboards in an upstream system. The Fig Finance API exposes POST /accounts as a single call that returns the new account ID, suitable for synchronous onboarding flows. Replaces manual account creation in finance dashboards.

Example prompt: POST /accounts with the customer name and currency, then return the account_id for downstream linking

### Transaction Recording

Record transactions against accounts as they occur in connected systems, building a complete ledger inside Fig Finance. The API offers POST /transactions for create and GET /transactions for listing with filters, supporting reconciliation against external sources. Useful for fintech integrators consolidating activity from multiple processors.

Example prompt: POST /transactions with amount, account_id, and reference, then GET /transactions to confirm it was recorded

### Account Reporting

Generate account-level reports by listing accounts and pulling their transactions for a specified period. With only 5 endpoints, this workflow is simple to implement and predictable to operate. Suitable for scheduled finance summaries delivered into Slack or email.

Example prompt: GET /accounts, then GET /transactions for each, and compose a summary of net activity per account this month

### AI Agent Finance Lookups via Jentic

Through Jentic, an agent can answer questions like which accounts had no activity this month or where a specific transaction landed. The minimal Fig Finance surface makes it ideal for agent tooling because the schema is small and the operations map cleanly to natural-language intents.

Example prompt: Search Jentic for 'list financial transactions', filter by account_id and date_from, and return the latest 20

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/accounts` | List accounts |
| POST | `/accounts` | Create an account |
| GET | `/accounts/{id}` | Get account by ID |
| GET | `/transactions` | List transactions |
| POST | `/transactions` | Create a transaction |

## Key resources

- **Accounts** — Create, retrieve, and list financial accounts
- **Transactions** — Create and list transactions tied to accounts

## Why Jentic

- **Setup:** Wiring the Fig Finance API by hand means managing its X-API-Key header, pointing at the v1 base, and separating account reads from transaction writes yourself. Through Jentic you install once, import the Fig Finance API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Fig Finance puts the account id in the URL path (`/accounts/{id}`), so a rule can pin your agent to the accounts you allow. You choose the operations it may call, so a write like creating a transaction is not included unless you add it alongside the account reads.
- **Credential handling:** Your Fig Finance API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw X-API-Key value never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'record a financial transaction' or 'list accounts', and Jentic returns the matching Fig Finance operation with its input schema, so the agent calls it without reading the developer docs.

## Related APIs

- **Plaid API** — Bank-data aggregation alternative covering thousands of financial institutions
- **TrueLayer API** — Open Banking alternative focused on UK and EU institutions
- **Invoice Ninja API** — Invoicing platform that pairs with Fig Finance for accounts receivable

## FAQ

### What authentication does the Fig Finance API use?

Fig Finance uses an API key sent in the X-API-Key header. Through Jentic the key is encrypted in your Jentic One instance and never enters agent context.

### Can I list transactions filtered by account?

Yes. GET /transactions accepts query parameters such as account_id and date filters so an agent can scope results per account without retrieving the full ledger.

### What are the rate limits for the Fig Finance API?

Fig Finance does not publish per-second limits in the OpenAPI spec; consult developers.figfinance.io for the current quotas tied to your plan.

### How do I create an account through Jentic?

Search Jentic for 'create financial account', load the POST /accounts schema, and execute with customer name and currency. Run pip install jentic to start.

### How many endpoints does the Fig Finance API expose?

Five: list and create accounts, get an account by ID, plus list and create transactions. The compact surface keeps integration straightforward.

### Can I record transactions against multiple accounts?

Yes. POST /transactions takes an account_id, so an agent can record activity against any account visible to the API key in a single call.

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

Yes. Jentic One is self-hosted, so your own rules decide which Fig Finance operations and credentials the agent may use. Because the account id lives in the URL path (`/accounts/{id}`), you can pin the agent to only the accounts you allow. You also choose the operations it may call, so a write such as creating a transaction via POST /transactions is not available unless you add it alongside the account reads like GET /accounts.