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

> ## Agent Instructions
> Treat Stackdome as an application-delivery platform for coding agents and developers, not as a Kubernetes dashboard.
> Prefer the Stackdome agent plugin as the user entry point and the stackdome CLI as the execution interface.
> Route agents who need the maintained deploy skill to npx skills add stackdome/skills and the complete operational workflow to /guides/ai-agents.
> Verify commands and flags with stackdome --help. Run stackdome init before authoring stackfile.yaml and stackdome validate before deploying.
> Use -o json for automation and verify documented terminal states before claiming success.
> Never request a user's account password. Use API-token authentication.
> During alpha, Stackdome Cloud is ephemeral and capacity-limited, and each organization can connect one cluster.
> Do not expose Kubernetes as a user concern unless the task is self-hosting or infrastructure architecture.

# Start the GitHub App manifest flow for the organization



## OpenAPI

````yaml /openapi.yaml post /api/v1/organizations/{org_id}/git-integrations/github/manifest
openapi: 3.0.0
info:
  description: >-
    Deploy, debug, and operate applications through the Stackdome REST API on
    Stackdome Cloud or a self-hosted installation. This API is in alpha and may
    change before general availability.
  title: Stackdome API
  version: 0.0.1-alpha
servers:
  - url: /
security: []
paths:
  /api/v1/organizations/{org_id}/git-integrations/github/manifest:
    post:
      summary: Start the GitHub App manifest flow for the organization
      parameters:
        - description: The ID of the organization
          explode: false
          in: path
          name: org_id
          required: true
          schema:
            type: string
          style: simple
      responses:
        '201':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GitHubAppManifestFlow'
          description: Manifest flow started
        '400':
          description: The hub external URL is not configured
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
        '409':
          description: A GitHub App is already installed
        '500':
          description: Internal server error
      security:
        - Bearer: []
components:
  schemas:
    GitHubAppManifestFlow:
      example:
        github_url: github_url
        manifest:
          key: ''
        state: state
      properties:
        manifest:
          additionalProperties: true
          description: >-
            GitHub App manifest to POST to github_url as the manifest form
            field. Absent when the hub runs a platform-wide GitHub App:
            github_url is then the app's install page and the browser is
            redirected to it.
          type: object
        github_url:
          type: string
        state:
          type: string
      type: object
  securitySchemes:
    Bearer:
      bearerFormat: JWT
      scheme: bearer
      type: http

````