openapi: 3.0.1 info: title: ilert REST Alert Actions Support Hours API description: "# Introduction\nThe ilert API is a [RESTful](https://en.wikipedia.org/wiki/Representational_state_transfer) API and provides programmatic access to entities in ilert and lets you easily integrate ilert with 3rd party tools. If you are looking to develop an inbound integration (e.g. for a monitoring tool), please use our [Events API](#tag/events). \n\nThe API supports the JSON content type for requests and responses. The response content type is requested via the HTTP Accept header (`application/json`). All resources are accessible via https and are located at `api.ilert.com/api`. \n\n You may download ilert's latest [OpenAPI.json {...} here](https://api.ilert.com/api-docs/openapi.json).\n\n If you are looking for a classic Swagger-UI view you may also open [this link](https://api.ilert.com/api-docs/swagger-ui). \n\n ## Authentication\nThe REST API accepts bearer API tokens. Each user may create API keys using the ilert web application. Note: Make sure to send the `Bearer ` prefix e.g. `Bearer APIKEY` when sending api key requests. By default, access to all resources (using any method) requires the client to be authenticated.\n\n ## Team Context\n When using API tokens, the currently selected team context of the user will not be taken into account, i.e. list results will always return all entities to which the user has a view permission. When using basic auth credentials the currently selected team context of the user will be used to filter resource results. The context may be overwritten for API key calls using the `team-context` HTTP header. Specifying `0` for ALL teams, `-1` for MY teams or a specific team id e.g. `team-context=901` to fetch results for a certain team. \n\n ## Errors\nilert uses HTTP response codes to indicate success or failure of an API request. Codes in the 2xx range indicate success, codes in the 4xx range indicate a client error (e.g. a missing required parameter) and codes in the 5xx range indicate an error with ilert's servers. In case of an error, the response body contains the following information:\n\n Attribute | Description \n ------------- | ------------- \n status | the corresponsing HTTP status code \n message | a human readable description of the error \n code | error code, used to identify error type \n\n ## API Versioning\nChanges to our API are always backwards-compatible. To get more information about our API versioning and historical changes, please take a look here." version: v2.2026.5-r.3 x-logo: url: ./ilert-logo-spaced.png backgroundColor: '#fafafa' altText: ilert documentation logo servers: - url: /api security: - apiKey: [] tags: - name: Support Hours paths: /support-hours: get: tags: - Support Hours summary: List support hours. description: Returns a shallow list of support hours without exception details. Use the single resource endpoint to retrieve the complete support hour including all exceptions. parameters: - name: start-index in: query description: an integer specifying the starting point (beginning with 0) when paging through a list of entities schema: type: integer format: int32 default: 0 - name: max-results in: query description: the maximum number of results when paging through a list of support hours. schema: maximum: 50 type: integer format: int32 default: 50 responses: '200': description: list of support hours content: application/json: schema: type: array items: $ref: '#/components/schemas/SupportHourListItem' post: tags: - Support Hours summary: Create a new support hour. requestBody: description: the support hour content: application/json: schema: $ref: '#/components/schemas/SupportHour' required: true responses: '201': description: the response content: application/json: schema: $ref: '#/components/schemas/SupportHour' x-codegen-request-body-name: support-hour /support-hours/{id}: get: tags: - Support Hours summary: Get the support hour with specified id. parameters: - name: id in: path description: entity ID required: true schema: type: number responses: '200': description: the support hour object content: application/json: schema: $ref: '#/components/schemas/SupportHour' put: tags: - Support Hours summary: Update an existing support hour. parameters: - name: id in: path description: entity ID required: true schema: type: number requestBody: description: the support hour content: application/json: schema: $ref: '#/components/schemas/SupportHour' required: true responses: '200': description: the updated support hour object content: application/json: schema: $ref: '#/components/schemas/SupportHour' x-codegen-request-body-name: support-hour delete: tags: - Support Hours summary: Delete the specified support hour. parameters: - name: id in: path description: entity ID required: true schema: type: number responses: '204': description: if deletion was successful content: {} components: schemas: TeamRel: type: object properties: id: type: integer format: int64 name: type: string SupportHourListItem: type: object properties: id: type: integer format: int64 name: type: string teams: type: array items: $ref: '#/components/schemas/TeamRel' timezone: $ref: '#/components/schemas/TimeZone' supportDays: type: object properties: MONDAY: $ref: '#/components/schemas/SupportDay' TUESDAY: $ref: '#/components/schemas/SupportDay' WEDNESDAY: $ref: '#/components/schemas/SupportDay' THURSDAY: $ref: '#/components/schemas/SupportDay' FRIDAY: $ref: '#/components/schemas/SupportDay' SATURDAY: $ref: '#/components/schemas/SupportDay' SUNDAY: $ref: '#/components/schemas/SupportDay' SupportHour: required: - name - supportDays - timezone type: object properties: id: type: integer format: int64 name: type: string teams: type: array items: $ref: '#/components/schemas/TeamRel' timezone: $ref: '#/components/schemas/TimeZone' supportDays: type: object properties: MONDAY: $ref: '#/components/schemas/SupportDay' TUESDAY: $ref: '#/components/schemas/SupportDay' WEDNESDAY: $ref: '#/components/schemas/SupportDay' THURSDAY: $ref: '#/components/schemas/SupportDay' FRIDAY: $ref: '#/components/schemas/SupportDay' SATURDAY: $ref: '#/components/schemas/SupportDay' SUNDAY: $ref: '#/components/schemas/SupportDay' exceptions: type: array items: $ref: '#/components/schemas/SupportHourException' SupportHourException: type: object required: - name - start - end - supportStatus properties: name: type: string start: type: string format: date end: type: string format: date supportStatus: type: string enum: - DURING - OUTSIDE SupportDay: required: - end - start type: object properties: start: type: string format: time end: type: string format: time TimeZone: type: string enum: - Europe/Berlin - America/New_York - America/Los_Angeles - Asia/Istanbul securitySchemes: apiKey: type: apiKey description: The Bearer API key of your user more info. name: Authorization in: header x-original-swagger-version: '2.0'