API Keys
Create Phasio API keys so your scripts, ERP and other systems can call the Manufacturer API, and choose when each key expires.
Available to manufacturers on Startup, Pro and Factory Floor plans
An API key lets your own software, such as a script, an automation, an ERP or a CRM, call the Phasio Manufacturer REST API for your organisation. With it, an integration can fetch and create orders, manage customers and customer organisations, query parts and part specifications, and follow production. An API key starts with phasio_ and belongs to one organisation.
API keys are for systems that call Phasio. To have Phasio call your systems when something happens, use webhooks. To connect an AI client such as Claude or ChatGPT to your account, use Phasio MCP.
How it works
Your integration sends the API key as a Bearer token in the Authorization header of every request. Phasio exchanges the key for a short-lived token on each request, so you never handle tokens yourself.
curl -X GET https://m-api.eu.phas.io/api/manufacturer/v1/order \
-H "Authorization: Bearer phasio_secret_token_here"Always send the API key itself. A token copied from your browser, or one stored from Phasio's previous login system, is refused with 401.
Create an API key
- Open the user menu (your name, bottom-left) and click Settings.
- Under Workspace, click Organisation & Security. The account app opens.
- Select the API keys tab.
- Create a key for your active organisation. If you have access to more than one organisation, the key is for the one you're signed in to. See Members and roles.
- Under Expiration, choose Never expires or a date between 24 hours and 365 days ahead.
Treat an API key like a password. Store it securely, for example in your integration's environment variables, and never put it in client-side code or a public repository.
Plan modules
The API enforces your plan, as the app does. Pro and Factory Floor endpoints, such as part specifications and catalogue items (Pro) or production steps, work order dates and traveller sheets (Factory Floor), return 403 with MODULE_NOT_SUBSCRIBED when your plan doesn't include the module. The message names the missing module, and retrying gets the same answer.
Storefront credentials are different
A custom storefront doesn't use an API key. It uses storefront credentials: a client ID (sf_…) and a client secret (sfs_…) that an owner or admin creates on the Custom storefronts tab of the account app. The storefront's server uses them to get access tokens for guests and signed-in customers.
- One set of credentials works for your store only.
- You can have up to 20 active sets of credentials. Use one set for each storefront or environment.
- The client secret shows one time only. To rotate credentials, create new ones, deploy them, then revoke the old ones.
- Customer and guest access tokens last 9 hours. There is no refresh token.
- The Auth API applies rate limits for each set of credentials and for each customer.
See Storefront authentication and Customer API for the details.
Reference
- Getting started with the API: your first call and common use cases.
- Manufacturer API: base URLs, authentication, pagination, errors, rate limits, and the API reference for the EU and US regions.
- Filtering: filter list endpoints. A filter that can't be parsed returns
400withINVALID_FILTER.
Last updated on
MCP
Connect an AI client such as Claude or ChatGPT to your Phasio account over the Model Context Protocol to review your setup and draft pricing equations and document templates.
Webhooks
Send real-time notifications to your ERP, CRM or automation when orders, quotes, customers, part specifications and carts change in Phasio.