LogoLogo
ALO.ai
Developer Documentation
Developer Documentation
  • Developer Documentation
  • Developer Account
    • API Key
  • SDKs
    • Authentication
    • Chat
      • Configuration
      • Send Messages
        • Upload Files
      • Message History
      • Message Actions
      • Message Counts
      • Translation
      • Typing Indicators
      • API Reference
        • Event
        • Message
    • Presence
      • Configuration
      • Basic Usage
      • Methods
    • Audio
      • Prerequisites
      • Instantiating Audio Service
      • Connect to a Channel
      • Disconnecting Audio Service
      • Push To Talk (PTT)
      • Full Duplex
      • Mute and Unmute Audio
      • Input/Output Device Selection
        • Microphone Selection
        • Speaker Selection
      • Channel Participants
      • Text To Speech Audio (TTS)
      • Automatic Reconnects
      • Handling Events
      • Classes
        • AloAudio
        • AudioUser
        • AudioChannel
        • Participant
    • Video
      • Prerequisites
      • Instantiating Video Service
      • Connect to a Channel
      • Disconnecting Video Service
      • Input Device Selection
        • Microphone Selection
        • Camera Selection
      • Publishing Streams
      • Modifying Published Streams
      • Channel Participants
      • Rendering Streams
        • Local Stream
        • Remote Streams
      • Muting/Unmuting Remote Streams
      • Recording Video (coming soon)
      • Automatic Reconnects
      • Handling Events
      • Classes
        • AloVideo
        • Participant
        • VideoChannel
        • VideoUser
  • ALO APPS
    • Overview
    • Creating Apps
    • Webhooks
      • Verifying Requests from ALO
    • Custom Action Forms
    • Using the ALO Platform API
  • ALO Platform API
    • Overview
    • Authentication
    • API
      • Actions and Periods
      • Channels
      • Channel Messages
      • Channel Users
      • Direct Message Channels
      • Direct Message Channel Chat Messages
      • Direct Message Channel Users
      • Groups
      • Periods
      • Types
      • Users
      • Video Management System
  • Misc
    • Supported Language Codes
Powered by GitBook
LogoLogo

ALO.ai

  • ALO.ai

© Copyright 2025 ALO.ai, Inc. • All Rights Reserved

On this page
  • Overview
  • Get Periods
  • GET /periods
  • Query Parameters
  • Success Response
  • Get Actions for a Period
  • GET /periods/{period_id}/actions
  • Query Parameters
  • Success Response
  • Response Properties
  • Example Request
  • Example Response
  • Error Responses
  1. ALO Platform API
  2. API

Actions and Periods

Retrieve tasks, to-do items, checklists, and incidents that occur within your organization, with support for pagination.

Overview

In ALO, tasks, incidents, requests, and checklists are referred to as Actions. Actions are associated with personalizable forms; when added to your request, these form fields can also be retrieved along with Action data.

Periods are used to represent specific timeframes within your team. All dates are in UTC and follow the ISO 8601 format (e.g., 2024-01-01T01:01:00.000Z)

By specifying a Period, you can retrieve a list of Actions for your team.

Get Periods

Get all periods, optionally within a specified date range.

GET /periods

Query Parameters

Parameter
Default
Description

start_date

None

Specifies the start date for the period in ISO 8601 format (YYYY-MM-DDTHH:MM:SS.sssZ). This parameter is optional.

end_date

None

Specifies the end date for the period in ISO 8601 format (YYYY-MM-DDTHH:MM:SS.sssZ). This parameter is optional.

Success Response

A successful response will have an HTTP status of 200.

Response Properties

Property
Description

periods

A collection of period objects matching the specified date range (if specified). Dates are in ISO 8601 format and UTC.

Example Response

The sample response below shows periods retrieved successfully within a specified date range.

{
    "periods": [
        {
            "id": 1,
            "name": "Example Period",
            "start_date": "2024-07-18T18:30:00.000Z",
            "end_date": "2024-07-18T20:30:00.000Z",
            "created_at": "2024-07-18T19:26:16.624Z",
            "updated_at": "2024-07-26T06:02:03.257Z"
            "markers": {
                  "name": "Example Period Marker",
                  "timestamp":"2024-07-18T18:40:00.000Z"
        }
    ]
}

Get Actions for a Period

Get actions occurring during a period within your team. You can optionally specify form fields to include additional custom data in the action responses. All dates must be in ISO 8601 format (e.g., 2024-08-12T11:58:19.349Z) and are returned in UTC.

GET /periods/{period_id}/actions

Query Parameters

Parameter
Default
Description

form_fields

None

Optional. Specifies an array of strings representing the form fields to be included in the output. These must be URL-encoded.

The form_fields parameter allows you to request specific custom fields associated with the actions in the period. These fields should be provided as an array of strings and must be URL-encoded when included in the request. Only the fields specified will be returned in the response. If a requested field is not found for a action, a note will be included in the response under the notes property indicating which fields were missing.

Ensure that the entire array is URL-encoded when included in the request.

Example:

Array to be used: [ "department", "budget", "priority" ]

The above array, when URL-encoded, will look like this:

%5B%22department%22%2C%22budget%22%2C%22priority%22%5D

Success Response

A successful response will have an HTTP status of 200.

Response Properties

Property
Description

actions

A collection of action objects associated with the specified period. Each object includes relevant action details such as status, times, and user information. Dates are in ISO 8601 format and UTC.

Example Request

GET /periods/{period_id}/actions?form_fields=%5B%22department%22%2C%22budget%22%2C%22priority%22%5D

Example Response

The sample response below indicates that actions have been retrieved successfully. All dates are in ISO 8601 format and UTC.

{
    "actions": [
        {
            "periodId": "Example Period ID",
            "periodName": "Example Period Name",
            "periodActionId": "Example Action ID in Period",
            "actionId": "Example Action ID",
            "status": "Example Status",
            "createdTime": "2024-08-12T11:58:19.349Z",
            "createdByUserName": "Example User Name",
            "periodMarker": "Example Period Marker",
            "assignedUserNames": "Example Assigned User Names",
            "department": [
                "Maintenance"
            ],
            "budget": [
                "$5000"
            ],
            "priority": [
                "High"
            ]
        }
    ]
}

Error Responses

If there was an issue with the request, you might receive one of the following error responses:

Invalid period_id

{
    "message": "Invalid period_id. It must be a valid integer for your team."
}

Period Not Found

{
    "message": "Period not found"
}

Invalid form_fields

{
    "message": "Invalid form_fields. It must be an array of strings."
}

Internal Server Error

{
    "message": "An error occurred while processing your request"
}
PreviousAPINextChannels

Last updated 9 months ago