Esper Pipelines Stages API

openapi: 3.2.0
info:
  title: ESPER API REFERENCE Pipelines Stages API
  x-logo:
    url: esper-logo-white.svg
    backgroundColor: '#141418'
    altText: Logo
  description: '# Introduction

    Welcome to Esper’s API documentation. The Esper API allows users to accomplish operations outside of the console. Some common uses for our APIs include observing device information and console activity, installing and updating apps, uploading files, and sending files to devices. Our users have also used the API to automate app updates, perform bulk actions, and more. Esper API endpoints use REST-based architecture and return JSON responses. See our documentation for:


    * Getting started guides

    * Commonly used API examples

    * API command examples

    * Automated Script examples

    * And more


    # Authentication


    You need to create an API Key to interact with our APIs. Learn more about generating an API Key. You can also learn more about Esper and sign up for an account at esper.io/signup. Some endpoints also require an Enterprise ID. This ID can be found in the API Management section of the Esper console. # Lifecycle Labels


    Esper uses lifecycle labels to communicate the support status of each API endpoint. Use the following table to understand what each label means and how to respond. Badge

    What it means

    Recommended action


    Stable

    This endpoint is fully supported and safe for production use. No action needed. Beta

    This endpoint is publicly available but may change. It is not recommended for production integrations. Use with caution. Monitor the API changelog for updates before relying on this endpoint. Legacy

    This endpoint uses an older architecture and is still supported, but a newer equivalent exists. It is not recommended for new integrations. Plan migration to the recommended replacement when possible. See the endpoint description for the alternative. Deprecated

    This endpoint has stopped being supported. A removal date may be added at a later time. A replacement is available or the feature is entirely retired. Migrate before the removal date listed in the endpoint description. Do not use this endpoint in new integrations. # Pagination


    Responses may be paginated. Use the following parameters to query the data. A full list of parameters can be found on the endpoint’s documentation page. Parameter

    Data Type

    Explanation


    limit

    integer

    Limit the data returned. Default = 20. offset

    integer

    Offset to the first item returned. Default = 0. ordering

    string

    Order the results set by the field name. Varies by endpoint. next

    string

    Paginate to the next response set. previous

    string

    Paginate to the last set response. # Errors

    We use standard HTTP status codes for success or failure. A typical error response may look something like this:


    ```json

    {

    "errors": [],

    "message": "error message",

    "status": 400

    }

    ```

    * `errors` - List of error details

    * `message` - Error description

    * `status` - HTTP status code


    Some common status codes and messages are:


    Number

    Message

    Explanation


    200

    OK

    The request succeeded. 201

    Resource creation

    A resource was created. 401

    Unauthorized

    The API key is invalid. 404

    Not found

    The resource was not found. 429

    Rate limit exceeded

    Too many requests. Wait a moment and try again. 500

    Server error

    Internal error. Wait a moment and try again. If the issue persists, contact Esper. See how our systems are doing by checking our status page. # Rate Limits

    To ensure quality of service for all customers, we enforce rate limits for API requests. Most customers won’t hit this limit with normal use. In case you experience 429 or rate limit exceeded errors, we recommend the following:

    * Try sending requests in batches. * Begin with about 20 requests at a time and building up from there. * Ensure your scripts are efficient and don’t contain redundant calls. * Reach out to your account manager to discuss your options.'
  termsOfService: https://esper.io/terms-of-service
  contact:
    email: developer@esper.io
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  version: 1.0.0
  x-prefix-tag: esper cloud api
servers:
- url: https://{foo}-api.esper.cloud/api
  variables:
    foo:
      default: develop
      description: Custom end point
tags:
- name: pipelines_Stages
  description: APIs to modify Stage information
  x-displayName: Stages
