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

# Get apps requestableusers

> Checks whether a user can request any resource or group inside this app, matching the App
dropdown on Opal's Access Request page. `app_id` may be a connection (native app) or an IDP
resource app (for example an Okta app). Apps are not requested directly, so the response
has no `access_levels`. Checking another user (or a requester other than the caller)
requires an Opal admin or a custom role with the CHECK_REQUESTABILITY permission; a caller
can always check their own requestability, in which case an app they cannot read is
reported as not found. Requestability does not factor visibility.




## OpenAPI

````yaml https://app.opal.dev/openapi.yaml get /apps/{app_id}/requestable/users/{user_id}
openapi: 3.1.0
info:
  contact:
    email: hello@opal.dev
    name: Opal Team
    url: https://www.opal.dev/
  description: >-
    The Opal API is a RESTful API that allows you to interact with the Opal
    Security platform programmatically.
  title: Opal API
  version: '1.0'
servers:
  - description: Production
    url: https://api.opal.dev/v1
security: []
tags:
  - name: access-rules
    description: Operations related to access rules
  - name: agent-activity
    description: Operations related to agent activity telemetry
  - name: apps
    description: Operations related to apps
  - name: bundles
    description: Operations related to bundles
  - name: campaigns
    description: Operations related to access review campaigns
  - name: configuration-templates
    description: Operations related to configuration templates
  - name: delegations
    description: Operations related to request reviewer delegations
  - name: event-streams
    description: Operations related to event streaming connections
  - name: events
    description: Operations related to events
  - name: groups
    description: Operations related to groups
  - name: group-bindings
    description: Operations related to group bindings
  - name: idp-group-mappings
    description: Operations related to IDP group mappings
  - name: message-channels
    description: Operations related to message channels
  - name: non-human-identities
    description: Operations related to non-human identities
  - name: on-call-schedules
    description: Operations related to on-call schedules
  - name: opal-queries
    description: Operations related to OpalQuery
  - name: opal-scripts
    description: Operations related to OpalScripts
  - name: owners
    description: Operations related to owners
  - name: requests
    description: Operations related to requests
  - name: resources
    description: Operations related to resources
  - name: role-assignments
    description: >-
      Operations related to role assignments (general grants between an entity
      and a principal)
  - name: paladin
    description: Operations related to Paladin
  - name: service-users
    description: Operations related to service users (non-human identities owned by a team)
  - name: sessions
    description: Operations related to sessions
  - name: tags
    description: Operations related to tags
  - name: tokens
    description: Operations related to API tokens
  - name: uars
    description: Operations related to UARs. Deprecated in favor of the `campaigns` API.
  - name: users
    description: Operations related to users
paths:
  /apps/{app_id}/requestable/users/{user_id}:
    get:
      tags:
        - apps
      description: >
        Checks whether a user can request any resource or group inside this app,
        matching the App

        dropdown on Opal's Access Request page. `app_id` may be a connection
        (native app) or an IDP

        resource app (for example an Okta app). Apps are not requested directly,
        so the response

        has no `access_levels`. Checking another user (or a requester other than
        the caller)

        requires an Opal admin or a custom role with the CHECK_REQUESTABILITY
        permission; a caller

        can always check their own requestability, in which case an app they
        cannot read is

        reported as not found. Requestability does not factor visibility.
      operationId: get_app_requestable_to_user
      parameters:
        - description: The ID of the app (connection ID or IDP resource-app ID).
          example: 32acc112-21ff-4669-91c2-21e27683eaa1
          explode: false
          in: path
          name: app_id
          required: true
          schema:
            type: string
            format: uuid
          style: simple
        - description: The ID of the user the access would be for.
          example: f92aa855-cea9-4814-b9d8-f2a60d3e4a06
          explode: false
          in: path
          name: user_id
          required: true
          schema:
            type: string
            format: uuid
          style: simple
        - description: >
            Optional ID of the person filling in the form when different from
            user_id. Adds the

            on-behalf check evaluated as that requester, following
            EnforceRequestOnBehalfOfUser.
          example: 29827fb8-f2dd-4e80-9576-28e31e9934ac
          explode: true
          in: query
          name: requester_id
          required: false
          schema:
            type: string
            format: uuid
          style: form
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserRequestabilityCheck'
          description: Whether the user can request anything in this app, and why.
        '400':
          description: Malformed UUID.
        '403':
          description: >-
            The caller is checking another user (or requester) and is not an
            Opal admin or holder of the CHECK_REQUESTABILITY permission.
        '404':
          description: The app, user_id or requester_id was not found.
      security:
        - BearerAuth: []
components:
  schemas:
    UserRequestabilityCheck:
      description: Whether an asset is requestable for a user, and why.
      example:
        resource_id: 4baf8423-db0a-4037-a4cf-f79c60cb67a5
        user_id: 29827fb8-f2dd-4e80-9576-28e31e9934ac
        requestable: true
        reason: REQUESTABLE
        access_levels:
          - access_level_remote_id: read
            access_level_name: Read
            requestable: true
      properties:
        resource_id:
          description: The ID of the resource that was checked. Set for resource checks.
          format: uuid
          type: string
        group_id:
          description: The ID of the group that was checked. Set for group checks.
          format: uuid
          type: string
        app_id:
          description: The ID of the app that was checked. Set for app checks.
          format: uuid
          type: string
        user_id:
          description: The ID of the user that was checked.
          format: uuid
          type: string
        requestable:
          type: boolean
        reason:
          $ref: '#/components/schemas/RequestabilityReasonEnum'
        access_levels:
          description: >-
            Per-access-level requestability. Omitted for apps; empty remote ID
            for assets without levels.
          type: array
          items:
            $ref: '#/components/schemas/RequestableAccessLevel'
      type: object
      required:
        - user_id
        - requestable
        - reason
    RequestabilityReasonEnum:
      description: >-
        Why an asset is or is not requestable for a user. Reasons are evaluated
        in order; the first

        that applies is returned. REQUESTABLE means at least one access level
        can be requested.
      enum:
        - ASSET_DELETED
        - REQUESTER_CANNOT_REQUEST_FOR_USER
        - UNSUPPORTED_ASSET_TYPE
        - LINKED_GROUP_NOT_REQUESTABLE
        - CONDITION_SCRIPT_FAILED
        - REQUESTS_DISABLED
        - NO_REQUESTABLE_ACCESS_LEVEL
        - NO_REQUESTABLE_ITEMS
        - REQUESTABLE
      example: REQUESTABLE
      type: string
    RequestableAccessLevel:
      description: Requestability of a single access level.
      properties:
        access_level_remote_id:
          description: >-
            The remote ID of the access level. Empty for assets without access
            levels.
          type: string
        access_level_name:
          description: The human-readable name of the access level.
          type: string
        requestable:
          type: boolean
        reason:
          $ref: '#/components/schemas/RequestabilityReasonEnum'
          description: Present when the access level is not requestable.
      type: object
      required:
        - access_level_remote_id
        - requestable
  securitySchemes:
    BearerAuth:
      scheme: bearer
      type: http

````

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