canonical: https://jentic.com/apis/getfinero.com/getfinero

# Getfinero Finero Public API

The Finero Public API automates accounts receivable and cash flow for a tenant's workspace. An agent reads customer aging balances and the installments behind them, lists and summarizes invoices by collection status, and creates payment links for an invoice singly or in a batch. It lists confirmed payments, reschedules or deletes the scheduled emails that chase a payment link, pushes held receipts to a connected ERP, and runs collection workflows. Every request is tenant-scoped, lists are cursor-paginated, and authentication is a bearer API key that is either admin or read-only.

## For AI agents

Track accounts-receivable aging, list and summarize invoices and payments, create payment links, run collection emails, and sync with connected ERPs. Authenticates with a bearer API key that is either admin or read-only.

## Scope

Does not handle general ledger accounting, payroll, or tax filing. Use for accounts-receivable and cash-flow automation only.

## Capabilities

- List customer aging balances and explain them by invoice installment
- Create a payment link for an invoice, singly or in a batch
- List invoices and summarize them by collection status and amount
- List confirmed payments and push held receipts to a connected ERP
- Start a pull from a connected ERP and set its automatic cadence
- Reschedule or delete a scheduled payment-link email
- List automation workflows and their executions

## Use cases

### Agent-Driven Collections

An AI agent handling collections can call the Finero Public API through Jentic to find overdue customers, create payment links for their invoices, and schedule the reminder emails that chase them. The agent works the receivables without the developer wiring the bearer auth or the cursor paging by hand, and a read-only key keeps a reporting agent off any side-effecting operation. Jentic returns the matching operation and its input schema so the agent acts inline.

Example prompt: Find invoices that are overdue, create a payment link for each, and schedule a reminder email per link

### AR Aging and Invoice Reporting

A finance dashboard can report the health of receivables by reading customer aging balances and summarizing invoices by collection status and total. Finero buckets aging per customer, explains it down to the installment, and totals invoices by status, so a workflow can show what is overdue and how much cash is outstanding without exporting the ledger.

Example prompt: Pull the aging summary and the invoice summary by collection status for a given currency

### Payment Links and Collection Emails

A billing workflow can issue payment links in bulk and manage the emails that deliver them to customers. Finero creates several payment links at once with an idempotency key, lists the scheduled payment-link emails, and lets an agent reschedule or cancel one, so a team controls exactly when each reminder goes out.

Example prompt: Create a batch of payment links for a set of invoices and reschedule the reminder email for one of them

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/aging/customers` | List customer aging balances |
| GET | `/v1/invoices` | List invoices |
| GET | `/v1/invoices/summary` | Summarize invoices by collection status |
| POST | `/v1/payment-links` | Create a payment link |
| POST | `/v1/payment-links/batch` | Create several payment links at once |
| GET | `/v1/payments` | List confirmed payments |
| POST | `/v1/erp-connections/{connectionId}/sync` | Start a pull from the ERP |

## Key resources

- **Aging** — List customer aging balances, the installments behind them, and the aging summary.
- **Invoices** — List invoices, read one with its installments, and summarize them by collection status.
- **Payment Links and Payments** — Create, read, and deactivate payment links, batch-create them, and list confirmed payments.
- **ERP Connections and Sync** — List connections, start a pull, set the sync cadence and payment-push mode, and read sync runs.
- **Scheduled Emails and Workflows** — Reschedule or delete scheduled payment-link emails and list automation workflows and executions.

## 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:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 68 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 93 / 100
- **View full report:** https://jentic.com/apis/getfinero.com/getfinero/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 Finero by hand means handling its bearer API key and admin-or-read-only permissions, following cursor pagination through every list, and sending an idempotency key on payment-link creation. Through Jentic you install once, import Finero from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Finero puts the resource id in the URL path, so a rule can bound your agent to the operations it needs, and a read-only key keeps it off side-effecting ones entirely. You choose which operations it may call, so deactivating a payment link or pushing receipts to the ERP is not included unless you add it.
- **Credential handling:** Your Finero API key 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 customer aging' or 'create a payment link', and Jentic returns the matching Finero operation with its input schema so the agent calls the right endpoint directly.

## Related APIs

- **ChargeOver API** — Manages invoices, recurring billing, and collections for a billing workspace.
- **Stripe API** — Issues invoices and payment links and handles dunning through Stripe Billing.
- **GoCardless API** — Collects direct debit payments and manages mandates.

## FAQ

### What authentication does the Finero Public API use?

The Finero Public API authenticates with a bearer API key, where a key is issued as either admin or read-only, per its OpenAPI spec. Through Jentic the key is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

### Is there a Finero MCP server?

You don't need an MCP server to give your agent the Finero Public API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can read receivables and create payment links straight away.

### Can I limit what my agent is allowed to do with the Finero Public API?

Yes. Finero keys can be issued read-only so they reach only side-effect-free operations, and a Jentic rule narrows it further: allow your agent to read aging and create payment links but leave deactivating links or pushing receipts to the ERP out unless you add them. Every call it makes is logged.

### Can I create a payment link for an invoice with the Finero Public API?

Yes. The create operation issues a payment link for an invoice and requires an idempotency key so a retry does not create a duplicate, and a batch operation creates several links in one request.

### What are the rate limits for the Finero Public API?

Its OpenAPI spec states a limit of 120 requests per minute per key and 600 requests per minute per tenant, both in fixed 60-second windows. Every response that reached the limiter carries RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers so an agent can pace against them.

### How do I read customer aging with the Finero Public API through Jentic?

Search Jentic for an intent like 'list customer aging balances' and it returns the Finero aging operation with its input schema, so your agent requests the balances and reads back the buckets. To run it on your own infrastructure, install Jentic One from its GitHub repo.