Loading article…
Loading article…
Last updated on Aug 28, 2026
Plan an integration before anyone writes code: what it connects, what has to happen inside it, and which of the four approaches below fits. Everything here is aimed at scoping the work rather than implementing it, so you can hand a clear brief to whoever builds it.
Four approaches cover almost every integration need, from installing something Maxio already built to commissioning custom work. Read all four before committing to one, since the right choice depends on whether you have developers available and whether a native integration already covers your case.
Advanced Billing offers a handful of native integrations. Start here, because a native integration needs no design work at all.
Most common
Additional
(Optional) If you bill for metered usage, your integration needs to send that usage into Advanced Billing. See Get Started with Maxio Metering.
(Optional) This approach suits developers, especially those who already know what they want to build. For the webhook and API building blocks to design against, see Core Resources for Building an Integration.
Important: Maxio points you to the right documented resources, such as Advanced Billing webhooks and API endpoints, but does not write code for you.
(Optional) This approach suits non-developers who want to build integrations without writing code. For the iPaaS comparison and scoping tables, see Core Resources for Building an Integration.
Important: Maxio does not build, debug, maintain, or support anything you or a developer builds with an iPaaS. Depending on your plan, Maxio can help you determine which Advanced Billing webhooks and API endpoints to use.
Does Maxio build integrations as a professional service?
No. Maxio is a product company rather than a custom-services company.
I don't have developers, but I need something built. What is the best approach?
Use an iPaaS (Integration Platform as a Service). Zapier and Cyclr are the two Maxio documents. See Core Resources for Building an Integration for a side-by-side comparison of cost, capability, and scope.
To see worked Zapier and Cyclr examples once you have chosen an approach, see Building Integrations and Workflows with iPaaS.
To see code-level workflow examples built on the API and webhooks, see Building Workflows with APIs and Webhooks.
Still need help?
Reach out and our support team will take it from here.