Cisco Identity Services Engine Data Access API

The Data Access API from Cisco Identity Services Engine — 2 operation(s) for data access.

Business capability
Identity & Access Management BC-620.20

Operations 5

GET /api/v1/rbac/data-access Get all data access available in Cisco ISE #
PUT /api/v1/rbac/data-access Update data access by name in Cisco ISE #
POST /api/v1/rbac/data-access Create data access in Cisco ISE #
GET /api/v1/rbac/data-access/{name} Get details of requested data access available in Cisco ISE #
DELETE /api/v1/rbac/data-access/{name} Delete data access by name in Cisco ISE #

Documentation

Specifications

Other Resources

🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/ERS-Open-API/ERS_APIs.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/TrustSec.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/policy.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/exim.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/rbac.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/deployment.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/certificates.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/upgrade.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/5G.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/alarms.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/prometheus-alertmanager.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/pxgrid-direct.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/webhooks.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/licensing.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/duo-identity-sync.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/endpoints.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/ise-profiler.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/ipsec.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/oidc.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/mfa.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/BackupRestore.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/patch-hot-patch.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/Repository.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/custom-attributes.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/data-connect.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/pxgrid-cloud.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/api-sgt-reservation.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/System-Settings.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/endpoint-replication.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/lsd-settings.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Open-API/task-service.yaml
🔗
OpenAPI Source
https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/endpoints/Monitoring-Open-API/monitoring-open-api.yaml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/cisco-ise-data-access-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

cisco-ise-data-access-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Cisco ISE API - Rbac Catalog Data Access API
  version: 1.0.0
  x-provenance:
    method: harvested
    authored_by: Cisco
    harvested_by: API Evangelist
    harvested_on: '2026-08-19'
    first_party: true
    provider_published: true
    source_host: pubhub.devnetcloud.com
    note: 103 ISE API descriptions (1,490 operations; 32 OpenAPI 3.0.x + 71 Swagger 2.0) enumerated from Cisco's own DevNet project manifest and fetched anonymously. Byte-identity reconfirmed 2026-08-19 by SHA-256 against the live source.
  x-evidence:
  - type: source
    url: https://pubhub.devnetcloud.com/media/identity-services-engine-api-v1/docs/
  - type: source
    url: https://developer.cisco.com/docs/identity-services-engine/
servers:
- url: https://10.86.189.217:443
  description: Inferred Url
