Overview

Use the Timeline endpoint to retrieve the monitoring attempt history for a specific SOS monitoring request.

A monitoring attempt represents an execution of the monitoring process in which Compliancely checks the SOS source for the monitored entity.

The timeline provides an operational history of those monitoring attempts.

When Should I Use This API?

Use this endpoint when you need to answer questions such as:

• When was monitoring last attempted?
• What monitoring attempts have occurred?
• What was the status of a particular attempt?
• Did a scheduled monitoring check complete successfully?

Monitoring Attempt vs. SOS Change

A monitoring attempt does not necessarily mean that the SOS record changed.

For example:

Monitoring Attempt 1 → No change
Monitoring Attempt 2 → No change
Monitoring Attempt 3 → SOS data changed
Monitoring Attempt 4 → No change

The Timeline API represents the monitoring execution history.

Use the Versions APIs when you need to understand the SOS data history and detected changes.

Typical Usage

monitoring_id
     ↓
Timeline
     ↓
Monitoring Attempts
     ↓
Attempt status/details

Related APIs

• Get Monitoring Details — current monitoring configuration/status.
• List SOS Versions — versions associated with the monitored SOS information.
• Version Detail — differences associated with a particular version.