paths:
  /pipelines/v0/pipelines/{pipeline_id}/stages/:
    get:
      x-badges:
      - name: Stable
        color: green
      summary: Get all Pipeline stages
      description: 'Retrieves all Stages configured for a Pipeline.


        Returns a paginated list of Stage objects belonging to the specified pipeline, in the order they run; use this to inspect a pipeline''s structure before triggering or editing it.


        **About Stages**


        A Stage is an ordered step within a Pipeline. Each Stage has Target Lists (defining which devices or Device Groups it targets) and Operation Lists (the actions it performs), and when a Pipeline Run executes, each Stage produces one Stage Run.'
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: getPipelineStages
      tags:
      - pipelines_Stages
      parameters:
      - name: pipeline_id
        in: path
        description: ID of the Pipeline
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Pipelines stages response
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    type: object
                    properties:
                      count:
                        type: integer
                      previous:
                        type: string
                      next:
                        type: string
                      results:
                        type: array
                        items:
                          $ref: '#/components/schemas/pipelines_Stage'
    post:
      x-badges:
      - name: Stable
        color: green
      summary: Create a Pipeline stage
      description: 'Adds a new Stage to a Pipeline.


        Send a POST request with the Stage''s details to append a new ordered step to the pipeline; the response returns the created Stage object, which you then attach Target Lists and Operation Lists to.


        **About Stages**


        A Stage represents one ordered step in a Pipeline''s execution. A newly created Stage has no Target Lists or Operation Lists attached by default, so a Stage Run produced from it would be marked INVALID (no targets or no operations) until those are added.


        **Workflow**


        1. Create the Stage

        2. Attach one or more Target Lists (directly or via Device Groups) to define which devices it targets

        3. Attach one or more Operation Lists to define what actions it performs'
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: createPipelineStage
      tags:
      - pipelines_Stages
      parameters:
      - name: pipeline_id
        in: path
        description: ID of the Pipeline
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/pipelines_Stage_POST'
      responses:
        '200':
          description: Pipelines stages create response
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    $ref: '#/components/schemas/pipelines_Stage'
        '400':
          description: Stage create error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipelines_Error_400_Bad_Data'
  /pipelines/v0/pipelines/{pipeline_id}/stages/{stage_id}/:
    get:
      x-badges:
      - name: Stable
        color: green
      summary: Get a Pipeline Stage
      description: 'Retrieves the details of a single Pipeline Stage by ID.


        Returns the full Stage object for the specified pipeline and stage; use this to inspect a specific step''s configuration within a pipeline''s execution order.


        **About Stages**


        A Stage is one ordered step within a Pipeline, holding the Target Lists (devices and/or Device Groups) and Operation Lists (actions) that run when the pipeline is executed.'
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: getPipelineStage
      tags:
      - pipelines_Stages
      parameters:
      - name: pipeline_id
        in: path
        description: ID of the Pipeline
        required: true
        schema:
          type: string
      - name: stage_id
        in: path
        description: ID of the Stage
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Pipelines stage get response
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    $ref: '#/components/schemas/pipelines_Stage'
    put:
      x-badges:
      - name: Stable
        color: green
      summary: Update a Pipeline Stage
      description: 'Updates the details of an existing Pipeline Stage.


        Send a PUT request with the updated Stage fields to modify a step in the pipeline; the response returns the updated Stage object.


        **About Stages**


        A Stage is one ordered step in a Pipeline. Its own configuration is managed separately from the Target Lists and Operation Lists attached to it, which are updated through their own dedicated endpoints.'
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: updatePipelineStage
      tags:
      - pipelines_Stages
      parameters:
      - name: pipeline_id
        in: path
        description: ID of the Pipeline
        required: true
        schema:
          type: string
      - name: stage_id
        in: path
        description: ID of the Stage
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/pipelines_Stage_PUT'
      responses:
        '200':
          description: Updated Stage Information
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    $ref: '#/components/schemas/pipelines_Stage'
        '400':
          description: Stage update error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipelines_Error_400_Bad_Data'
        '401':
          description: Stage update error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipelines_Error_401_Unauthorized'
    delete:
      x-badges:
      - name: Stable
        color: green
      summary: Delete a pipeline stage
      description: 'Deletes a Stage from a Pipeline.


        Permanently removes the specified Stage, along with its association to any attached Target Lists and Operation Lists, from the pipeline; the response returns the deleted Stage object.


        **About Stages**


        A Stage is one ordered step in a Pipeline''s execution, containing the Target Lists and Operation Lists that define what devices it targets and what actions it runs as part of the pipeline''s overall orchestration flow.'
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: deletePipelineStage
      tags:
      - pipelines_Stages
      parameters:
      - name: pipeline_id
        in: path
        description: ID of the Pipeline
        required: true
        schema:
          type: string
      - name: stage_id
        in: path
        description: ID of the Stage
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Deleted Stage Information
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    $ref: '#/components/schemas/pipelines_Stage'
        '401':
          description: Stage delete error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipelines_Error_401_Unauthorized'
  /pipelines/v0/stages/{stage_id}/targetlists/:
    get:
      description: 'Retrieves all Target Lists currently attached to a Pipeline stage.


        Returns the Target Lists linked to the specified stage, which determine which devices or device groups the stage will act on when the pipeline runs.


        **About Stage Target Lists**

        Pipelines orchestrate multi-step device operations through Stages, each of which executes against one or more Target Lists (collections of devices or device groups). Attaching a Target List to a Stage is what tells that step of the pipeline which devices to target.


        **Key Fields / Query Parameters**

        - `stage_id` — UUID of the Stage whose attached Target Lists you want to retrieve

        - `type` — Optional query filter to scope the returned Target Lists by type'
      x-badges:
      - name: Stable
        color: green
      summary: Get all Target Lists attached to the Stage
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: getStageTargetLists
      tags:
      - pipelines_Stages
      parameters:
      - name: stage_id
        in: path
        description: ID of the Stage
        required: true
        schema:
          type: string
          format: uuid
      - in: query
        name: type
        schema:
          type: string
          enum:
          - groups
          - devices
          - collections
      responses:
        '200':
          description: All Targets Lists attached to the Stage
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    type: object
                    properties:
                      count:
                        type: integer
                      previous:
                        type: string
                      next:
                        type: string
                      results:
                        type: array
                        items:
                          $ref: '#/components/schemas/pipelines_TargetList'
        '401':
          description: Target List get error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipelines_Error_401_Unauthorized'
    post:
      description: 'Attaches an existing Target List to a Pipeline stage.


        Links a Target List (identified by target_list_id) to the specified stage, so that the stage will act on the devices or device groups contained in that list when the pipeline runs.


        **About Stage Target Lists**

        Pipelines orchestrate multi-step device operations through Stages, each of which executes against one or more Target Lists. This endpoint is how a Target List that already exists on the pipeline gets scoped to a specific stage.


        **Key Fields / Query Parameters**

        - `stage_id` — UUID of the Stage to attach the Target List to

        - `target_list_id` — Required — UUID of an existing Target List to attach'
      x-badges:
      - name: Stable
        color: green
      summary: Attach the Target List to the Stage
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: addStageTargetList
      tags:
      - pipelines_Stages
      parameters:
      - name: stage_id
        in: path
        description: ID of the Stage
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/pipelines_StageTargetList_POST'
      responses:
        '200':
          description: Attach target list to a Stage
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    $ref: '#/components/schemas/pipelines_TargetList'
        '401':
          description: Target list attach error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipelines_Error_401_Unauthorized'
  /pipelines/v0/stages/{stage_id}/targetlists/{targetlist_id}/:
    delete:
      description: 'Detaches a Target List from a Pipeline stage.


        Removes the association between the specified Target List and stage; the Target List itself is not deleted, only its attachment to this stage.


        **About Stage Target Lists**

        Detaching a Target List from a stage changes which devices that stage acts on for future pipeline runs — it does not affect runs that have already executed, and the Target List remains available to attach elsewhere.


        **Key Fields / Query Parameters**

        - `stage_id` — UUID of the Stage

        - `targetlist_id` — UUID of the Target List to detach from the stage'
      x-badges:
      - name: Stable
        color: green
      summary: Detach the Target List from the Stage
      security:
      - pipelines_SCAPIAuthToken: []
      operationId: deleteStageTargetList
      tags:
      - pipelines_Stages
      parameters:
      - name: stage_id
        in: path
        description: ID of the Stage
        required: true
        schema:
          type: string
      - name: targetlist_id
        in: path
        description: ID of the Target List
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Detach target list from stage
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                  message:
                    type: string
                  content:
                    $ref: '#/components/schemas/pipelines_TargetList'
        '401':
          description: Target list attach error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/pipelines_Error_401_Unauthorized'
