canonical: https://jentic.com/apis/xero.com/xero-bank-feeds-api

# Xero Bank Feeds API

The Bank Feeds API is a closed API that is only available to financial institutions that have an established financial services partnership with Xero. If you're an existing financial services partner that wants access, contact your local Partner Manager. If you're a financial institution who wants to provide bank feeds to your business customers, contact us to become a financial services partner. The API exposes 7 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create one or more new feed connection, searches for feed connections. Covers 7 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- Create one or more new feed connection
- Searches for feed connections
- Retrieve single feed connection based on a unique id provided
- Delete an existing feed connection
- Monitor Xero Bank Feeds API operational status and events

## Use cases

### Finance and Accounting Operations

Use the Xero Bank Feeds API to perform finance operations programmatically. The API provides 7 endpoints covering core functionality including create one or more new feed connection, searches for feed connections, retrieve single feed connection based on a unique id provided.

Example prompt: Call POST /FeedConnections to create one or more new feed connection

### Automated Feedconnections Management

Automate feedconnections operations by combining multiple Xero Bank Feeds API endpoints. Agents can searches for feed connections and then retrieve single feed connection based on a unique id provided in a single workflow.

Example prompt: Call GET /FeedConnections to searches for feed connections, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Xero Bank Feeds API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'create one or more new feed connection', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /FeedConnections | Create one or more new feed connection |
| GET | /FeedConnections | Searches for feed connections |
| GET | /FeedConnections/{id} | Retrieve single feed connection based on a unique id provided |
| POST | /FeedConnections/DeleteRequests | Delete an existing feed connection |
| POST | /Statements | Creates one or more new statements |
| GET | /Statements | Retrieve all statements |
| GET | /Statements/{statementId} | Retrieve single statement based on unique id provided |

## Key resources

- **Feedconnections** — Operations for FeedConnections
- **Statements** — Operations for Statements

## Why Jentic

- **Setup:** Wiring the Xero Bank Feeds API by hand means implementing its OAuth2 flow, sending the tenant header, and managing feed connections and statements yourself. Through Jentic you install once, import the Xero Bank Feeds API from the API Directory, store the OAuth2 credential once, and your agent calls it.
- **Permission scoping:** The Xero Bank Feeds API puts the feed connection and statement id in the URL path (/FeedConnections/{id}, /Statements/{statementId}), so a rule can pin your agent to one feed connection or statement. You choose the operations it may call, so writes like creating feed connections or delete requests are not included unless you add them.
- **Credential handling:** Your Xero Bank Feeds API OAuth2 credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a new feed connection' or 'get a statement', and Jentic returns the matching Xero Bank Feeds API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Alternative finance API
- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows

## FAQ

### What authentication does the Xero Bank Feeds API use?

The Xero Bank Feeds API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create one or more new feed connection with the Xero Bank Feeds API?

Yes. Use the POST /FeedConnections endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Xero Bank Feeds API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create one or more new feed connection through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create one or more new feed connection'. Jentic returns the matching Xero Bank Feeds API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Xero Bank Feeds API have?

The Xero Bank Feeds API exposes 7 endpoints covering feedconnections, statements operations.

### Can I limit what my agent is allowed to do with the Xero Bank Feeds API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Xero Bank Feeds API operations and credentials the agent may use. You can grant read-only calls such as GET /FeedConnections, GET /FeedConnections/{id}, and GET /Statements while withholding writes like POST /FeedConnections, POST /FeedConnections/DeleteRequests, and POST /Statements. Because the feed connection and statement id sit in the URL path, a rule can also pin the agent to a single feed connection or statement.