Phasio Customer Expense Controller API

API for customers to view expenses on their orders

Operations 2

GET /api/customer/v1/expense/{expenseId} Get an expense by ID #
GET /api/customer/v1/expense/order/{orderId} Get all expenses for an order #

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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/phasio-customer-expense-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 email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

phasio-customer-expense-controller-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Phasio Activity Internal Customer Expense 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: Customer Expense Controller
  description: API for customers to view expenses on their orders
paths:
  /api/customer/v1/expense/{expenseId}:
    get:
      tags:
      - Customer Expense Controller
      summary: Get an expense by ID
      operationId: getExpense
      parameters:
      - name: expenseId
        in: path
        description: ID of the expense to retrieve
        required: true
        schema:
          type: integer
          format: int64
        example: 1
      responses:
        '200':
          description: Expense retrieved successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ExpenseDto'
        '401':
          description: Unauthorized - missing customer or operator context
        '404':
          description: Expense not found
  /api/customer/v1/expense/order/{orderId}:
    get:
      tags:
      - Customer Expense Controller
      summary: Get all expenses for an order
      operationId: getExpensesByOrder
      parameters:
      - name: orderId
        in: path
        description: ID of the order to get expenses for
        required: true
        schema:
          type: integer
          format: int64
        example: 1
      responses:
        '200':
          description: Expenses retrieved successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ExpenseDto'
        '401':
          description: Unauthorized - missing customer or operator context
components:
  schemas:
    ExpenseDto:
      type: object
      properties:
        expenseId:
          type: integer
          format: int64
        name:
          type: string
        description:
          type: string
        type:
          type: string
      required:
      - expenseId
      - name
      - type
  securitySchemes:
    Phasio_API_Bearer_Token:
      type: http
      name: Authorization
      in: header
      scheme: bearer
      bearerFormat: JWT