Phasio Manufacturer Post Processing Controller API
Endpoints for managing post-processing options for manufactured parts
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/phasio:phasio-manufacturer-post-processing-controller-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Phasio Manufacturer Post Processing Controller API
description: This is the API documentation for the Phasio application.
version: '1.0'
servers:
- url: https://m-api.eu.phas.io
description: Generated server url
security:
- Phasio API Bearer Token: []
tags:
- name: Manufacturer Post Processing Controller
description: Endpoints for managing post-processing options for manufactured parts
paths:
/api/manufacturer/v1/post-processing/{postProcessingId}:
get:
tags:
- Manufacturer Post Processing Controller
summary: Get post-processing by ID
description: Retrieves a specific post-processing option by its ID
operationId: get_7
parameters:
- name: postProcessingId
in: path
description: ID of the post-processing option to retrieve
required: true
schema:
type: integer
format: int64
responses:
'200':
description: Post-processing option found
content:
application/json:
schema:
$ref: '#/components/schemas/PostProcessingDto'
'404':
description: POST_PROCESSING_NOT_FOUND - Post-processing option not found
content:
application/json:
schema:
$ref: '#/components/schemas/ApiError'
components:
schemas:
PostProcessingDto:
type: object
discriminator:
propertyName: type
properties:
id:
type: integer
format: int64
type:
type: string
name:
type: string
purchasable:
type: boolean
effectiveFrom:
type: string
format: date
operationIds:
type: array
items:
type: string
format: uuid
uniqueItems: true
isDefault:
type: boolean
isDeleted:
type: boolean
colors:
type: array
items:
$ref: '#/components/schemas/ColorDto'
incompatibleMaterialIds:
type: array
items:
type: integer
format: int64
incompatibleMaterials:
type: array
items:
$ref: '#/components/schemas/MaterialDto'
mutuallyExclusiveGroup:
type: string
productionStatusIds:
type: array
items:
type: string
format: uuid
uniqueItems: true
required:
- effectiveFrom
- isDefault
- isDeleted
- name
- purchasable
- type
ApiError:
type: object
additionalProperties: true
description: Stable error contract. `error` is a SCREAMING_SNAKE code that clients match on; `message` is a human-readable sentence. Some errors add extra string fields (for example organisationId).
properties:
error:
type: string
example: ORDER_NOT_FOUND
message:
type: string
example: Order not found
required:
- error
- message
ColorDto:
type: object
properties:
id:
type: integer
format: int64
code:
type: string
name:
type: string
required:
- code
- id
- name
MaterialDto:
type: object
properties:
materialId:
type: integer
format: int64
name:
type: string
type:
type: string
required:
- materialId
- name
- type
securitySchemes:
Phasio_API_Bearer_Token:
type: http
name: Authorization
in: header
scheme: bearer
bearerFormat: JWT