Skip to content

Accounting · Beta

Maxio Core
API integration

Ship Accounting features without building the integration. Full Maxio Core API access via Proxy and 60+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us
Maxio Core

Use Cases

Why integrate with Maxio Core

Common scenarios for SaaS companies building Maxio Core integrations for their customers.

01

Embed Quote-to-Cash handoff in your CRM

Let sales teams using your CRM push closed-won deals directly into their finance team's Maxio Core instance, eliminating manual re-entry of customers, contracts, and sales orders. This turns your CRM into a credible system of record for finance-aligned RevOps teams.

02

Power automated AR and dunning workflows

If you build collections or AR automation software, connecting to Maxio Core lets you pull receivables summaries, past-due invoices, and expired autopay cards to drive proactive outreach. Your users get accurate collections data without exporting CSVs from Maxio.

03

Feed FP&A and BI tools with trusted SaaS metrics

Instead of rebuilding ARR, MRR, and deferred revenue logic, pull finalized reports and CSVs directly from Maxio Core into your forecasting or BI product. Your users trust the numbers because they match what their controller already signed off on.

04

Inject usage-based billing events into revenue recognition

If you run a metering or usage-based billing engine, push transactions and invoices into Maxio Core so its rules engine can handle ASC 606-compliant revenue recognition. You stay focused on metering while Maxio owns compliance.

05

Keep external data warehouses in sync with finance

Data platforms can use Maxio Core's deleted-state feeds for contracts, invoices, transactions, and revenue entries to maintain accurate mirrors without exhaustive re-syncs. This gives your users a reliable finance dataset for downstream analytics.

What You Can Build

Ship these features with Truto + Maxio Core

Concrete product features your team can ship faster by leveraging Truto’s Maxio Core integration instead of building from scratch.

01

Closed-won to Maxio sync

Automatically create customers, contracts, and sales orders in Maxio Core the moment a deal is marked closed-won in your product.

02

Receivables and collections dashboard

Surface customer receivables summaries, open invoices, and expired autopay cards inside your app to drive dunning sequences and cash collection workflows.

03

Period-close aware writes

Check close dates and GL sync statuses before mutating transactions or invoices so your integration never attempts edits against a locked accounting period.

04

Programmatic report ingestion

Trigger Maxio Core report runs and pull the resulting CSVs to feed ARR, MRR, and deferred revenue data into FP&A models or BI dashboards.

05

Incremental finance data sync

Use deleted-contract, deleted-invoice, deleted-transaction, and deleted-revenue-entry feeds to keep an external warehouse perfectly aligned without full-table scans.

06

Contract and invoice lifecycle management

Create, update, and delete contracts, invoices, and transactions in Maxio Core from inside your product, with full read access to customers, items, and billing methods.

SuperAI

Maxio Core AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_maxio_core_accounts

List GL account records, up to 100 per page. Other field filters from the account's API documentation are passed through.

get_single_maxio_core_account_by_id

Get one GL account by its id.

list_all_maxio_core_auto_renewal_profiles

List auto-renewal profile records, up to 100 per page. Other field filters from the account's API documentation are passed through.

get_single_maxio_core_auto_renewal_profile_by_id

Get one auto-renewal profile by its id.

list_all_maxio_core_billing_descriptions

List billing line item description records, up to 100 per page. Other field filters from the account's API documentation are passed through.

get_single_maxio_core_billing_description_by_id

Get one billing line item description by its id.

list_all_maxio_core_billing_methods

List billing method records, up to 100 per page. Other field filters from the account's API documentation are passed through.

get_single_maxio_core_billing_method_by_id

Get one billing method by its id.

list_all_maxio_core_close_date_changes

List every closing date and transaction lock date change, oldest first, with who made it and the old and new dates. Needs the Report User role.

list_all_maxio_core_close_dates

Get the closing and transaction lock dates in effect today, how each is set, and the latest closing date Maxio enforces with its Maxio, QuickBooks and Xero sources. Needs the Report User role.

list_all_maxio_core_contracts

List contract records, up to 100 per page. A contract belongs to a customer and a register; transactions hang off contracts. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_contract_by_id

Get one contract by its id. The response carries an ETag header to send back as if_match on update.

create_a_maxio_core_contract

Create a contract. Field names follow the contract record; check required fields in the account's in-app API documentation.

