---
title: "Data feed for schedule occurrences"
method: GET
path: "/scheduling/v1/feed/schedule_occurrences"
tags: ["Data Feeds"]
---

# Data feed for schedule occurrences

`GET /scheduling/v1/feed/schedule_occurrences`

## Request

- Base URL: `https://api.mitti.com`
- URL: `https://api.mitti.com/scheduling/v1/feed/schedule_occurrences`
- Auth: HTTP bearer

## Query parameters

- `limit` integer
- `template` string[]
- `start_date` string, date-time
- `end_date` string, date-time
- `next_page_token` string
- `include_entity_names` boolean

## Response `200`

A successful response.

- S12SchedulingFeedV1FeedScheduleOccurrencesResponse: The response for `FeedScheduleOccurrences` V2
  - `metadata` S12CommonV1FeedMetadataSimple: FeedMetadataSimple for a feed.
    - `next_page` string: Full path to retrieve the next page of results, including the next_page_token.
    - `next_page_token` string: The value you can use to retrieve additional results. If a value exists, it means there are more results than listed. Use the value in your request body as a page_token to view more results.
  - `data` S12SchedulingFeedV1FeedScheduleOccurrence[]: The flat list of schedule occurrence records.
    - `id` string: Identifier for this schedule occurrence. Format: `scheduleitem_{schedule UUID}_occurrence_{due_time in epoch milliseconds}_{assignee_id}` Example: `scheduleitem_123_occurrence_1705338000000_user_789`. A schedule for several sites or assets returns one record per site or asset with the same `id`; use `id` with `target_id` as the unique key.
    - `schedule_id` string: ID of the schedule that generated this occurrence. References a schedule from the FeedSchedules endpoint, which returns the same UUID with the `scheduleitem_` prefix.
    - `occurrence_id` string: ID of the specific occurrence within the schedule's recurrence pattern. Each occurrence represents one instance of the scheduled inspection. • A sequence number per schedule target; it restarts for each `target_id`.
    - `template_id` string: ID of the template used for inspections created from this occurrence. References the inspection template that will be used.
    - `start_time` string: When the occurrence becomes available for inspection (ISO 8601 timestamp format; for example, `2024-01-15T09:00:00Z`).
    - `due_time` string: Final deadline (ISO 8601 timestamp format; for example, `2024-01-15T17:00:00Z`). After this time, the occurrence is missed and cannot be completed. For schedules with an overdue period, this comes after `miss_time`.
    - `miss_time` string: When this occurrence becomes overdue (ISO 8601 timestamp format). • Present only if an overdue period configured; otherwise omitted. • Between `miss_time` and `due_time`, unfinished occurrences are `OVERDUE`. • It is `null` if an overdue period is not configured.
    - `occurrence_status` string: Current status of this scheduled occurrence as a whole, the same on every record of the occurrence. See `assignee_status` for the status of this record's assignee. • `TODO`: Not started. • `IN_PROGRESS`: Inspection has been started but not completed. • `COMPLETED`: Inspection has been finished on time. • `LATE`: Inspection has been finished after the `miss_time` but before `due_time`. • `OVERDUE`: Past `miss_time` but before `due_time`; not started. • `MISSED`: Past `due_time` and has not been completed. • `WONT_DO`: Intentionally skipped; `wont_do_note` is mandatory for this status. Only in `assignee_status`.
    - `audit_id` string: ID of the inspection created from this occurrence. • Present when the `assignee_status` is `IN_PROGRESS`, `COMPLETED` or `LATE`. • It is `null` for occurrences that haven't been started yet. • Use this ID to fetch full inspection details from inspection APIs.
    - `completed_at` string: When this occurrence was marked as completed (ISO 8601 timestamp format). • Present only when `assignee_status` is `COMPLETED`, `LATE` or `WONT_DO`. • It is `null` for incomplete occurrences.
    - `completion_rule` string: Completion requirement for the occurrence. One of: `any` (at least one assignee must complete) or `all` (every assignee must complete).
    - `organisation_id` string: ID of the organization that owns the occurrence.
    - `wont_do_note` string: Reason provided when marking occurrence as `won't do`. • Only populated when `assignee_status` is `WONT_DO`. • Contains the explanation for why the occurrence was skipped.
    - `assignee_id` string: ID of the user assigned to complete this occurrence. • Group, role and site assignments are expanded to one record per user; `assignee_from` says how the user was assigned. • Use with FeedScheduleAssignees to get assignee details.
    - `assignee_from` string: Original assignment source that generated this individual occurrence. • Format: `{type}_{id}` where type is user, group, role, or location. • Examples: `user_xxx`, `role_yyy`, `location_zzz` • A site and group intersection is `location_zzz+role_yyy`. • For past occurrences, it is the user who did the work. • Shows how this specific assignee was determined from the schedule's assignment rules.
    - `target_id` string: ID of the site or asset this occurrence is for. A schedule for several sites or assets has one record per site or asset. • UUID of the site or asset; `target_type` says which. • Empty when the schedule has no sites or assets.
    - `target_type` string: Type of `target_id`. One of: `SITE` or `ASSET`. Empty when `target_id` is empty.
    - `completed_by_user_id` string: ID of the user who completed the inspection of this record's assignee (`assignee_id`). • Present when `assignee_status` is `COMPLETED` or `LATE`. • Can differ from `assignee_id` when another user completed the inspection. • It is `null` when this assignee's inspection has not been completed.
    - `assignee_status` string: Status of this record's assignee (`assignee_id`) for the occurrence. Uses the same values as `occurrence_status`. • `occurrence_status` is the status of the occurrence as a whole, taking `completion_rule` into account. • `assignee_status` is the status of this assignee's own work. For example, with `all`, one assignee can be `COMPLETED` while another is `TODO` and the occurrence is `IN_PROGRESS`.
    - `assignee_name` string: Name of the `assignee_id` user. Returned when `include_entity_names` is `true`. • Empty when the user can't be found.
    - `assignee_from_names` string[]: Names of the user, site or group in `assignee_from`, in the same order as its parts. Returned when `include_entity_names` is `true`. • `user_xxx`: the user's name, for example `["Ada Lovelace"]`. • `location_zzz`: the site's name, for example `["Sydney"]`. • `role_yyy`: the group's name, for example `["Cleaners"]`. • `location_zzz+role_yyy`: the site's and the group's names, for example `["Sydney", "Cleaners"]`. • A name is empty when the user, site or group can't be found, for example after it was deleted.
    - `completed_by_user_name` string: Name of the `completed_by_user_id` user. Returned when `include_entity_names` is `true`. • It is `null` when `completed_by_user_id` is `null`. • Empty when the user can't be found.
    - `target_name` string: Name of the `target_id` site, or code of the `target_id` asset. Returned when `include_entity_names` is `true`. • Empty when `target_id` is empty, or the site or asset can't be found.

## Other responses

- `default`: An unexpected error response.

## Changes

- **2026-11-03** `eb6bb843bf18`: 9 info
  - added the new optional `query` request parameter `include_entity_names`
  - added the optional property `data/items/assignee_from_names` to the response with the `200` status
  - added the optional property `data/items/assignee_name` to the response with the `200` status
  - added the optional property `data/items/assignee_status` to the response with the `200` status
  - …5 more

[Operation history](https://skmtc.dev/safetyculture/apis/safetyculture-api/changes/scheduling/v1/feed/schedule_occurrences/get.md)

---

[API](https://skmtc.dev/safetyculture/apis/safetyculture-api.md) - [All operations](https://skmtc.dev/safetyculture/apis/safetyculture-api/llms.txt) - [OpenAPI document](https://skmtc.dev/safetyculture/apis/safetyculture-api/revisions/eb6bb843bf18?raw)
