How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Phasio Customer Organisation Controller API

Endpoints for managing customer organization details

Phasio Customer Organisation Controller API is one of 92 APIs that Phasio publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customer Organisation Controller. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://m-api.eu.phas.io.

2 operations 1 paths 4 schemas 1 GET1 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://m-api.eu.phas.io/api/manufacturer/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Phasio Customer Organisation Controller API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Phasio_API_Bearer_Token). By default, every request must be authenticated.

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 PATCH. Each is listed below with its method, path, parameters, and response codes.

Customer Organisation Controller 2

Endpoints for managing customer organization details

GET
/api/customer/v1/customer-organisation
Get customer organisation
getCustomerOrganisation → 200401404
PATCH
/api/customer/v1/customer-organisation
Update customer organisation
updateCustomerOrganisation body → 200400401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CustomerAddressDto (18 properties), CustomerDto (11 properties), CustomerOrganisationDto (8 properties), UpdateCustomerOrganisationDto (2 properties). Each schema is shown below with its type and property counts.

CustomerAddressDto
object
18 properties
CustomerOrganisationDto
object
8 properties 6 required
UpdateCustomerOrganisationDto
object
Update details for the customer organisation
2 properties
CustomerDto
object
11 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

phasio-customer-organisation-controller-api-openapi.yml Raw ↑

Other APIs Phasio publishes across the network.

Phasio Activity Internal API
Phasio Addresses API
Phasio cart-resource API
Phasio constraint-resource API
Phasio Customer Activity Controller API
Phasio Customer Addresses API
Phasio Customer Analytics Controller API
Phasio Customer Assembly Controller API
Phasio Customer Authentication API
Phasio Customer Cart Controller API
Phasio Customer Cart Item Controller API
Phasio Customer Catalog Controller API
Where this information came from

This is an independent, third-party profile of Phasio Customer Organisation Controller API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.