Request Finance

Read access to a Request Finance workspace via the Request Finance API. Lists invoices and payment requests, fetches one by ID, and reads the client directory.

The tool is read-only. It creates no invoices, changes no payment state, and never executes a payment.

Actions

Filtering invoices

variant separates ordinary invoices from payroll, and filter_by separates payables from receivables. Both map to Request Finance's own wire values (rnf_invoice / rnf_salary, sent / received).

{
  "action": "list_invoices",
  "filter_by": "received",
  "status": ["pending"],
  "take": 50
}

search matches transaction hash, invoice number, or company name. Responses always request format=paginated, so the caller gets total counts alongside the page rather than a bare array.

Incremental reads, with a caveat that matters

fetch_since sends the vendor's creationDateRange filter, a URL-encoded JSON object:

{ "action": "fetch_since", "created_from": "2026-08-01T00:00:00.000Z", "take": 100 }

It filters on creation date, not modification. An invoice created last month and edited today will not come back. Request Finance documents no updated-since parameter, and states that this filter is not a true incremental sync.

The consequence is worth stating plainly: a sync built only on this will look complete while missing every edit to an older invoice. Pair it with a periodic full read if edits matter.

Only the two-field form {"from":..., "to":...} appears in the vendor documentation. Omitting created_to sends a one-sided range, which is not documented and is unverified.

Auth

Create an API key in the Request Finance dashboard and store it:

export REQUEST_FINANCE_API_KEY=<api key>

The host injects it as the raw Authorization header value with no Bearer prefix, which is how the Request Finance API expects it. The key is never visible to the tool.

Limits

• One workspace per API key, so an agent reading two workspaces needs two installations.
• take caps at 100 per call (default 25); page with skip.
• Request Finance documents OAuth as the more secure production option. This tool supports API keys only.
• Date-range filtering (creationDateRange) is not exposed. The API documents it as an ISO 8601 range but does not state the range syntax, and it has not been verified against a live workspace. It will be added once confirmed.
• Invoice status values are passed through as free strings for the same reason: the documented parameter exists but its enum is not enumerated in the published reference. Multiple statuses are sent as a repeated status query parameter, which is the common REST convention but is not stated in the published reference. A server that reads only the last value would narrow results silently, so verify a multi-status filter against a live workspace before trusting it.
• No write actions. Creating invoices, approving, and paying are deliberately out of scope, per the Finance spec's rule that payment execution stays outside the agent.