AI2Fin Travel & Vehicles API

openapi: 3.2.0
info:
  title: AI2Fin Financial Management Travel & Vehicles API
  description: Financial management platform with AI-powered categorization, tax optimization, and bill management.
  version: 1.0.0
  contact:
    name: AI2Fin Support
    url: https://ai2fin.com
  license:
    name: Proprietary
servers:
- url: https://api.ai2fin.com
  description: Production
- url: http://localhost:3001
  description: Local Development
security:
- bearerAuth: []
- cookieAuth: []
tags:
- name: Travel & Vehicles
  description: Vehicle registration and business trip tracking
paths:
  /api/vehicles:
    get:
      tags:
      - Travel & Vehicles
      summary: List vehicles
      description: Get registered vehicles for travel expense tracking
      responses:
        '200':
          description: Vehicles retrieved
      operationId: getApiVehicles
      x-operation-id-source: derived
    post:
      tags:
      - Travel & Vehicles
      summary: Register vehicle
      description: Add vehicle for ATO logbook and travel deductions
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/VehicleInput'
      responses:
        '201':
          description: Vehicle registered
      operationId: postApiVehicles
      x-operation-id-source: derived
  /api/trips:
    get:
      tags:
      - Travel & Vehicles
      summary: List trips
      description: Get recorded business trips for tax deductions
      responses:
        '200':
          description: Trips retrieved
      operationId: getApiTrips
      x-operation-id-source: derived
    post:
      tags:
      - Travel & Vehicles
      summary: Record trip
      description: Log business trip for ATO travel expense claims
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TripInput'
      responses:
        '201':
          description: Trip recorded
      operationId: postApiTrips
      x-operation-id-source: derived
components:
  schemas:
    VehicleInput:
      type: object
      required:
      - make
      - model
      - year
      - registrationNumber
      properties:
        make:
          type: string
        model:
          type: string
        year:
          type: integer
        registrationNumber:
          type: string
        businessUsePercentage:
          type: number
    TripInput:
      type: object
      required:
      - vehicleId
      - startDate
      - endDate
      - distance
      - purpose
      properties:
        vehicleId:
          type: string
        startDate:
          type: string
          format: date-time
        endDate:
          type: string
          format: date-time
        distance:
          type: number
        purpose:
          type: string
        startLocation:
          type: string
        endLocation:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: First-party access token for your own signed-in session, obtained from the /api/enterprise-auth/login endpoint. The REST API returns your own account data to you — it is a first-party consumer surface, not a third-party integration channel. Data from connected bank feeds (open-banking / CDR data) is your own data, returned only to you in your own authenticated session.
    cookieAuth:
      type: apiKey
      in: cookie
      name: ai2_sess
      description: Session cookie for web applications
    apiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: 'API key for the MCP Inspector endpoint (/mcp/inspector) only. Generate your own key via /api/api-keys. Format: mcp_<64 hex characters>. API keys carry mcp:* scopes and authenticate MCP Inspector operations — they are not accepted on the REST API (/api/...) or the main MCP endpoint (/mcp), which use OAuth bearer tokens.'