Skip to main content

Read API Introduction and Webhooks

Our read API is available to access your transactions and accounts, bringing new levels of connectivity to your Xace accounts

M
Written by Mariia

What is the Xace API?

The Xace API is a secure way for your company’s software to communicate with Xace so you can view account information and, where enabled, manage payments without logging into the Xace app each time.

You do not need to be a developer to understand the idea. Think of it as a reliable messenger between your systems and Xace.


Why does this exist?

Many businesses already use their own tools for accounting, payroll, or operations. They don’t want to copy balances and payments by hand.

The API lets those tools:

  • Look up what is on your Xace accounts

  • Keep records of money in and money out

  • Set up who you pay and, with the right access, send payments

  • Get notified when something important happens with a payment


What can you do with it?

1. See your accounts and balances:

Ask Xace: “Which accounts do we have?” and “How much is available right now?”

2. See transactions (money movements):

Ask for a list of payments and receipts — like a bank statement inside your own system.


For a full day view, Xace can also provide a daily statement (CAMT.053), often used for reconciliation.

3. Save people or companies you pay (payees):

Add contractors or suppliers once. Later payments use that saved profile — no retyping bank details every time.

4. Send and approve payments (when your access allows it):

Payments use the payee’s ID. If needed, your process can include approvals before funds are disbursed.

5. Get alerts when something changes (webhooks)

Xace can notify your system of payment-related events, so you don’t have to keep asking, “Anything new?”


A simple picture of how it works

  1. You get the credentials in your Xace account.

  2. Your software signs in securely

  3. It asks for what it needs (balances, transactions, payees…)

  4. Xace replies — or confirms an action

  5. Optional: Xace also pushes updates when payments change.


Good habits

  • Prefer focused requests (one account, one day’s statement) over downloading everything repeatedly

  • If you see “too many requests”, wait and try again

  • Be clear early: do you mainly need visibility, or also need to send payments?


Who is this for?

Finance/ops teams, partners evaluating connectivity, or anyone who opened the page by accident and wanted a plain explanation.

One takeaway: the Xace API is the bridge that lets your software see account activity and, with the right permissions, help manage payments — safely and without constant manual login.


Next step

Full technical docs are available here:

Did this answer your question?