update_a_maxio_core_contract_by_id

Update a contract; only the fields sent are changed (PATCH). A successful write returns only the id, so read the record again for its new ETag.

delete_a_maxio_core_contract_by_id

Delete a contract by its id.

list_all_maxio_core_country_codes

List country code records, up to 100 per page. Other field filters from the account's API documentation are passed through.

get_single_maxio_core_country_code_by_id

Get one country code by its id.

list_all_maxio_core_currency_codes

List currency code records, up to 100 per page. Other field filters from the account's API documentation are passed through.

list_all_maxio_core_customer_analytics

Get a customer's analytics (the data behind the customer dashboard). Needs the Report User role. Required: customer_id.

list_all_maxio_core_customer_receivables_summaries

Get a customer's open balance, past-due balance and count, oldest past-due date, last payment date, average days to pay and first contract start date, in home currency. Required: customer_id.

list_all_maxio_core_customers

List customer records, up to 100 per page. Customers hold contracts; billing details sit in the nested billing_profile. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_customer_by_id

Get one customer by its id. The response carries an ETag header to send back as if_match on update.

create_a_maxio_core_customer

Create a customer. Field names follow the customer record; check required fields in the account's in-app API documentation.

update_a_maxio_core_customer_by_id

Update a customer; only the fields sent are changed (PATCH). A successful write returns only the id, so read the record again for its new ETag.

delete_a_maxio_core_customer_by_id

Delete a customer by its id.

list_all_maxio_core_deleted_contracts

List deleted contract records, up to 100 per page. Feed of contracts deleted in Maxio Core, for incremental syncs. Other field filters from the account's API documentation (e.g. customer=) are passed through.

list_all_maxio_core_deleted_invoices

List deleted invoice records, up to 100 per page. Feed of invoices deleted in Maxio Core, for incremental syncs. Other field filters from the account's API documentation (e.g. customer=) are passed through.

list_all_maxio_core_deleted_revenue_entries

List deleted revenue entry records, up to 100 per page. Feed of revenue entries deleted in Maxio Core, for incremental syncs. Other field filters from the account's API documentation (e.g. customer=) are passed through.

list_all_maxio_core_deleted_transactions

List deleted transaction records, up to 100 per page. Feed of transactions deleted in Maxio Core, for incremental syncs. Other field filters from the account's API documentation (e.g. customer=) are passed through.

list_all_maxio_core_expired_autopay_cards

List active customers on card autopay whose card has expired, or expires within two months of as_of, earliest expiry first.

list_all_maxio_core_fx_rates

Get the rate Maxio Core uses to convert a local currency into home currency on a day (date) or over a range of up to 366 days (start_date/end_date). Multi-currency accounts only; a day without a rate returns nulls. Required: local_currency.

list_all_maxio_core_gl_sync_statuses

Get each GL Sync destination's connection state, newest run and error, what holds a period closed, and each configuration's attempt for that period with posted totals.

list_all_maxio_core_invoices

List invoice records, up to 100 per page. Invoices are generated from transactions; line_items link back to transactions. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_invoice_by_id

Get one invoice by its id.

create_a_maxio_core_invoice

Create an invoice. Field names follow the invoice record; check required fields in the account's in-app API documentation.

update_a_maxio_core_invoice_by_id

Update an invoice; only the fields sent are changed (PATCH).

delete_a_maxio_core_invoice_by_id

Delete an invoice by its id.

list_all_maxio_core_items

List item records, up to 100 per page. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_item_by_id

Get one item by its id.

list_all_maxio_core_payment_terms

List payment term records, up to 100 per page. Other field filters from the account's API documentation are passed through.

get_single_maxio_core_payment_term_by_id

Get one payment term by its id.

list_all_maxio_core_registers

List register records, up to 100 per page. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_register_by_id

Get one register by its id.

list_all_maxio_core_report_definitions

List the report definitions in the account (read-only through the API). Use an id with report_runs.create.

get_single_maxio_core_report_definition_by_id

Get one report definition with its configuration and parameters.

list_all_maxio_core_report_exports

List report exports.

get_single_maxio_core_report_export_by_id

Get an export and its status; once Completed, url points to the file.

create_a_maxio_core_report_export

Export a completed report run to a file (recommended for large reports). Poll report_exports.get until Completed. Required: report_run, format_name.

list_all_maxio_core_report_run_csvs

