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

# Check Repo Access

> Can floo reach this repo, and if not, exactly why?

Answers the install question without minting a setup token or creating an
app. Authorization may complete an already observed setup intent. Causes
are distinguished only inside installations the org is authorized for;
see `_authorized_repo_access`.



## OpenAPI

````yaml https://api.getfloo.com/openapi.json get /v1/github/check-repo-access
openapi: 3.1.0
info:
  title: floo API
  version: 0.1.0
servers:
  - url: https://api.getfloo.com
security: []
paths:
  /v1/github/check-repo-access:
    get:
      tags:
        - github
      summary: Check Repo Access
      description: >-
        Can floo reach this repo, and if not, exactly why?


        Answers the install question without minting a setup token or creating
        an

        app. Authorization may complete an already observed setup intent. Causes

        are distinguished only inside installations the org is authorized for;

        see `_authorized_repo_access`.
      operationId: github_check_repo_access
      parameters:
        - name: repo
          in: query
          required: true
          schema:
            type: string
            description: Full repo name (owner/repo)
            title: Repo
          description: Full repo name (owner/repo)
        - $ref: '#/components/parameters/X-Floo-Org-Id'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GitHubRepoAccessResponse'
        default:
          description: Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearerAuth: []
components:
  parameters:
    X-Floo-Org-Id:
      name: X-Floo-Org-Id
      in: header
      required: false
      schema:
        type: string
        format: uuid
      description: Organization to act in; defaults to the one joined most recently.
  schemas:
    GitHubRepoAccessResponse:
      properties:
        accessible:
          type: boolean
          title: Accessible
        default_branch:
          anyOf:
            - type: string
            - type: 'null'
          title: Default Branch
        reason:
          $ref: '#/components/schemas/GitHubRepoAccessReason'
        install_url:
          anyOf:
            - type: string
            - type: 'null'
          title: Install Url
        settings_url:
          anyOf:
            - type: string
            - type: 'null'
          title: Settings Url
        installation_id:
          anyOf:
            - type: integer
            - type: 'null'
          title: Installation Id
      type: object
      required:
        - accessible
        - reason
      title: GitHubRepoAccessResponse
      description: Response from GET /v1/github/check-repo-access.
    ErrorResponse:
      properties:
        detail:
          $ref: '#/components/schemas/ErrorDetail'
      type: object
      required:
        - detail
      title: ErrorResponse
      description: Body of every error response except request validation (422).
    GitHubRepoAccessReason:
      type: string
      enum:
        - ok
        - app_not_installed
        - repo_not_in_installation
        - repo_not_accessible
      title: GitHubRepoAccessReason
      description: >-
        Why floo can or cannot reach a repository, as one distinguishable cause.


        `accessible: false` on its own is what made first-time setup opaque: the

        three causes below need three different actions, and collapsing them
        left

        the operator re-running an install that had already succeeded (#2293).
    ErrorDetail:
      properties:
        code:
          type: string
          title: Code
        message:
          type: string
          title: Message
      additionalProperties: true
      type: object
      required:
        - code
        - message
      title: ErrorDetail
      description: Standard error envelope with operation-specific JSON context.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: A `floo_` API key.

````

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