Simpro Schedules API

openapi: 3.0.3
info:
  title: Simpro REST Companies Schedules API
  description: 'The Simpro (simPRO) REST API v1.0 provides a RESTful interface to view, create, and modify resources on a Simpro Premium build - the field service, trade, and project management platform. The API is hosted on each customer''s own build, so the host is per-build (for example https://your-build.simprosuite.com) and requests are authenticated with an OAuth2 Bearer access token issued by that same build''s /oauth2/token endpoint. Most resources are nested under a company: /api/v1.0/companies/{companyID}/... where companyID is 0 on single-company builds. This document models a representative, commonly used subset of the API - companies, customers, sites, jobs, quotes, invoices, schedules, vendor orders, cost centers, stock, and webhook subscriptions. The full published API covers 300+ resource types. Endpoint paths, HTTP methods, the common list/search query parameters, and the confirmed list/read response fields are grounded in Simpro''s published API reference; request bodies for create/update are modeled minimally and marked as such, because the real payloads are large and build-configuration dependent.'
  version: '1.0'
  contact:
    name: Simpro Developer Center
    url: https://developer.simprogroup.com/
  x-access-model: Not a shared public API. Access requires an existing Simpro Premium subscription and API access enabled on that build; OAuth2 client credentials are provisioned per build by the account administrator. Base host is the customer's own build subdomain, not a single global endpoint.
servers:
- url: https://{build}.simprosuite.com/api/v1.0
  description: Per-build Simpro Premium host. Replace {build} with your build subdomain.
  variables:
    build:
      default: your-build
      description: Your Simpro Premium build subdomain - the same domain you use to log in to the Simpro staff portal (e.g. mycompany in mycompany.simprosuite.com).
security:
- oauth2: []
tags:
- name: Schedules
  description: Resource and staff scheduling records.
paths:
  /companies/{companyID}/schedules/:
    parameters:
    - $ref: '#/components/parameters/CompanyID'
    get:
      operationId: listSchedules
      tags:
      - Schedules
      summary: List all schedules
      parameters:
      - $ref: '#/components/parameters/Search'
      - $ref: '#/components/parameters/PageSize'
      - $ref: '#/components/parameters/Page'
      - $ref: '#/components/parameters/OrderBy'
      responses:
        '200':
          description: A list of schedule records.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ScheduleListItem'
        '401':
          $ref: '#/components/responses/Unauthorized'
  /companies/{companyID}/schedules/{scheduleID}:
    parameters:
    - $ref: '#/components/parameters/CompanyID'
    - $ref: '#/components/parameters/ScheduleID'
    get:
      operationId: getSchedule
      tags:
      - Schedules
      summary: Retrieve a schedule
      responses:
        '200':
          description: The requested schedule record.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ScheduleListItem'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  parameters:
    ScheduleID:
      name: scheduleID
      in: path
      required: true
      description: The schedule record's ID.
      schema:
        type: integer
    Page:
      name: page
      in: query
      required: false
      description: The page number on a paginated request.
      schema:
        type: integer
    CompanyID:
      name: companyID
      in: path
      required: true
      description: The company ID. A build with Multi-company setup may have companyID >= 0; other builds use 0 by default.
      schema:
        type: integer
        default: 0
    OrderBy:
      name: orderby
      in: query
      required: false
      description: Order of the requested records. Prefix a column name with '-' for descending order. A comma-separated list may be provided.
      schema:
        type: array
        items:
          type: string
      style: form
      explode: false
    PageSize:
      name: pageSize
      in: query
      required: false
      description: The maximum number of results to return per page.
      schema:
        type: integer
    Search:
      name: search
      in: query
      required: false
      description: Search filter. With search=all the result must match all provided fields; with search=any it may match any of them.
      schema:
        type: string
  responses:
    Unauthorized:
      description: Missing or invalid OAuth2 Bearer token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: The requested resource was not found.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    ScheduleListItem:
      type: object
      description: Modeled from the schedules resource. Verify field names against the Simpro API reference.
      properties:
        ID:
          type: integer
        Staff:
          type: object
          additionalProperties: true
        Date:
          type: string
          format: date
    Error:
      type: object
      description: Modeled error envelope. Verify the exact shape against the Simpro API reference.
      properties:
        errors:
          type: array
          items:
            type: object
            properties:
              message:
                type: string
              key:
                type: string
  securitySchemes:
    oauth2:
      type: oauth2
      description: 'OAuth2 issued by the customer''s own Simpro build. Access tokens are obtained from https://{build}.simprosuite.com/oauth2/token and sent as `Authorization: Bearer ACCESS_TOKEN`. Both the client credentials and authorization code grants are supported depending on how the API application is registered on the build.'
      flows:
        clientCredentials:
          tokenUrl: https://your-build.simprosuite.com/oauth2/token
          scopes: {}
        authorizationCode:
          authorizationUrl: https://your-build.simprosuite.com/oauth2/authorize
          tokenUrl: https://your-build.simprosuite.com/oauth2/token
          scopes: {}