> ## 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. # List alert routing rules > List alert routing rules. **Note: If you are an advanced alert routing user, you should use the Alert Routes endpoint instead of this endpoint. If you don't know whether you are an advanced user, please contact Rootly customer support.** ## OpenAPI ````yaml https://rootly-heroku.s3.amazonaws.com/swagger/v1/swagger.json get /v1/alert_routing_rules 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/alert_routing_rules: get: tags: - AlertRoutingRules summary: List alert routing rules description: >- List alert routing rules. **Note: If you are an advanced alert routing user, you should use the Alert Routes endpoint instead of this endpoint. If you don't know whether you are an advanced user, please contact Rootly customer support.** operationId: listAlertRoutingRules parameters: - name: include in: query required: false schema: type: string - name: page[number] in: query required: false schema: type: integer - name: page[size] in: query required: false schema: type: integer - name: filter[search] in: query required: false schema: type: string - name: filter[name] in: query required: false schema: type: string - name: filter[created_at][gt] in: query required: false schema: type: string - name: filter[created_at][gte] in: query required: false schema: type: string - name: filter[created_at][lt] in: query required: false schema: type: string - name: filter[created_at][lte] in: query required: false schema: type: string - name: sort in: query required: false schema: type: string responses: '200': description: success content: application/vnd.api+json: schema: $ref: '#/components/schemas/alert_routing_rule_list' security: - bearer_auth: [] components: schemas: alert_routing_rule_list: type: object properties: data: type: array items: type: object properties: id: type: string description: Unique ID of the alert_routing_rule type: type: string enum: - alert_routing_rules attributes: type: object allOf: - $ref: '#/components/schemas/alert_routing_rule' required: - id - type - attributes links: type: object allOf: - $ref: '#/components/schemas/links' meta: type: object allOf: - $ref: '#/components/schemas/meta' required: - data - links - meta alert_routing_rule: type: object properties: name: type: string description: The name of the alert routing rule enabled: type: boolean description: Whether the alert routing rule is enabled alerts_source_id: type: string format: uuid description: The ID of the alerts source position: type: integer description: The position of the alert routing rule for ordering evaluation condition_type: type: string description: The type of condition for the alert routing rule enum: - all - any conditions: type: array description: The conditions for the alert routing rule items: type: object properties: property_field_type: type: string description: The type of the property field enum: - attribute - payload property_field_name: type: string description: >- The name of the property field. If the property field type is selected as 'attribute', then the allowed property field names are 'summary' (for Title), 'description', 'alert_urgency' and 'external_url' (for Alert Source URL). If the property field type is selected as 'payload', then the property field name should be supplied in JSON Path syntax. property_field_condition_type: type: string description: The condition type of the property field enum: - is_one_of - is_not_one_of - contains - does_not_contain - starts_with - ends_with - matches_regex - is_empty property_field_value: type: string description: >- The value of the property field. Can be null if the property field condition type is 'is_one_of' or 'is_not_one_of' nullable: true property_field_values: type: array description: >- The values of the property field. Used if the property field condition type is 'is_one_of' or 'is_not_one_of' except for when property field name is 'alert_urgency' items: type: string required: - property_field_type - property_field_name - property_field_condition_type destination: type: object description: The destinations for the alert routing rule nullable: true properties: target_type: type: string enum: - Service - Group - Functionality - EscalationPolicy description: >- The type of the target. Please contact support if you encounter issues using `Functionality` as a target type. target_id: type: string format: uuid description: The ID of the target required: - target_type - target_id condition_groups: type: array description: The condition groups for the alert routing rule items: type: object properties: id: type: string format: uuid description: Unique ID of the condition group position: type: integer description: The position of the condition group for ordering conditions: type: array description: The conditions within this group items: type: object properties: id: type: string format: uuid description: Unique ID of the condition property_field_type: type: string description: The type of the property field enum: - attribute - payload property_field_name: type: string description: The name of the property field property_field_condition_type: type: string description: The condition type of the property field enum: - is_one_of - is_not_one_of - contains - does_not_contain - starts_with - ends_with - matches_regex - is_empty property_field_value: type: string description: The value of the property field nullable: true property_field_values: type: array description: The values of the property field items: type: string nullable: true conditionable_id: type: string format: uuid description: The ID of the conditionable object nullable: true conditionable_type: type: string description: The type of the conditionable object nullable: true created_at: type: string description: Date of creation updated_at: type: string description: Date of last update required: - property_field_type - property_field_name - property_field_condition_type created_at: type: string description: Date of creation updated_at: type: string description: Date of last update required: - position created_at: type: string description: Date of creation updated_at: type: string description: Date of last update required: - name - enabled - alerts_source_id - position - condition_type - created_at - updated_at links: type: object properties: self: type: string first: type: string prev: type: string nullable: true next: type: string nullable: true last: type: string nullable: true required: - self - first - prev - next - last meta: type: object properties: next_cursor: type: string nullable: true current_page: type: integer nullable: true next_page: type: integer nullable: true prev_page: type: integer nullable: true total_count: type: integer total_pages: type: integer required: - current_page - next_page - prev_page - total_count - total_pages securitySchemes: bearer_auth: type: http scheme: bearer ````