> ## 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 Zone Schemes

> Whether the submission can have zone sets, and the zone schemes new zone sets can be created from: post a scheme's `name` as the `zone_scheme` of `POST .../zone-sets`, and show its `label`. Comes from the submission's policy terms config, so it doesn't need a coverage option.



## OpenAPI

````yaml https://vision.pingintel.com/api/schema/?format=json get /api/v1/submission/{pingid}/cat/zone-schemes
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: Get Submission Data
    description: >-
      The Get Submission Data API lets you list and look up submissions, track
      their events, download their documents, and generate or retrieve their
      outputs.
  - name: Update Submission
    description: >-
      The Update Submission API provides various endpoints to update, modify, or
      act upon existing submissions.
  - name: CAT Modeling
    description: >-
      The CAT Modeling API manages catastrophe modeling setup for a submission:
      coverage options, peril groups, layer structures, and modeling options. It
      also generates Acc/Loc files for CAT models.
  - 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: Reference Data
    description: >-
      The Reference Data API lists lookup values used by other endpoints, such
      as the submission statuses available to a division.
  - name: Account
    description: >-
      The Account API returns information about the authenticated user: their
      identity, permissions, and sitewide settings.
paths:
  /api/v1/submission/{pingid}/cat/zone-schemes:
    get:
      tags:
        - CAT Modeling
      summary: List Zone Schemes
      description: >-
        Whether the submission can have zone sets, and the zone schemes new zone
        sets can be created from: post a scheme's `name` as the `zone_scheme` of
        `POST .../zone-sets`, and show its `label`. Comes from the submission's
        policy terms config, so it doesn't need a coverage option.
      operationId: api_v1_submission_cat_zone_schemes_retrieve
      parameters:
        - in: path
          name: pingid
          schema:
            type: string
          required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ZoneSchemes'
              examples:
                Example:
                  value:
                    enable_zone_sets: true
                    available_zone_schemes:
                      - name: zone_scheme:everest:v1
                        label: Everest
          description: ''
      security:
        - authorization_header: []
components:
  schemas:
    ZoneSchemes:
      type: object
      properties:
        available_zone_schemes:
          type: array
          items:
            $ref: '#/components/schemas/AvailableZoneScheme'
          readOnly: true
        enable_zone_sets:
          type: boolean
          description: >-
            Whether users can create zone sets: the config allows them and
            settings.ENABLE_ZONE_SETS is on.
          readOnly: true
      required:
        - available_zone_schemes
        - enable_zone_sets
    AvailableZoneScheme:
      type: object
      properties:
        label:
          type: string
        name:
          type: string
      required:
        - label
        - name
  securitySchemes:
    authorization_header:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Supports `Token `-prefixed API keys and `Bearer `-prefixed JWT-based
        authentication.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.