[comment]: # ({c9539601-c9539601})
# > Maintenance object
The following objects are directly related to the `maintenance` API.
[comment]: # ({/c9539601-c9539601})
[comment]: # ({406b708d-406b708d})
### Maintenance
The maintenance object has the following properties.
|Property|[Type](/manual/api/reference_commentary#data_types)|Description|
|--------|---------------------------------------------------|-----------|
|maintenanceid|string|*(readonly)* ID of the maintenance.|
|**name**
(required)|string|Name of the maintenance.|
|**active\_since**
(required)|timestamp|Time when the maintenance becomes active.|
|**active\_till**
(required)|timestamp|Time when the maintenance stops being active.|
|description|string|Description of the maintenance.|
|maintenance\_type|integer|Type of maintenance.
Possible values:
0 - *(default)* with data collection;
1 - without data collection.|
|tags\_evaltype|integer|Problem tag evaluation method.
Possible values:
0 - *(default)* And/Or;
2 - Or.|
[comment]: # ({/406b708d-406b708d})
[comment]: # ({1449c33d-1449c33d})
### Time period
The time period object is used to define periods when the maintenance
must come into effect. It has the following properties.
|Property|[Type](/manual/api/reference_commentary#data_types)|Description|
|--------|---------------------------------------------------|-----------|
|timeperiodid|string|*(readonly)* ID of the maintenance.|
|day|integer|Day of the month when the maintenance must come into effect.
Required only for monthly time periods.|
|dayofweek|integer|Days of the week when the maintenance must come into effect.
Days are stored in binary form with each bit representing the corresponding day. For example, 4 equals 100 in binary and means, that maintenance will be enabled on Wednesday.
Used for weekly and monthly time periods. Required only for weekly time periods.|
|every|integer|For daily and weekly periods `every` defines day or week intervals at which the maintenance must come into effect.
For monthly periods `every` defines the week of the month when the maintenance must come into effect.
Possible values:
1 - first week;
2 - second week;
3 - third week;
4 - fourth week;
5 - last week.|
|month|integer|Months when the maintenance must come into effect.
Months are stored in binary form with each bit representing the corresponding month. For example, 5 equals 101 in binary and means, that maintenance will be enabled in January and March.
Required only for monthly time periods.|
|period|integer|Duration of the maintenance period in seconds.
Default: 3600.|
|start\_date|timestamp|Date when the maintenance period must come into effect.
Required only for one time periods.
Default: current date.|
|start\_time|integer|Time of day when the maintenance starts in seconds.
Required for daily, weekly and monthly periods.|
|timeperiod\_type|integer|Type of time period.
Possible values:
0 - *(default)* one time only;
2 - daily;
3 - weekly;
4 - monthly.|
[comment]: # ({/1449c33d-1449c33d})
[comment]: # ({2913a3ae-2913a3ae})
### Problem tag
The problem tag object is used to define which problems must be
suppressed when the maintenance comes into effect. It has the following
properties.
|Property|[Type](/manual/api/reference_commentary#data_types)|Description|
|--------|---------------------------------------------------|-----------|
|**tag**
(required)|string|Problem tag name.|
|operator|integer|Condition operator.
Possible values:
0 - Equals;
2 - *(default)* Contains.|
|value|string|Problem tag value.|
[comment]: # ({/2913a3ae-2913a3ae})