6 APIs across 4 product groups.
| I want to... | Use | Why |
|---|---|---|
| Record invoices, payments, and produce financial reports | Xero Accounting API | The Accounting API is the core double-entry ledger, covering invoices, contacts, bank transactions, and reporting across 237 operations. |
| Track fixed assets and their valuations | Xero Assets API | The Assets API manages the fixed asset register and asset types separately from the general ledger. |
| Push bank statement lines into an organisation | Xero Bank Feeds API | The Bank Feeds API is a partner-only service for financial institutions to deliver statement data for reconciliation, distinct from recording transactions in the ledger. |
| Run Australian payroll for employees and leave | Xero Payroll AU API | The Payroll AU API handles employees and leave applications for Australia-region organisations, which the Accounting API does not cover. |
| Store and attach source documents | Xero Files API | The Files API manages file uploads, folders, and associations, while the Accounting API only attaches documents to existing records. |
| List or disconnect connected organisations | Xero OAuth 2 Identity Service API | The OAuth 2 Identity Service API manages tenant connections rather than any business data. |
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Xero APIs by hand means implementing OAuth 2.0, sending the correct xero-tenant-id header on every request, and mapping operations across accounting, assets, payroll, bank feeds, files, and identity yourself. Through Jentic you install once, add the Xero APIs from the Jentic directory, store the OAuth credential once, and your agent calls any of them.
Permission scoping
Your own rules decide which Xero operations the agent may run, so you can grant read-only reporting from the Accounting API while withholding writes such as posting invoices, creating payroll employees, or deleting a tenant connection until you add them.
Credential isolation
Your Xero OAuth credential and tenant details are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Specific to using Xero APIs through Jentic.
What can an AI agent do across the Xero APIs?
An agent can run a small business's finances end to end: create and reconcile invoices, record payments, pull profit-and-loss and balance sheet reports, maintain a fixed asset register, run Australian payroll and leave, upload and attach source documents, deliver bank statement feeds, and manage which Xero organisations it is connected to.
Do the Xero APIs share one set of credentials?
Yes. All of them use OAuth 2.0, and a single Xero connection with the appropriate scopes authorises requests across the Accounting, Assets, Bank Feeds, Payroll AU, Files, and Identity Service APIs. Each request adds a xero-tenant-id header to pick the organisation the operation applies to.
How do the accounting-related APIs fit together?
The Accounting API is the core ledger for invoices, contacts, payments, and reports. The Assets API keeps the fixed asset register, the Files API stores source documents, the Bank Feeds API delivers statement lines for reconciliation, and the Payroll AU API handles employees and leave. They reference the same organisation, so an agent can combine them in one workflow.
Are any of the Xero APIs restricted?
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can create and reconcile invoices, record payments, pull profit-and-loss and balance sheet reports, manage fixed assets, run Australian payroll for employees and leave, upload source documents, push bank statement feeds, and list or disconnect the Xero organisations it is connected to.
Xero exposes a full double-entry accounting system as an API, with dedicated services for fixed assets, Australian payroll, bank feeds, file storage, and tenant identity built around the same organisation model. Every operation is keyed to a specific Xero organisation through a tenant id, so one integration can serve many businesses under one connection model.
Use for: Automating small-business accounting on Xero: invoicing, payments, bank reconciliation, financial reporting, fixed assets, Australian payroll, source-document storage, and managing connected organisations.
Not supported: card payment processing, inventory management, non-Australian payroll, public bank-feed access, customer support ticketing
Credentials: All six APIs use OAuth 2.0 (the Identity Service API also accepts basic auth), and a single Xero OAuth connection with the right scopes covers them, with each request carrying a xero-tenant-id header to select the target organisation.
All 6 Xero OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.
Xero is a cloud accounting platform for small and medium businesses. Its APIs cover double-entry bookkeeping, invoicing, payments, and financial reporting through the Accounting API, plus fixed asset registers, Australian payroll, bank feed connections, file storage, and OAuth 2 tenant connection management. Together they let software record and reconcile financial transactions, run payroll, attach source documents, and manage which organisations an integration is connected to.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Xero APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fxero.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fxero.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “automate small business accounting and payroll on xero”.
Each workflow spans multiple Xero APIs. Jentic routes each operation to the right API automatically.
Invoice with attached receipt
An agent creates a sales invoice in the Accounting API, then uploads the supporting receipt through the Files API and associates it with the invoice so the source document travels with the ledger entry.
Create an authorised sales invoice for a contact, upload the PDF receipt, and associate the file with the new invoice.
Xero Accounting API + Xero Files API
Feed-driven bank reconciliation
A financial services partner pushes statement lines through the Bank Feeds API, then an agent pulls the unreconciled bank transactions in the Accounting API and matches them against outstanding invoices by amount and date.
Deliver a batch of statement lines via a feed connection, then retrieve unreconciled bank transactions and reconcile them against matching invoices.
Xero Bank Feeds API + Xero Accounting API
Payroll cost posting
An agent reads employees and leave applications from the Payroll AU API and records the corresponding wage and leave costs as transactions in the Accounting API general ledger.
List active payroll employees and their leave applications, then record the associated wage expenses as bank transactions in the ledger.
Xero Payroll AU API + Xero Accounting API
Multi-organisation reporting
An agent lists the connected Xero organisations through the Identity Service API and then pulls a profit-and-loss report for each one through the Accounting API, selecting the tenant per request.
Retrieve all connected organisations, then generate a profit-and-loss report for each by setting the tenant id per call.
Xero OAuth 2 Identity Service API + Xero Accounting API
Intent-based discovery
Agents search the Jentic directory by intent, such as 'create an invoice', 'run a profit and loss report', or 'add a fixed asset', and Jentic returns the matching Xero operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
The Bank Feeds API is a closed, partner-only service available to financial institutions with a financial services partnership with Xero, so an agent can only use it once that access is granted. The Payroll AU API applies only to organisations in the Australia region.
Which API selects the organisation an agent acts on?
The OAuth 2 Identity Service API lists the tenant connections available to the authorised user and can disconnect one. Every other API then uses the xero-tenant-id header to target a specific organisation, which is how one integration serves multiple businesses.
Can an agent work with more than one Xero organisation at a time?
Yes. After listing connections through the Identity Service API, an agent can direct each request at a different organisation by changing the tenant id header, so a single connection can generate reports or post transactions across several businesses.
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.