Connect Phasio to Your Existing Tools with the API and Webhooks

Most manufacturers running a service bureau don't start from scratch. They already have an accounting system, a CRM, maybe an ERP they've spent years configuring. The question isn't whether to replace those tools. It's how to connect them to where your orders, quotes, and production actually live.

Phasio's REST API and webhooks are built for exactly that. You can sync orders, customers, and production data between Phasio and the tools you already rely on, without rebuilding your stack or managing duplicate records by hand.

Arthur Kopp, founder and managing director of KIT3D in Germany, a 3D printing service bureau running MJF, SLS, SLA, and FDM, called the API his favourite feature.

"It lets you connect so many different tools with Phasio, whether it's an external accounting system or an external CRM platform." - Arthur Kopp, KIT3D

GETTING STARTED

Phasio's manufacturer API uses an API key sent as a Bearer token. Create the key in Developers and use the API base URL documented for your deployment. Webhooks send encrypted notifications for supported events, including order creation and updates, quote conversion, customer organisation changes, part specification creation, and cart creation.

Use the developer setup guide for authentication and API references: https://docs.phas.io/developers

WHAT CHANGES FROM DAY ONE

Here are the workflows manufacturers are already running through the API:

• Syncing orders to an ERP. Use the Orders API to fetch orders on a schedule, or subscribe to the Order Created webhook to push data across in real time. Either way, you're not re-entering order details manually across two systems.
• Importing customers from a CRM. The Customer Organisation API lets you create and manage customer accounts in Phasio. If a customer already exists in your CRM, push them into Phasio rather than maintaining two separate records.
• Pulling quote and part data into reporting tools. The Part Specification and Part Revision APIs expose part details and pricing. If you want to feed quote data into a custom dashboard or external reporting tool, this is the starting point.
• Tracking production progress externally. The Production Step API lets you monitor where each job sits in your production workflow from outside Phasio. Useful if you're building ops dashboards or feeding status data into another system your team uses.

For KIT3D, the API was central to how Arthur and his team kept the whole operation visible.

"For me, as managing director, it's extremely important to keep our processes clear and transparent across the entire company." - Arthur Kopp, KIT3D

WHY IT MATTERS

When your quoting tool, accounting system, and production workflow are all disconnected, someone on your team is spending time on data entry instead of production. That's not a tools problem. It's an integration problem.

The API lets your team connect systems that would otherwise require repeated data entry. Your integration must map identifiers, choose the relevant events, and handle delivery failures. The webhook documentation specifies a five-second timeout and no automatic retry of failed deliveries, so critical synchronisation needs a recovery or reconciliation process.

"We've actually been using Phasio since day one, and we really need Phasio for our entire internal workflow, not just for production control itself." - Arthur Kopp, KIT3D

Start with the developer guide and the documented webhook events: https://docs.phas.io/developers/webhooks

API authentication and reference

Webhook events and delivery behaviour