> ## Documentation Index > Fetch the complete documentation index at: https://docs.rootly.com/llms.txt > Use this file to discover all available pages before exploring further. # Update an escalation level > Update a specific escalation level by id ## OpenAPI ````yaml https://rootly-heroku.s3.amazonaws.com/swagger/v1/swagger.json put /v1/escalation_levels/{id} openapi: 3.0.1 info: title: Rootly API v1 version: v1 description: >+ # How to generate an API Key? - **Organization dropdown** > **Organization Settings** > **API Keys** # JSON:API Specification Rootly is using **JSON:API** (https://jsonapi.org) specification: - JSON:API is a specification for how a client should request that resources be fetched or modified, and how a server should respond to those requests. - JSON:API is designed to minimize both the number of requests and the amount of data transmitted between clients and servers. This efficiency is achieved without compromising readability, flexibility, or discoverability. - JSON:API requires use of the JSON:API media type (**application/vnd.api+json**) for exchanging data. # Authentication and Requests We use standard HTTP Authentication over HTTPS to authorize your requests. ``` curl --request GET \ --header 'Content-Type: application/vnd.api+json' \ --header 'Authorization: Bearer YOUR-TOKEN' \ --url https://api.rootly.com/v1/incidents ```
# Rate limiting - There is a default limit of **5** **GET**, **HEAD**, and **OPTIONS** calls **per API key** every **60 seconds** (0 hours). The limit is calculated over a **0-hour sliding window** looking back from the current time. While the limit can be configured to support higher thresholds, you must first contact your **Rootly Customer Success Manager** to make any adjustments. - There is a default limit of **3** **POST**, **PUT**, **PATCH** or **DELETE** calls **per API key** every **60 seconds** (0 hours). The limit is calculated over a **0-hour sliding window** looking back from the current time. While the limit can be configured to support higher thresholds, you must first contact your **Rootly Customer Success Manager** to make any adjustments. - When rate limits are exceeded, the API will return a **429 Too Many Requests** HTTP status code with the response: `{"error": "Rate limit exceeded. Try again later."}` - **X-RateLimit headers** are included in every API response, providing real-time rate limit information: - **X-RateLimit-Limit** - The maximum number of requests permitted and the time window (e.g., "1000, 1000;window=3600" for 1000 requests per hour) - **X-RateLimit-Remaining** - The number of requests remaining in the current rate limit window - **X-RateLimit-Used** - The number of requests already made in the current window - **X-RateLimit-Reset** - The time at which the current rate limit window resets, in UTC epoch seconds # Pagination - Pagination is supported for all endpoints that return a collection of items. - Pagination is controlled by the **page** query parameter ## Example ``` curl --request GET \ --header 'Content-Type: application/vnd.api+json' \ --header 'Authorization: Bearer YOUR-TOKEN' \ --url https://api.rootly.com/v1/incidents?page[number]=1&page[size]=10 ``` x-logo: url: https://rootly-heroku.s3.us-east-1.amazonaws.com/swagger/v1/logo.png servers: - url: https://api.rootly.com security: [] paths: /v1/escalation_levels/{id}: parameters: - name: id in: path required: true schema: type: string put: tags: - EscalationLevels summary: Update an escalation level description: Update a specific escalation level by id operationId: updateEscalationLevel parameters: [] requestBody: content: application/vnd.api+json: schema: $ref: '#/components/schemas/update_escalation_policy_level' required: true responses: '200': description: >- escalation policy updated with notification_target set with slack_channel_id instead of slack_channel uuid content: application/vnd.api+json: schema: $ref: '#/components/schemas/escalation_policy_level_response' '404': description: resource not found content: application/vnd.api+json: schema: $ref: '#/components/schemas/errors_list' security: - bearer_auth: [] components: schemas: update_escalation_policy_level: type: object properties: data: type: object properties: type: type: string enum: - escalation_levels attributes: type: object properties: delay: type: integer description: Delay before notifying targets in the next Escalation Level. position: type: integer description: Position of the escalation policy level escalation_policy_path_id: type: string description: >- The ID of the dynamic escalation policy path the level will belong to. If nothing is specified it will add the level to your default path. nullable: true paging_strategy_configuration_strategy: type: string enum: - default - random - cycle - alert nullable: true default: default paging_strategy_configuration_schedule_strategy: type: string enum: - on_call_only - everyone nullable: true default: on_call_only notification_target_params: type: array description: Escalation level's notification targets items: type: object properties: id: type: string description: The ID of notification target type: type: string description: The type of the notification target enum: - team - user - schedule - slack_channel - service team_members: type: string enum: - all - admins - escalate nullable: true description: >- For targets with type=team, controls whether to notify admins, all team members, or escalate to team EP. required: - id - type nullable: true additionalProperties: false required: - type - attributes required: - data escalation_policy_level_response: type: object properties: data: type: object properties: id: type: string description: Unique ID of the escalation policy level type: type: string enum: - escalation_levels attributes: type: object allOf: - $ref: '#/components/schemas/escalation_policy_level' required: - id - attributes required: - data errors_list: type: object properties: errors: type: array items: type: object properties: title: type: string status: type: string code: type: string nullable: true detail: type: string nullable: true required: - title - status escalation_policy_level: type: object properties: escalation_policy_id: type: string description: The ID of the escalation policy escalation_policy_path_id: type: string description: >- The ID of the dynamic escalation policy path the level will belong to. If nothing is specified it will add the level to your default path. nullable: true paging_strategy_configuration_strategy: type: string enum: - default - random - cycle - alert nullable: true default: default paging_strategy_configuration_schedule_strategy: type: string enum: - on_call_only - everyone nullable: true default: on_call_only delay: type: integer description: Delay before notifying targets in the next Escalation Level. position: type: integer description: Position of the escalation policy level created_at: type: string description: Date of creation updated_at: type: string description: Date of last update notification_target_params: type: array description: Escalation level's notification targets items: type: object properties: id: type: string description: The ID of notification target type: type: string description: The type of the notification target enum: - team - user - schedule - slack_channel - service team_members: type: string enum: - all - admins - escalate nullable: true description: >- For targets with type=team, controls whether to notify admins, all team members, or escalate to team EP. required: - id - type nullable: true required: - escalation_policy_id - position - delay - notification_target_params securitySchemes: bearer_auth: type: http scheme: bearer ````