Manufacturer API
Connect your own systems to your Phasio organisation with the Manufacturer REST API
The Manufacturer API is the REST API for your own Phasio organisation. Use it from scripts, automations, an ERP, or a CRM to fetch and create orders, manage customers and customer organisations, query parts and part specifications, and follow production.
The interactive reference lists every endpoint with its parameters, request and response bodies, and error codes, and lets you send test requests.
Base URL
All paths start with /api/manufacturer/v1. Use the host of the region of your Phasio account.
| Region | Base URL |
|---|---|
| Europe (EU) | https://m-api.eu.phas.io/api/manufacturer/v1 |
| United States (US) | https://m-api.us.phas.io/api/manufacturer/v1 |
Authentication
The Manufacturer API authenticates with an API key. Create one in Settings > Workspace > Organisation & Security, on the API keys tab. A key starts with phasio_ and belongs to one organisation.
Send the key as a Bearer token in the Authorization header of every request:
Authorization: Bearer phasio_secret_token_hereAlways send the API key itself. A token copied from your browser is refused with 401. Keep the key on your server, never in browser code or a public repository.
Make your first request
List the orders of your organisation:
curl https://m-api.eu.phas.io/api/manufacturer/v1/order \
-H "Authorization: Bearer phasio_secret_token_here"Pagination
Paginated list endpoints take three optional query parameters:
| Parameter | Description |
|---|---|
page | Zero-based page index. Default 0. |
size | Number of items on a page. Default 20. |
sort | property,asc or property,desc. Repeat the parameter to sort by more than one property. |
curl -G https://m-api.eu.phas.io/api/manufacturer/v1/order \
-H "Authorization: Bearer phasio_secret_token_here" \
--data-urlencode "page=0" \
--data-urlencode "size=50"The response wraps the items in a page object:
| Field | Description |
|---|---|
content | The items on this page |
pageNumber | Zero-based index of this page |
pageSize | Number of items on a page |
totalElements | Number of items on all pages |
totalPages | Number of pages |
isFirst, isLast | This is the first or the last page |
isEmpty | This page has no items |
To narrow a list, add a filter. Refer to Filtering.
Errors
An error response has a JSON body with a stable error code and a message for people:
{
"error": "ORDER_NOT_FOUND",
"message": "Order not found"
}Match on error and the HTTP status in your code, not on message. Some errors add more fields.
| Status | Meaning |
|---|---|
400 | The request is not valid, for example a filter that cannot be read (INVALID_FILTER) |
401 | The API key is missing, not valid, or expired |
403 | The request is not permitted. MODULE_NOT_SUBSCRIBED means your plan does not include the module of the endpoint. |
404 | The resource does not exist |
409 | The request conflicts with the state of the resource |
429 | The API key is over its rate limit. Refer to Rate limits. |
The API enforces your plan, as the app does. For the endpoints that need Pro or Factory Floor, refer to API changes in the 31 October 2026 release.
Rate limits
Each API key can make up to 300 requests per minute.
| Authentication | Limit | Per | Period |
|---|---|---|---|
| API key | 300 | API key | 1 minute |
The allowance does not reset at the start of each minute. It refills continuously at one request every 200 ms, and unused capacity builds up to a burst of 300 requests.
Every response to a request with an API key has these headers:
| HTTP header | Description |
|---|---|
X-RateLimit-Requests-Limit | The maximum burst: 300 |
X-RateLimit-Requests-Remaining | The number of requests that you can make now |
X-RateLimit-Requests-Reset | Seconds until your full allowance is restored |
Handling rate limit errors
Over the limit, the API responds with 429 Too Many Requests. The Retry-After header gives the number of seconds until you can make your next request.
{
"error": "API_KEY_RATE_LIMITED",
"message": "API key request rate exceeded"
}To stay under the limit, use webhooks instead of polling for changes, and use a filter to fetch only the rows that you need.
Last updated on