Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
Every Xero query type available in TrustPager - contacts, invoices, P&L, Balance Sheet, aged receivables and payables - with parameters, examples, and troubleshooting.
TrustPager connects directly to your Xero account and lets you pull live financial data into the CRM — via the API, the MCP server, or any automation that can call a webhook. This article covers every available Xero query type, the parameters each one accepts, and what to watch out for.
integration_id — copy it from the Xero tile on the integrations page after connecting.Send a POST request to the TrustPager API:
POST https://app.trustpager.com/api/integrations/query
Authorization: Bearer <your_api_key>
Content-Type: application/json
{
"query_type": "xero_contacts",
"integration_id": "<your_integration_id>",
"params": {}
}
Your API key is available at https://app.trustpager.com/account/api. If you are using the TrustPager MCP server, call the query_integration tool with the same fields.
Returns your full Xero contact list — customers and suppliers.
No required params. Optionally pass { "search": "acme" } to filter by name.
Returns full detail for a single Xero contact including addresses, phone numbers, and account details.
Required: contact_id — the Xero ContactID (UUID).
Returns all invoices across your Xero organisation. Supports filtering by status, date range, and contact.
Optional params: status (e.g. AUTHORISED, PAID), from_date, to_date, contact_id.
Returns invoices for a specific Xero contact only.
Required: contact_id. Optional: status, from_date, to_date.
Returns your Xero chart of accounts — account codes, types, and balances.
No required params.
Returns all tax rates configured in Xero.
No required params.
Returns the Profit & Loss report for a date range.
Optional params: from_date or fromDate, to_date or toDate, periods, timeframe (MONTH / QUARTER / YEAR), tracking_category_id, tracking_option_id, standard_layout, payments_only. Both snake_case and camelCase are accepted.
Returns the Balance Sheet report as at a given date.
Optional params: date (YYYY-MM-DD, defaults to today), periods, timeframe, tracking_option_id_1, tracking_option_id_2, standard_layout, payments_only. Both snake_case and camelCase are accepted.
Returns outstanding receivables (money owed to you) bucketed by how overdue each invoice is — across all contacts.
Response shape: { as_at, totals: { total, current, days_1_30, days_31_60, days_61_90, days_90_plus }, contacts: [...] }. Contacts are sorted by total outstanding, largest first.
Optional param: date (YYYY-MM-DD). Defaults to today.
Same as above but for payables — money your organisation owes to suppliers.
Optional param: date (YYYY-MM-DD). Defaults to today.
Returns the detailed Xero aged receivables report for a specific contact.
Required: contact_id (Xero ContactID UUID). Optional: date, from_date, to_date, periods, timeframe.
If you need a summary across all contacts, use xero_aged_receivables_summary instead.
Returns the detailed Xero aged payables report for a specific contact.
Required: contact_id (Xero ContactID UUID). Optional: date, from_date, to_date, periods, timeframe.
If you need a summary across all contacts, use xero_aged_payables_summary instead.
The Xero ContactID is a UUID like 3e776c4b-ea9e-4bb1-9bc9-f2c24f5e4c3a. The quickest way to find it is to run xero_contacts first — each record in the response includes a ContactID field.
xero_aged_receivables without a contact_id. Use xero_aged_receivables_summary for an across-the-board view, or pass a Xero ContactID.from_date and fromDate are accepted. If you were using camelCase previously and values were being dropped, re-run your query — this has been fixed.Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Hear her in 10 seconds.

60 minutes with a real human · Google Meet · Free.