Skip to Content

Machine Planning, File Previews & API Key Limits

Plan Production by Machine

On the Factory Floor plan with the Scheduling module, you can now choose the machine each build runs on when you move parts into a production step, so the plan knows which printer or mill is busy and when. The production schedule has a new Machines tab that lays each machine's builds out on its own row, and the changeover rules you set per machine show as downtime between builds. Your AI assistant can read and change the same machine setups.

Preview Files Without Downloading Them

PDFs and images attached to parts and orders, and the documents Phasio generates, now open in a preview inside Phasio. You can check a drawing, a photo of a finished part or an invoice in one click, instead of downloading it and opening it in another app.

RIM Moulding

RIM Moulding is now a technology type. You can pick it when you set up a process and its pricing equation under Settings in Processes, and it shows on quotes and orders and in your AI assistant like every other technology, so shops that offer reaction injection moulding can quote it as itself instead of under a stand-in.

Manufacturer API Keys Reach More, With Clear Limits

A Manufacturer API key can now reach almost every manufacturer endpoint, including the Factory Floor endpoints, so an integration can move parts between production steps without a person signed in, and each parts move now sends the Workflow Progress Parts webhook.

The routes that move money or speak for your organisation stay with signed-in users: billing and payment accounts, connecting or disconnecting accounting, email and sending-domain settings, payment provider and Bcc settings, and creating API clients. Each key now has a rate limit of 300 requests a minute with a burst of 300, counted separately on the Manufacturer and Customer APIs, and every response tells your integration how much is left.

Clearer Docs, a New API Reference and an MCP Setup Guide

The platform docs are now organised by topic. Each feature has one topic page, grouped under sections such as Intake, Services, Production and Finances, so there is one place to read about it and to link a colleague to. Step-by-step guides such as the Starter Guide, the Pricing Guide and the template editor writing guide sit apart from the topic pages.

The developer docs have a new REST API section. Manufacturer API and Customer API explain how to connect, authenticate, page through lists, handle errors and stay within rate limits, and Filtering covers list filters. Each links to a new interactive OpenAPI reference for your region, which lists every endpoint and lets you send test requests.

MCP now has a setup guide, with the server URL for your region, steps for Claude, Claude Code, ChatGPT, Codex and Cursor, example prompts and answers to common questions.

What to Check After This Release

  • API integrations that send many requests. Read the X-RateLimit-Requests-Remaining and X-RateLimit-Requests-Reset headers, and when a request is answered 429 with API_KEY_RATE_LIMITED, wait for the Retry-After seconds before you retry. See Rate limits.
  • Lead time buffers sent through the API must now be whole hours. A decimal buffer is refused with a 400 that names the field, where it used to be rounded down.
  • APIManufacturer API list filters now accept a date-time with Z or a time zone offset, such as 2026-11-01T09:00:00+01:00, and compare it as that exact moment in UTC
  • APIListing part specifications through the Manufacturer API no longer fails with a server error when one specification has no revision. That specification is left out of the list
  • APIPricing a pre-order or a storefront cart item with a quantity below 1 is now refused with a 400 that names the quantity field
  • RegressionFixed a regression where updating a kanban column through the Manufacturer API with the older field name was refused with a 400
  • APIThe Phasio MCP server now checks where each request comes from and validates every tool's input before it runs, so a malformed save or delete from your AI assistant is refused with a clear error instead of half applied

On this page