Request Finance
Request Finance is a crypto and fiat invoicing, payments, and payroll platform that lets businesses issue invoices, accept payments in crypto and fiat, pay contractors and employees, and manage accounts payable and receivable. Its Accounts Payable and Receivable (AP/AR) REST API lets developers programmatically create and send invoices, run off-chain and on-chain payroll payments, track invoice status without polling blockchains or bank accounts, manage organizations and clients, and download invoice PDFs. Invoices are settled through the Request Network protocol across many EVM chains and stablecoins, with crypto-to-fiat settlement via banking partners. The API uses Bearer authentication (API keys for quick starts, OAuth 2.0 / OIDC via Auth0 for production), real-time webhooks with HMAC-signed payloads, and a Sepolia testnet sandbox. Request Finance is backed by Balderton Capital.
Request Finance publishes 1 API on the APIs.io network: AP and AR API. Tagged areas include Company, Payments, Invoicing, Crypto, and Web3.
The Request Finance catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Request Finance’s developer surface includes documentation, API reference, getting-started guide, support, signup flow, authentication, sandbox, and 19 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Request Finance AP and AR API
The Accounts Payable and Receivable REST API for issuing invoices, accepting crypto and fiat payments, running payroll, and managing organizations and clients. JSON request and ...
Rate Limits 1
Documented rate limits and quota policies.
Request Rate Limits
RATE LIMITSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Request Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Company 1
The organization behind the API