Xero

Overview

Property	Value
Slug	`xero`
Auth	OAuth 2.0 + PKCE
API version	v2.0
Sandbox	Yes — via Xero’s “Demo Company”
Rate limit	60 req/min, 5,000 req/day per org

Supported resources

Resource	List	Get	Create	Update	Delete
Invoice	✓	✓	✓	✓	✓
Contact	✓	✓	✓	✓	✓
Account	✓	✓	✓	✓	✓
Payment	✓	✓	✓	✓	✓
Tax Rate	✓	✓	—	—	—
Journal Entry	✓	✓	✓	✓	✓
Expense	✓	✓	✓	✓	✓
Purchase Order	✓	✓	✓	✓	✓
Sales Order	✓	✓	✓	✓	✓
Credit Note	✓	✓	✓	✓	✓
Vendor Credit	✓	✓	✓	✓	✓
Item	✓	✓	✓	✓	✓
Tracking Category	✓	✓	—	—	—
Company Info	✓	✓	—	—	—
Employee	✓	✓	—	—	—
Transaction	✓	✓	✓	✓	✓
Bank Feed Account	✓	✓	✓	✓	✓
Bank Feed Transaction	—	—	✓	—	—
Balance Sheet	✓	✓	—	—	—
Income Statement	✓	✓	—	—	—
Attachment	✓	✓	✓	✓	✓
Address	—	✓	—	—	—
Phone Number	—	✓	—	—	—
Accounting Period	—	—	—	—	—
Payment Method	—	—	—	—	—
Payment Term	—	—	—	—	—
Cash Flow Statement	—	—	—	—	—
General Ledger Transaction	—	—	—	—	—
Expense Report	—	—	—	—	—
Item Fulfillment	—	—	—	—	—
Project	—	—	—	—	—

Connect setup

Xero uses OAuth 2.0 with PKCE. You need an app registered in the Xero Developer Portal.

Create a Xero app

Go to Xero Developer Portal → New app. Choose Web app and integration type Accounting. Under Configuration, copy the Client ID and Client Secret.

Add the redirect URL

In your app’s OAuth 2.0 redirect URIs list, add:

https://api.routemcp.io/api/v1/auth/callback

Configure required scopes

Enable the following scopes on your app:

openid
profile
email
offline_access
accounting.invoices
accounting.payments
accounting.banktransactions
accounting.manualjournals
accounting.contacts
accounting.settings
accounting.reports.balancesheet.read
accounting.reports.profitandloss.read
accounting.attachments
files

Connect via the widget

When your end user opens the Connect widget, they will enter the Client ID and Client Secret, then be redirected to Xero to authorize the connection.

Usage

# List sales invoices (AR) from Xero
curl "https://api.routemcp.io/api/v1/accounting/invoice?provider=xero" \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "X-End-User-Id: user-123"

# Create a bill (AP) — set type=ACCOUNTS_PAYABLE
curl -X POST "https://api.routemcp.io/api/v1/accounting/invoice?provider=xero" \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -H "X-End-User-Id: user-123" \
  -d '{ "type": "ACCOUNTS_PAYABLE", "contact": "urn:xero:contact:abc", "total_amount": 850.00, "due_date": "2026-06-01" }'

# Update by URN
curl -X PATCH "https://api.routemcp.io/api/v1/accounting/invoice/urn:xero:invoice:abc-uuid?provider=xero" \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -H "X-End-User-Id: user-123" \
  -d '{ "memo": "Approved by ops" }'

Notes

Pass type: "ACCOUNTS_PAYABLE" on invoice create to write a bill. The same pattern applies to credit_note / vendor_credit. For vendor contacts, set is_supplier: true.
address and phone_number ids are discoverable inline on contact.addresses[].id and contact.phone_numbers[].id.

Overview

CRM

Accounting

Calendar

Developer

Productivity

Documents & Storage

Communication

Project Management

Database

Overview

Supported resources

Connect setup

Usage

Notes

​Overview

​Supported resources

​Connect setup

​Usage

​Notes

Overview

Supported resources

Connect setup

Usage

Notes