tags:
- name: Data Access
paths:
  /api/v1/rbac/data-access:
    get:
      tags:
      - Data Access
      summary: Get all data access available in Cisco ISE
      description: Get data access API allows to retrieve all the data access created in Cisco ISE
      operationId: listAllDataAccess
      parameters:
      - name: page
        in: query
        description: Page number
        required: false
        style: form
        schema:
          type: integer
          format: int32
          exampleSetFlag: true
      - name: size
        in: query
        description: Number of objects returned per page
        required: false
        style: form
        schema:
          type: integer
          format: int32
          exampleSetFlag: true
      - name: sort
        in: query
        description: sort type - asc or desc
        required: false
        style: form
        schema:
          type: string
          exampleSetFlag: true
          enum:
          - asc
          - desc
      - name: sortBy
        in: query
        description: sort column by which objects needs to be sorted
        required: false
        style: form
        schema:
          type: string
          exampleSetFlag: true
      - name: filter
        in: query
        description: '<div> <style type="text/css" scoped> .apiServiceTable td, .apiServiceTable th { padding: 5px 10px !important; text-align: left; } </style> <span> <b>Simple filtering</b> should be available through the filter query string parameter. The structure of a filter is a triplet of field operator and value separated with dots. More than one filter can be sent. The logical operator common to ALL filter criteria will be by default AND, and can be changed by using the <i>"filterType=or"</i> query string parameter. Each resource Data model description should specify if an attribute is a filtered field. </span> <br /> <table class="apiServiceTable"> <thead> <tr> <th>OPERATOR</th> <th>DESCRIPTION</th> </tr> </thead> <tbody> <tr> <td>EQ</td> <td>Equals</td> </tr> <tr> <td>NEQ</td> <td>Not Equals</td> </tr> <tr> <td>GT</td> <td>Greater Than</td> </tr> <tr> <td>LT</td> <td>Less Then</td> </tr> <tr> <td>STARTSW</td> <td>Starts With</td> </tr> <tr> <td>NSTARTSW</td> <td>Not Starts With</td> </tr> <tr> <td>ENDSW</td> <td>Ends With</td> </tr> <tr> <td>NENDSW</td> <td>Not Ends With</td> </tr> <tr> <td>CONTAINS</td> <td>Contains</td> </tr> <tr> <td>NCONTAINS</td> <td>Not Contains</td> </tr> </tbody> </table> </div>'
        required: false
        style: form
        explode: true
        schema:
          type: string
          exampleSetFlag: true
      - name: filterType
        in: query
        description: The logical operator common to ALL filter criteria will be by default AND, and can be changed by using the parameter
        required: false
        style: form
        schema:
          type: string
          exampleSetFlag: true
          enum:
          - AND
          - OR
      responses:
        '200':
          description: A paged array of data access
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataAccessResponse'
                exampleSetFlag: false
        '400':
          description: Bad Request for this specified resource
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
                exampleSetFlag: false
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Not Found
      security:
      - BasicAuth: []
    put:
      tags:
      - Data Access
      summary: Update data access by name in Cisco ISE
      operationId: updateDataAccess
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DataAccessRequest'
              exampleSetFlag: false
      responses:
        '200':
          description: Updated data access successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '201':
          description: Created
        '400':
          description: Request passed is not valid
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Data access not found.
      security:
      - BasicAuth: []
    post:
      tags:
      - Data Access
      summary: Create data access in Cisco ISE
      description: Create data access API allows to create new data access in Cisco ISE
      operationId: createDataAccess
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DataAccessRequest'
              exampleSetFlag: false
      responses:
        '200':
          description: Unexpected error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '201':
          description: Added data access successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '400':
          description: Request passed is not valid
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Not Found
        '500':
          description: Internal server error
      security:
      - BasicAuth: []
  /api/v1/rbac/data-access/{name}:
    get:
      tags:
      - Data Access
      summary: Get details of requested data access available in Cisco ISE
      description: Get details of requested data access available in Cisco ISE, which has the details of all the accessible tabs
      operationId: getDataAccessByName
      parameters:
      - name: name
        in: path
        description: The name of the data access
        required: true
        style: simple
        schema:
          type: string
          exampleSetFlag: true
      responses:
        '200':
          description: Expected response to a valid request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataAccessByNameResponse'
                exampleSetFlag: false
        '400':
          description: Invalid request parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Group already exists
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
      security:
      - BasicAuth: []
    delete:
      tags:
      - Data Access
      summary: Delete data access by name in Cisco ISE
      description: Delete data access API allows to delete data access name available in Cisco ISE
      operationId: deleteDataAccess
      parameters:
      - name: name
        in: path
        description: The name of the data access
        required: true
        style: simple
        schema:
          type: string
          exampleSetFlag: true
      responses:
        '200':
          description: Data access deleted successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '204':
          description: No Content
        '400':
          description: Invalid request parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '404':
          description: Data access name not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BaseResponse'
                exampleSetFlag: false
      security:
      - BasicAuth: []
