Embat
Embat is a real-time treasury management platform for finance teams, founded in Madrid and backed by Creandum. Its REST/JSON API (OpenAPI 3.1, 103 operations across 21 resource areas) connects third-party applications and ERPs to Embat to manage bank connections, balances, transactions, payments and payment orders, cash-flow forecasting, scenarios, accounting entries and accounts, contacts, and bank reconciliation across multiple companies. Authentication is HTTP Bearer using a JWT idToken obtained from an email/password token endpoint (60-minute expiry, no refresh); every resource is scoped by a companyId path parameter and list endpoints paginate with limit + nextPageToken.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Embat the way a machine reads it — 48 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Embat scores 29.0/100 (thin), with a separate agent-readiness read of 29/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Embat's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/embat/"
title="Embat on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/embat.svg"
alt="Embat Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/embat/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/embat/"
title="Embat on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/embat/card.svg"
alt="Embat Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Embat
Each block below is one kind of artifact we hold for Embat. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Embat AccountingAccounts API
`AccountingAccount` represents an account in the company's chart of accounts. `accountingCode` is the unique identifier of an account and is used as its ID; it also determines t...
Embat AccountingEntries API
`AccountingEntry` represents a single line of a company's general accounting journal — an outflow (`assetAmount`) or inflow (`liabilityAmount`) movement posted to a ledger accou...
Embat Attributes API
`Attribute` represents a custom field that you can define once and then use to tag records across Embat, such as an ERP dimension, a cost center or any other analytic field you ...
Embat Authentication API
`Authentication` provides the credentials Embat issues to access the rest of the public API. Every other endpoint requires a JWT `idToken` in the `Authorization: Bearer
Embat Balances API
`Balance` represents the end-of-day balance of a bank product (account) for a given calendar day. Embat records one balance per product per day, expressed both in the product's ...
Embat Banks API
`Bank` represents a banking relationship connected to your company in Embat — for example, an aggregated connection to a specific banking entity. Each bank relationship groups t...
Embat Categories API
`Category` represents a treasury or cashflow classification in Embat, used to group transactions, forecasts and operations for reporting (e.g. "Providers", "Payroll", "Subscript...
Embat Companies API
A `Company` represents a legal entity configured in your Embat workspace. Its `id` is the `companyId` used throughout this API: almost every other endpoint is scoped by `company...
Embat Contacts API
`Contact` represents a client or supplier your company transacts with. `customId` is the unique identifier of a contact: set your own value to use as your ERP contact ID, or let...
Embat DebtScheduleConfigs API
Embat Files API
`File` represents a banking file exchanged between Embat and a bank: either a file **received** from a bank (a reception, e.g. an account statement or a confirmation file) or a ...
Embat Forecasts API
`Forecast` represents a treasury cash flow projection generated by Embat for a given date, classified under a `Category` and grouped into a `Scenario` (e.g. a base case or a str...
Embat ForeignExchangeRates API
`ForeignExchangeRate` records the daily exchange rates Embat uses to convert amounts between currencies for accounting purposes. Each record captures the rates observed on a giv...
Embat Logs API
`Logs` let your integration report execution events, warnings or errors observed while interacting with the Embat API, so Embat's support team can diagnose integration issues. L...
Embat Operations API
`Operation` represents an accounting operation with a pending amount to settle — typically an invoice or bill due from or to a `Contact` (client or supplier). An invoice with se...
Embat PaymentOrders API
Embat Payments API
`Payment` represents money moving between a bank transaction and the operations (invoices, bills) or accounting entries it settles. `customId` is the unique identifier of a paym...
Embat Products API
`Product` represents a bank account, credit line, card or wallet held by the company — either aggregated automatically from a bank connection, or added manually in Embat. A prod...
Embat ReconcilingItems API
Embat ReconcilingSources API
Embat Scenarios API
A `Scenario` represents a forecasting hypothesis in Embat's treasury forecast: a named, currency-denominated projection covering a defined horizon (`startPeriod` to `endPeriod`)...
Embat Transactions API
`Transaction` represents a movement recorded on one of your bank accounts (`Product`). Each transaction reports the balance of its product immediately after the movement, and ca...
Scroll within the panel for all 22 ·
Open Collections 23
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONEmbat AccountingAccounts API
OPEN COLLECTIONEmbat AccountingAccounts AccountingEntries API
OPEN COLLECTIONEmbat AccountingAccounts Attributes API
OPEN COLLECTIONEmbat AccountingAccounts Authentication API
OPEN COLLECTIONEmbat AccountingAccounts Balances API
OPEN COLLECTIONEmbat AccountingAccounts Banks API
OPEN COLLECTIONEmbat AccountingAccounts Categories API
OPEN COLLECTIONEmbat AccountingAccounts Companies API
OPEN COLLECTIONEmbat AccountingAccounts Contacts API
OPEN COLLECTIONEmbat AccountingAccounts DebtScheduleConfigs API
OPEN COLLECTIONEmbat AccountingAccounts Files API
OPEN COLLECTIONEmbat AccountingAccounts Forecasts API
OPEN COLLECTIONEmbat AccountingAccounts ForeignExchangeRates API
OPEN COLLECTIONEmbat AccountingAccounts Logs API
OPEN COLLECTIONEmbat AccountingAccounts Operations API
OPEN COLLECTIONEmbat AccountingAccounts PaymentOrders API
OPEN COLLECTIONEmbat AccountingAccounts Payments API
OPEN COLLECTIONEmbat AccountingAccounts Products API
OPEN COLLECTIONEmbat AccountingAccounts ReconcilingItems API
OPEN COLLECTIONEmbat AccountingAccounts ReconcilingSources API
OPEN COLLECTIONEmbat AccountingAccounts Scenarios API
OPEN COLLECTIONEmbat AccountingAccounts Transactions API
OPEN COLLECTIONScroll within the panel for all 23 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Embat — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/embat · machine-readable index on apis.io
This is an independent, third-party profile of Embat, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.