AlayaCare Service Status API

Service status related endpoints.

Operations 2

POST /service/{service_id}/status Create a service status #
POST /service/by_id/{external_service_id}/status Create a service status using external client id #

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/alayacare-service-status-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

alayacare-service-status-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Patients - Clients Service Status API
  version: 1.0.18-oas3
  description: '**AlayaCare IDs:**

    The following terms are used to reference IDs that identify resources in AlayaCare:

    - client_id

    - status_id

    - contact_id


    **External IDs**

    The following terms are used to reference IDs that identify resources systems external to AlayaCare:

    - external_client_id

    - external_contact_id


    External IDs are required to be unique.

    No other assumptions are made regarding their format they are treated as strings.

    External IDs are unique to a single profile_id.


    **Profile IDs**

    The following term is used to describe a profile resource in AlayaCare:

    - profile_id


    Profile IDs can be shared across clients, contacts, and employees in the

    case that an entity shares one or more of those roles.


    **Client Status Considerations**

    - Clients can have multiple status configured depending on their business needs. Rules for configuring client status follow the internal AlayaCare application logic.

    - Updating the `status` of a client will have repercussions in the AlayaCare application.


    Please refer to this link for more information: https://alayacare.zendesk.com/hc/en-us/articles/360015538392

    '
  contact:
    name: AlayaCare
servers:
- url: '{server}/ext/api/v2/patients'
  variables:
    server:
      default: https://demo3.alayacare.ca
tags:
- name: Service Status
  description: Service status related endpoints.
paths:
  /service/{service_id}/status:
    post:
      tags:
      - Service Status
      summary: Create a service status
      operationId: createServiceStatus
      description: Creates a service status for a service by service ID.
      parameters:
      - name: service_id
        description: ID of the service
        in: path
        required: true
        schema:
          type: integer
      requestBody:
        $ref: '#/components/requestBodies/ServiceStatusCreate'
      responses:
        '201':
          description: Service status created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceStatusCreate'
        '400':
          $ref: '#/components/responses/ErrorResponseClientStatusInvalidRequest'
        '401':
          $ref: '#/components/responses/ErrorResponseAuthentication'
  /service/by_id/{external_service_id}/status:
    post:
      tags:
      - Service Status
      summary: Create a service status using external client id
      operationId: createServiceStatusByExt
      description: Creates a service status for a service by external service ID.
      parameters:
      - name: external_service_id
        description: External ID of the service
        in: path
        required: true
        schema:
          type: integer
      requestBody:
        $ref: '#/components/requestBodies/ServiceStatusCreate'
      responses:
        '201':
          description: Service status created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceStatusCreate'
        '400':
          $ref: '#/components/responses/ErrorResponseClientStatusInvalidRequest'
        '401':
          $ref: '#/components/responses/ErrorResponseAuthentication'
components:
  responses:
    ErrorResponseClientStatusInvalidRequest:
      description: Invalid request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          examples:
            response:
              value:
                code: 400
                idstatus:
                - Not a valid choice.
                message: Validation error.
    ErrorResponseAuthentication:
      description: Authorization required
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          examples:
            response:
              value:
                code: 401
                message: Authorization required.
  schemas:
    ErrorResponse:
      description: Error response
      type: object
      properties:
        code:
          type: integer
          example: 400
          description: Response code
        message:
          type: string
          example: Invalid request
          description: Detailed error message
      required:
      - code
      - message
    ServiceStatusCreate:
      type: object
      properties:
        status_id:
          type: string
          description: ID of the status
          enum:
          - active
          - on_hold
          - waiting_list
          - discharged
        upcoming_status_id:
          type:
          - integer
          - 'null'
          description: ID of the upcoming status
        status_reason:
          type:
          - string
          - 'null'
          description: Reason for the status
        status_date:
          type: string
          format: date-time
          example: '2025-02-26T04:32:10.000Z'
          description: Date of the status, set to now if not provided.
        status_end_date:
          type:
          - string
          - 'null'
          format: date-time
          description: End date of the status
      required:
      - status_id
  requestBodies:
    ServiceStatusCreate:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ServiceStatusCreate'
      required: true
  securitySchemes:
    basic_auth:
      type: http
      description: Basic HTTP auth over https
      scheme: basic