LATAM context
finO$'s API is pure REST: every resource (transactions, accounts, categories, statements, summary, periods) has its own URL, HTTP verbs express intent, errors follow convention (4xx client, 5xx server), and every response is JSON wrapped in the same envelope { data, pagination }.
Concrete example
GET /api/v1/summary?month=2026-07 returns the month's summary. GET /api/v1/transactions?from=2026-01-01&limit=200 lists paginated transactions. POST /api/v1/statements uploads a PDF and responds 202 because processing is asynchronous.
How it shows up on your bank statement
A REST API doesn't change what the bank statement says. It changes how you get it. Instead of downloading a PDF and opening it, a program sends the file and gets back already-structured transactions, in the same shape for every bank.
How does finO$ handle this?
finO$ publishes its OpenAPI spec at api.getfinos.com/api/v1/openapi.json. Official SDKs (Node, Python, PHP, Laravel) are still on the roadmap. Until then, any HTTP client works.