components:
  schemas:
    pipelines_TargetList:
      type: object
      properties:
        id:
          type: string
          readOnly: true
        pipeline_id:
          type: string
        name:
          type: string
        target_list_type:
          type: string
        created_by:
          type: number
          format: int32
        updated_by:
          type: number
          format: int32
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    pipelines_Error_401_Unauthorized:
      type: object
      properties:
        code:
          type: integer
          format: int32
          default: 401
        message:
          type: string
        content:
          type: object
      required:
      - code
      - message
    pipelines_Stage:
      type: object
      properties:
        id:
          type: string
          readOnly: true
        enterprise_id:
          type: string
          readOnly: true
        pipeline_id:
          type: string
        description:
          type: string
        name:
          type: string
        timeout_seconds:
          type: number
          format: int32
        created_by:
          type: number
          format: int32
        updated_by:
          type: number
          format: int32
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    pipelines_StageTargetList_POST:
      type: object
      properties:
        target_list_id:
          type: string
          format: uuid
      required:
      - target_list_id
    pipelines_Stage_POST:
      type: object
      properties:
        name:
          type: string
        description:
          type: string
        timeout_seconds:
          type: number
          format: int32
      required:
      - name
    pipelines_Stage_PUT:
      type: object
      properties:
        name:
          type: string
        description:
          type: string
        timeout_seconds:
          type: number
          format: int32
    pipelines_Error_400_Bad_Data:
      type: object
      properties:
        code:
          type: integer
          format: int32
          default: 400
        message:
          type: string
        content:
          type: object
      required:
      - code
      - message
  securitySchemes:
    esper_cloud_api_apiKey:
      type: http
      scheme: bearer
      description: "#### API KEY - Access Token\nAccess token for API is passed as authorization header in calls. You need to generate this from your Esper Console at `<domain>-api.esper.cloud` where foo is the sub-domain name you gave for your Esper Dev environment when you signed up for your Esper account. Please follow the instructions [in this Help article](https://help.esper.io/hc/en-us/articles/12656959508497) to generate an access token.\nOnce you have the access token, you need to send an authorization header as below\n\n```bash\n\n    curl -X GET \\\n      https://<domain>-api.esper.cloud/api/enterprise/<enterprise_id>/device/ \\\n      -H 'Authorization: Bearer <ACCESS_TOKEN>' \\\n      -H 'Content-Type: application/json' \\\n```\n\n> Please note the use of keyword **Bearer** before the token value.\n\n\nYou can read more about api key authentication [here](https://help.esper.io/hc/en-us/articles/12656959508497).\n"
    pipelines_SCAPIAuthToken:
      type: http
      scheme: bearer
    device_apiKey:
      type: http
      scheme: bearer
      description: "#### API KEY - Access Token\nAccess token for API is passed as authorization header in calls. You need to generate this from your Esper Console at `<domain>-api.esper.cloud` where foo is the sub-domain name you gave for your Esper Dev environment when you signed up for your Esper account. Please follow the instructions [in this Help article](https://help.esper.io/hc/en-us/articles/12656959508497) to generate an access token.\nOnce you have the access token, you need to send an authorization header as below\n\n```bash\n\n    curl -X GET \\\n      https://<domain>-api.esper.cloud/api/enterprise/<enterprise_id>/device/ \\\n      -H 'Authorization: Bearer <ACCESS_TOKEN>' \\\n      -H 'Content-Type: application/json' \\\n```\n\n> Please note the use of keyword **Bearer** before the token value.\n\n\nYou can read more about api key authentication [here](https://help.esper.io/hc/en-us/articles/12656959508497).\n"
    apps_management_apiKey:
      type: http
      scheme: bearer
      description: "#### API KEY - Access Token\nAccess token for API is passed as authorization header in calls. You need to generate this from your Esper Console at `<domain>-api.esper.cloud` where foo is the sub-domain name you gave for your Esper Dev environment when you signed up for your Esper account. Please follow the instructions [in this Help article](https://help.esper.io/hc/en-us/articles/12656959508497) to generate an access token.\nOnce you have the access token, you need to send an authorization header as below\n\n```bash\n\n    curl -X GET \\\n      https://<domain>-api.esper.cloud/api/enterprise/<enterprise_id>/device/ \\\n      -H 'Authorization: Bearer <ACCESS_TOKEN>' \\\n      -H 'Content-Type: application/json' \\\n```\n\n> Please note the use of keyword **Bearer** before the token value.\n\n\nYou can read more about api key authentication [here](https://help.esper.io/hc/en-us/articles/12656959508497).\n"
    commands_apiKey:
      type: http
      scheme: bearer
      description: "#### API KEY - Access Token\nAccess token for API is passed as authorization header in calls. You need to generate this from your Esper Console at `<domain>-api.esper.cloud` where foo is the sub-domain name you gave for your Esper Dev environment when you signed up for your Esper account. Please follow the instructions [in this Help article](https://help.esper.io/hc/en-us/articles/12656959508497) to generate an access token.\nOnce you have the access token, you need to send an authorization header as below\n\n```bash\n\n    curl -X GET \\\n      https://<domain>-api.esper.cloud/api/enterprise/<enterprise_id>/device/ \\\n      -H 'Authorization: Bearer <ACCESS_TOKEN>' \\\n      -H 'Content-Type: application/json' \\\n```\n\n> Please note the use of keyword **Bearer** before the token value.\n\n\nYou can read more about api key authentication [here](https://help.esper.io/hc/en-us/articles/12656959508497).\n"
    drift_apiKey:
      type: http
      scheme: bearer
      description: "#### API KEY - Access Token\nAccess token for API is passed as authorization header in calls. You need to generate this from your Esper Console at `<domain>-api.esper.cloud` where foo is the sub-domain name you gave for your Esper Dev environment when you signed up for your Esper account. Please follow the instructions [in this Help article](https://help.esper.io/hc/en-us/articles/12656959508497) to generate an access token.\nOnce you have the access token, you need to send an authorization header as below\n\n```bash\n\n    curl -X GET \\\n      https://<domain>-api.esper.cloud/api/enterprise/<enterprise_id>/device/ \\\n      -H 'Authorization: Bearer <ACCESS_TOKEN>' \\\n      -H 'Content-Type: application/json' \\\n```\n\n> Please note the use of keyword **Bearer** before the token value.\n\n\nYou can read more about api key authentication [here](https://help.esper.io/hc/en-us/articles/12656959508497).\n"
    device_onboarding_apiKey:
      type: http
      scheme: bearer
      description: "#### API KEY - Access Token\nAccess token for API is passed as authorization header in calls. You need to generate this from your Esper Console at `<domain>-api.esper.cloud` where foo is the sub-domain name you gave for your Esper Dev environment when you signed up for your Esper account. Please follow the instructions [in this Help article](https://help.esper.io/hc/en-us/articles/12656959508497) to generate an access token.\nOnce you have the access token, you need to send an authorization header as below\n\n```bash\n\n    curl -X GET \\\n      https://<domain>-api.esper.cloud/api/enterprise/<enterprise_id>/device/ \\\n      -H 'Authorization: Bearer <ACCESS_TOKEN>' \\\n      -H 'Content-Type: application/json' \\\n```\n\n> Please note the use of keyword **Bearer** before the token value.\n\n\nYou can read more about api key authentication [here](https://help.esper.io/hc/en-us/articles/12656959508497).\n"
    tenant_apiKey:
      type: http
      scheme: bearer
      description: "#### API KEY - Access Token\nAccess token for API is passed as authorization header in calls. You need to generate this from your Esper Console at `<domain>-api.esper.cloud` where foo is the sub-domain name you gave for your Esper Dev environment when you signed up for your Esper account. Please follow the instructions [in this Help article](https://help.esper.io/hc/en-us/articles/12656959508497) to generate an access token.\nOnce you have the access token, you need to send an authorization header as below\n\n```bash\n\n    curl -X GET \\\n      https://<domain>-api.esper.cloud/api/enterprise/<enterprise_id>/device/ \\\n      -H 'Authorization: Bearer <ACCESS_TOKEN>' \\\n      -H 'Content-Type: application/json' \\\n```\n\n> Please note the use of keyword **Bearer** before the token value.\n\n\nYou can read more about api key authentication [here](https://help.esper.io/hc/en-us/articles/12656959508497).\n"
    foundation_AuthToken:
      type: apiKey
      in: header
      name: Authorization
    reports_bearerAuth:
      type: http
      scheme: bearer
    geofence_bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
