> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pingintel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List Available Peril Groups

> Returns the group labels that are valid to create a new peril group with on this coverage option (i.e. labels allowed by at least one subperil's `allowed_peril_groups` that are not already in use by an existing peril group). Use with <a href="#tag/CAT/operation/api_v1_internal_submissions_coverage_options_peril_groups_create">Create a peril group</a>.



## OpenAPI

````yaml https://vision.dev.pingintel.com/api/schema/?format=json get /api/v1/submission/{pingid}/cat/coverage-options/{coverage_option_uuid}/peril-groups/available-labels
openapi: 3.0.3
info:
  title: Ping.Vision API
  version: v1.0
  description: >
    ### Ping.Vision API


    This API provides convenient, efficient access to Ping Intel's data and
    services. It is designed to be used by developers and data scientists to
    integrate Ping Intel's capabilities into their applications.


    Once SSO is set up with your organization, you can create an Organization or
    Personal API key at https://auth.pingintel.com/org.


    Please see the Python client library
    [pingintel-api](https://pypi.org/project/pingintel-api/) for commandline
    tools and programmatic access, and you

    can refer to the following documentation for details on interacting with the
    system via the HTTP API.
  contact:
    email: support@pingintel.com
    name: Ping Intel
    url: https://www.pingintel.com
servers:
  - url: https://vision.pingintel.com
    description: Ping.Vision API
  - url: https://vision.staging.pingintel.com
    description: Ping.Vision API (staging)
security: []
tags:
  - name: Create Submission
    description: The Create Submission API allows you to add new data into the system.
  - name: Update Submission
    description: >-
      The Update Submission API provides various endpoints to update, modify, or
      act upon existing submissions.
  - name: Get Submission Data
    description: ''
  - name: User Memberships
    description: >-
      The User Memberships API allows you to add, remove, and change the role of
      users in different teams, divisions, or companies.
  - name: Miscellaneous
    description: ''
paths:
  /api/v1/submission/{pingid}/cat/coverage-options/{coverage_option_uuid}/peril-groups/available-labels:
    get:
      tags:
        - CAT Modeling
      summary: List Available Peril Groups
      description: >-
        Returns the group labels that are valid to create a new peril group with
        on this coverage option (i.e. labels allowed by at least one subperil's
        `allowed_peril_groups` that are not already in use by an existing peril
        group). Use with <a
        href="#tag/CAT/operation/api_v1_internal_submissions_coverage_options_peril_groups_create">Create
        a peril group</a>.
      operationId: >-
        api_v1_submission_cat_coverage_options_peril_groups_available_labels_retrieve
      parameters:
        - in: path
          name: coverage_option_uuid
          schema:
            type: string
          required: true
        - in: path
          name: pingid
          schema:
            type: string
          required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AvailableGroupLabels'
              examples:
                Example:
                  value:
                    available_group_labels:
                      - EQ2
                      - HU2
          description: ''
      security:
        - authorization_header: []
components:
  schemas:
    AvailableGroupLabels:
      type: object
      properties:
        available_group_labels:
          type: array
          items:
            type: string
          description: >-
            Group labels not yet used on this coverage option that a subperil
            allows.
      required:
        - available_group_labels
  securitySchemes:
    authorization_header:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Supports `Token `-prefixed API keys and `Bearer `-prefixed JWT-based
        authentication.

````