components:
  schemas:
    DataAccessPermission:
      title: DataAccessPermission
      type: object
      properties:
        childPermissions:
          type: array
          description: A list of child permissions under this data access permission, allowing nested or hierarchical permissions.
          exampleSetFlag: true
          items:
            $ref: '#/components/schemas/DataAccessPermission'
            exampleSetFlag: false
        id:
          type: string
          description: A unique identifier for the data access permission.
          exampleSetFlag: true
        name:
          type: string
          description: The name of the data access permission.
          exampleSetFlag: true
        permission:
          type: string
          description: The actual permission type (e.g., 'read', 'write', 'execute').
          exampleSetFlag: true
      description: Represents a single data access permission, with potential child permissions for hierarchical structure.
      exampleSetFlag: false
    DataAccessRequest:
      title: DataAccessRequest
      required:
      - dataAccessPrivileges
      type: object
      properties:
        dataAccessPrivileges:
          type: array
          description: A list of data access privileges associated with this request.
          exampleSetFlag: true
          items:
            $ref: '#/components/schemas/DataAccessPermission'
            exampleSetFlag: false
        description:
          type: string
          description: A description of the data access request.
          exampleSetFlag: true
        name:
          type: string
          description: The name of the data access request.
          exampleSetFlag: true
      description: Represents a request for data access, including the name, description, and associated privileges.
      exampleSetFlag: false
    BaseResponse:
      title: BaseResponse
      required:
      - code
      - message
      type: object
      properties:
        code:
          type: integer
          description: The response status code. A code of 0 typically indicates success, while non-zero codes represent errors or issues.
          format: int32
          exampleSetFlag: true
        message:
          type: string
          description: A message detailing the response, indicating success or failure.
          exampleSetFlag: true
      description: 'The `BaseResponse` object represents the standard structure for a response.  It contains a `code` indicating the success or failure of the request, and a  `message` providing additional details about the outcome. A `code` of `0` typically indicates a successful operation, whereas non-zero  values represent various types of errors or issues. '
      exampleSetFlag: false
    Error:
      title: Error
      required:
      - code
      - message
      type: object
      properties:
        code:
          type: integer
          description: The error code associated with the response. A non-zero code typically indicates an error.
          format: int32
          exampleSetFlag: true
        message:
          type: string
          description: A description of the error encountered.
          exampleSetFlag: true
      description: 'The `Error` object represents an error response. It provides information about  the error code and a message that explains the cause of the error. This object is typically returned when a request fails due to invalid input,  server issues, or other unforeseen circumstances. '
      exampleSetFlag: false
    DataAccessByNameResponse:
      title: DataAccessByNameResponse
      required:
      - code
      - message
      type: object
      properties:
        code:
          type: integer
          description: The status code of the response, indicating the success or failure of the operation.
          format: int32
          exampleSetFlag: true
        dataAccessPrivileges:
          type: array
          description: A list of data access permissions (privileges) associated with the data access.
          exampleSetFlag: true
          items:
            $ref: '#/components/schemas/DataAccessPermission'
            exampleSetFlag: false
        description:
          type: string
          description: A description of the data access object.
          exampleSetFlag: true
        message:
          type: string
          description: A message providing more details about the response.
          exampleSetFlag: true
        name:
          type: string
          description: The name of the data access object.
          exampleSetFlag: true
      description: Response schema for retrieving data access by its name, with associated privileges and description.
      exampleSetFlag: false
    DataAccessResponse:
      title: DataAccessResponse
      required:
      - code
      - message
      type: object
      properties:
        code:
          type: integer
          description: The status code of the response, indicating success or failure.
          format: int32
          exampleSetFlag: true
        dataAccessList:
          type: array
          description: A list of `DataAccess` objects representing the available data access permissions.
          exampleSetFlag: true
          items:
            $ref: '#/components/schemas/DataAccess'
            exampleSetFlag: false
        message:
          type: string
          description: A message providing more details about the response.
          exampleSetFlag: true
      description: Response schema for retrieving a list of data access objects, including status code and message.
      exampleSetFlag: false
    DataAccess:
      title: DataAccess
      required:
      - name
      type: object
      properties:
        description:
          type: string
          description: A description of the data access.
          exampleSetFlag: true
        name:
          type: string
          description: The name of the data access.
          exampleSetFlag: true
      description: Represents a simple data access object with name and description fields.
      exampleSetFlag: false