Stream a completed report run's results as CSV (smaller reports; use report_exports for large ones). Required: report_run_id.

list_all_maxio_core_report_run_results

Read a completed run's results as JSON: without section, the run metadata and its sections; with section, that section's columns and one page of rows. Generic Report Builder reports only; 410 once the results are purged. Required: report_run_id.

create_a_maxio_core_report_run_retention

Keep a run's stored results past the 5-day purge window (keep true), or release them (keep false). Required: report_run_id, keep.

list_all_maxio_core_report_runs

List report runs, newest settings first unless sorted.

get_single_maxio_core_report_run_by_id

Get a report run and its status (Running, Completed or Failed). Poll every 5-10 seconds until Completed.

create_a_maxio_core_report_run

Run a report from a report_definition id or a one_click_report UUID (never both). export_format_name also creates an export. Returns the run id; poll report_runs.get.

list_all_maxio_core_revenue_entries

List revenue entry records, up to 100 per page. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_revenue_entry_by_id

Get one revenue entry by its id.

list_all_maxio_core_revenue_recognition_methods

List revenue recognition method records, up to 100 per page. Other field filters from the account's API documentation are passed through.

get_single_maxio_core_revenue_recognition_method_by_id

Get one revenue recognition method by its id.

list_all_maxio_core_sales_orders

List sales order records, up to 100 per page. Sales orders carry customer, contract and line item data that Maxio Core processes into records. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_sales_order_by_id

Get one sales order by its id.

create_a_maxio_core_sales_order

Create a sales order. Field names follow the sales order record; check required fields in the account's in-app API documentation.

list_all_maxio_core_transactions

List transaction records, up to 100 per page. Transactions (subscription, one-time and renewal lines) drive invoices and revenue schedules. Other field filters from the account's API documentation (e.g. customer=) are passed through.

get_single_maxio_core_transaction_by_id

Get one transaction by its id.

create_a_maxio_core_transaction

Create a transaction. Field names follow the transaction record; check required fields in the account's in-app API documentation.

update_a_maxio_core_transaction_by_id

Update a transaction; only the fields sent are changed (PATCH).

delete_a_maxio_core_transaction_by_id

Delete a transaction by its id.

Why Truto

Why use Truto’s MCP server for Maxio Core

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1100+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Start with Maxio Core in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

01

Link your customer’s Maxio Core account

Use Truto’s frontend SDK to connect your customer’s Maxio Core account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Maxio Core

Truto’s Proxy API is a 1-to-1 mapping of the Maxio Core API. You call us, we call Maxio Core, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Maxio Core’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Maxio Core on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How does authentication to Maxio Core work through Truto?

Your end users connect their Maxio Core account through Truto's hosted auth flow or your embedded connect UI. Truto manages credential storage, refresh, and tenant isolation so you never handle Maxio secrets directly.

Which Maxio Core objects can I read and write?

You can read customers, contracts, invoices, transactions, sales orders, items, revenue entries, payment terms, billing methods, accounts, registers, reports, and more. Writes are supported for customers, contracts, invoices, transactions, sales orders, and report runs/exports.

How do I avoid writing to a closed accounting period?

Use list_all_maxio_core_close_dates and list_all_maxio_core_gl_sync_statuses before issuing updates or deletes. This lets your integration detect locked periods and gracefully skip or queue mutations against transactions and invoices that are already closed.

Can I keep an external database in sync without full re-syncs?

Yes. Maxio Core exposes dedicated feeds for deleted contracts, invoices, transactions, and revenue entries. Combined with list endpoints for the live records, you can run incremental syncs and reconcile deletes without scanning the entire dataset.

How do I pull ARR, MRR, or deferred revenue metrics?

Rather than recomputing them, trigger a report via create_a_maxio_core_report_run (or create_a_maxio_core_report_export for larger datasets) and fetch the results through the report run results and CSV endpoints. This gives you the same numbers Maxio's UI shows.

How fresh is the data Truto returns?

Truto proxies calls directly to Maxio Core's API in real time, so reads reflect current state. For high-volume use cases you can schedule polling intervals that match your product's freshness requirements and Maxio's rate limits.

Maxio Core

Get Maxio Core integrated into your app

Our team understands what it takes to make a Maxio Core integration successful. A short, crisp 30 minute call with folks who understand the problem.