x-tagGroups:
- name: ESPER CLOUD API
  tags:
  - esper_cloud_api_Company Settings
  - esper_cloud_api_Application
  - esper_cloud_api_Application V1
  - esper_cloud_api_AndroidDevice
  - esper_cloud_api_Device Group
  - esper_cloud_api_Token (Deprecated)
  - esper_cloud_api_Commands V2
  - esper_cloud_api_Enterprise Policy
  - esper_cloud_api_Geofence
  - esper_cloud_api_Content
  - esper_cloud_api_User (Deprecated)
  - esper_cloud_api_User
  - esper_cloud_api_Blueprint (Deprecated)
  - esper_cloud_api_Directory Record
  - esper_cloud_api_Tile Icon
  - esper_cloud_api_Alerts
  - esper_cloud_api_Alarms
  - esper_cloud_api_Wallpapers
  - esper_cloud_api_Device Telemetry
  - esper_cloud_api_Daily and Custom Reports
  - esper_cloud_api_SSO Connections
  - esper_cloud_api_Roles
  - esper_cloud_api_Personal Access Token
- name: BLUEPRINTS
  tags:
  - blueprints_Blueprints API
  - blueprints_Custom Actions API
  - blueprints_Background Scripts API
- name: PIPELINES
  tags:
  - pipelines_System Status Code
  - pipelines_System
  - pipelines_Pipelines
  - pipelines_Stages
  - pipelines_Target Lists
  - pipelines_Targets
  - pipelines_Device Groups
  - pipelines_Operation Lists
  - pipelines_Operations
  - pipelines_Pipeline Runs
  - pipelines_Stage Runs
  - pipelines_Target Runs
- name: DEVICE
  tags:
  - device_Device
  - device_Device Heartbeat
  - device_Device Apps
  - device_Device Enrollment in EMM
  - device_Operations
  - device_DeviceOperations
  - device_MultiOS Remote Viewer
- name: APPS MANAGEMENT
  tags:
  - apps_management_VPP License Management
  - apps_management_VPP App Management
  - apps_management_Tenant Apps
  - apps_management_Apple App Store
  - apps_management_App List
  - apps_management_Webclips
  - apps_management_Provisioning Profiles
  - apps_management_Preferred Regions
  - apps_management_OEM Config Schema
  - apps_management_Esper Apps
  - apps_management_Tenant Esper Apps
- name: COMMANDS
  tags:
  - commands_Command Request
  - commands_Command Status
- name: DRIFT
  tags:
  - drift_Converge
  - drift_Converge Command
  - drift_Blueprint Drift
- name: DEVICE ONBOARDING
  tags:
  - device_onboarding_DEP Sync Request
  - device_onboarding_ABM Provisioning
- name: TENANT
  tags:
  - tenant_APNs certificate
  - tenant_DEP Profile
  - tenant_DEP Tokens
  - tenant_VPP Token Management
  - tenant_Google Enterprise
  - tenant_MDM Service Config
- name: FOUNDATION
  tags:
  - foundation_FoundryBuilds
  - foundation_FoundryDeviceModels
  - foundation_FoundryEvents
- name: REPORTS
  tags:
  - reports_Reports API
- name: GEOFENCE
  tags:
  - geofence_Geofences
  - geofence_Device State
x-provenance:
  method: harvested
  publisher: Esper
  source: https://api.esper.io/_bundle/openapi.json?download
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)