4 results found

1. Provide Cloud-First API Access (OpenAPI Schemas + Static Bearer Tokens) for AI Agents and Cloud Orchestrators

   The business problem:
   As a modern agency, we are moving away from fragmented, individual desktop setups. We are centralising our team workflow inside headless cloud orchestrators (like Google AI Studio and Vertex AI) so everyone (from developers to leadership) can query financial insights securely from one central workspace.

   Currently, AI agent integrations heavily favour local-first protocols (like desktop-bound MCP servers). This creates a massive architectural wall for cloud-first teams. Desktop-first setups rely on interactive browser logins and local environments, which completely block stateless, headless cloud workflows.

   The Blocker:
   Cloud orchestrators operate entirely in headless cloud environments. They cannot open interactive desktop browser windows to click "Connect." They require standard, stateless web connections.

   Why This Matters:
   - Supporting the A2A Standard: As the tech industry aligns around open standards like Google's Agent-to-Agent (A2A) protocol, integrations are shifting from traditional UI dashboards to multi-agent collaboration. Exposing machine-readable schemas keeps Xero at the cutting edge of this shift.
   - Unlocking Enterprise & Agency Adoption: Larger accounting partners and agencies operate under strict cloud-first IT governance. They block local desktop clients for security reasons. Enabling centralised cloud access allows enterprise teams to safely adopt Xero AI workflows at scale.
   - Reducing Support Overhead: Right now, teams are forced to hack together complex, brittle local proxy infrastructure to get AI tools to talk to Xero. Exposing clean, cloud-native endpoints eliminates this setup friction entirely.

   Our Feature Request:
   To allow businesses to securely connect their centralised AI agents directly to Xero data without massive engineering overhead, we need Xero to expose a cloud-to-cloud option containing:

   1. Standard OpenAPI 3.0 Schemas (JSON/YAML): A clean schema detailing available read-only tools and endpoints that can be dropped directly into the "Tools" section of cloud platforms like Google AI Studio.
   2. Static, Long-Lived API Bearer Tokens (or M2M Client Credentials): Support for secure, stateless Machine-to-Machine (M2M) authentication, eliminating the need for interactive desktop OAuth loops.

   Thank you

   The business problem:
   As a modern agency, we are moving away from fragmented, individual desktop setups. We are centralising our team workflow inside headless cloud orchestrators (like Google AI Studio and Vertex AI) so everyone (from developers to leadership) can query financial insights securely from one central workspace.

   Currently, AI agent integrations heavily favour local-first protocols (like desktop-bound MCP servers). This creates a massive architectural wall for cloud-first teams. Desktop-first setups rely on interactive browser logins and local environments, which completely block stateless, headless cloud workflows.

   The Blocker:
   Cloud orchestrators operate entirely in headless cloud environments. They cannot open interactive… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General requests  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Connection management in Developer Portal

   With the upcoming changes to the developer program and connection-based billing, I’ve run into a practical issue: there’s currently no clear way to determine which connections are still active versus legacy or unused.

   In most cases, there’s a single connection per Xero tenant. However, edge cases do occur, for example when a tenant wasn’t correctly disconnected, resulting in multiple connections tied to the same tenant across different users. Over time, these can accumulate, and it becomes difficult to identify which ones are actually in use.

   Would it be possible to introduce a “Last Used” or “Last Request” field for each connection in the connection management section in the developer portal? This would make it straightforward to identify active connections and safely clean up inactive ones.

   Given that billing is now tied to connection count, having a way to distinguish active from inactive connections would be extremely helpful. I’m happy to handle cleanup on our side, but I need a reliable signal to do so.

   With the upcoming changes to the developer program and connection-based billing, I’ve run into a practical issue: there’s currently no clear way to determine which connections are still active versus legacy or unused.

   In most cases, there’s a single connection per Xero tenant. However, edge cases do occur, for example when a tenant wasn’t correctly disconnected, resulting in multiple connections tied to the same tenant across different users. Over time, these can accumulate, and it becomes difficult to identify which ones are actually in use.

   Would it be possible to introduce a “Last Used” or “Last Request” field for each… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General requests  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. CIS

   CIS annual statements - it would be very helpful if we could bulk email ALL subcontractors at the end of the tax year. Most lose monthly emailed statements so ask for an annual statement so they can do their returns and its time consuming to go in and individually, download statement, print to PDF and then email each person one at a time. Can you make a function like with the monthly CIS returns where you can email ALL subcontractors at once please ! :)

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General requests  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. P&L by tracking category as a widget on my dashboard

   P&L by Tracking Category as a widget on my dashboard

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  General requests  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating