Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

GET https://youruptime/api/v1/elements/<id>/metrics/<metric>?StartDateTime=<startdatetime>&EndDateTime=<enddatetime>

Either or both StartDatetime StartDateTime and EndDatetime EndDateTime can be included. If both are included, only data points between and equal to the supplied datetimes are included. If only StateDatetime StartDateTime is included, only values from that point forward are included. If only EndDatetime EndDateTime is included, only values prior to and including are included.

...

Other response codes that may occur include the following:

Response Code

Code Description

HTTP Status Code

Details

 OK200Information retrieved successfully.
UT-1000Element Does Not Exist404

A specifically referenced Element ID does not exist.

In such a case, referencing:

https://youruptime:9997/api/v1/elements/12345

returns the following:

The element id '12345' does not exist.

The Element ID endpoint may be omitted, was inputted incorrectly, or is ignored in up.time.

UT-1010Element Filter Expired410

The referenced filter is expired. Created filters persist, by default, for five minutes.

UT-1012Element Group Filter Expired410The referenced group filter is expired. Created filters persist, by default, for five minutes.
UT-1013Invalid Element Filter400The JSON used to create an Element filter is invalid, and cannot be parsed. Check to ensure you are posting well-formed JSON.
UT-1015Invalid Element Group Filter400The JSON used to create an Element group filter is invalid, and cannot be parsed. Check to ensure you are posting well-formed JSON.
UT-1028URL ID Body Mismatch400The Element ID in the URL and the JSON object do not match.

...

FieldTypeDescription
descriptionStringdescription of this service monitor
elementIdIntegerID for this service monitor's parent Element; can return a null value for unassigned monitors
idIntegerID for this Element
isHiddenBooleanhidden monitors are internal monitors that up.time uses, and can generally be ignored
isMonitoredBooleanmonitoring status for this Element
isHostCheckBooleanreturns true if this service monitor is the host check for its parent Element
nameStringdisplay name of the service monitor
typeString

the service monitor type, typically as seen in the up.time UI

...

Other response codes that may occur include the following:

Response Code

Code Description

HTTP Status Code

Details

 OK200Information retrieved successfully.
UT-1011Monitor Filter Expired410

The referenced filter is expired. Created filters persist, by default, for five minutes.

UT-1014Invalid Monitor Filter400The referenced Element filter does not exist.

...

FieldTypeDescription
descriptionStringdescription of this service monitor
elementIdIntegerID for this service monitor's parent Element; can return a null value for unassigned monitors
idIntegerID for this Element
isHiddenBooleanhidden monitors are internal monitors that up.time uses, and can generally be ignored
isMonitoredBooleanmonitoring status for this Element
isHostCheckBooleanreturns true if this service monitor is the host check for its parent Element
isHiddenBooleanhidden monitors are internal monitors that up.time uses, and can generally be ignored
nameStringdisplay name of the service monitor
typeString

the service monitor type, typically as seen in the up.time UI

...

Other response codes that may occur include the following:

Response Code

Code Description

HTTP Status Code

Details

 OK200Information retrieved successfully.
UT-1001Monitor Does Not Exist404

A specifically referenced service monitor ID does not exist.

In such a case, referencing
https://youruptime:9997/api/v1/monitors/456/
returns the following:

The service monitor id '456' does not exist.

UT-1011Monitor Filter Expired410

The referenced filter is expired. Created filters persist, by default, for five minutes.

UT-1014Invalid Monitor Filter400The referenced Element filter does not exist.

...

FieldTypeDescription
elementIdIntegerID for this service monitor's parent Element; can be null for unassigned monitors
elementStatusObjectan object listing the status of the parent Element for this monitor
(see Element Status Object below for more detail)
idIntegerID for this service monitor
isMonitoredBooleanmonitoring Status for this service monitor
isHiddenBooleanhidden monitors are internal monitors that up.time uses, and can generally be ignored
isHostCheckBooleanreturns true if this service monitor is the host check for its parent Element
lastCheckTimeString - Date Timethe last time this service monitor was executed successfully
lastTransitionTimeString - Date Timethe last time this service monitor changed status, which can be used to determine time in its current status
messageStringoutput message produced the last time the service monitor was executed
nameStringname of this service monitor
statusStringlast known status of this service monitor

...

Other response codes that may occur include the following:

Response Code

Code Description

HTTP Status Code

Details

 OK200Information retrieved successfully.
UT-1001Monitor Does Not Exist404

A specifically referenced service monitor ID does not exist.

In such a case, referencing
https://youruptime:9997/api/v1/monitors/456/
returns the following:

The service monitor id '456' does not exist.

UT-1011Monitor Filter Expired410

The referenced filter is expired. Created filters persist, by default, for five minutes.

UT-1014Invalid Monitor Filter400The referenced Element filter does not exist.

...