> ## Documentation Index > Fetch the complete documentation index at: https://docs.agentmark.co/llms.txt > Use this file to discover all available pages before exploring further. # Link a repository and branch to an app > Persists the chosen repository + branch onto the app's existing git_connection. The next push to `branch` triggers the deploy webhook which materializes templates and datasets. Requires an existing OAuth install (returns 409 `git_connection_missing` otherwise). A repo+branch pair can be watched by only one app per organization — linking a pair already linked to another app returns 409 `repo_branch_already_linked`. Idempotent — re-linking the same repo+branch is a no-op aside from a commit_sha refresh. ## OpenAPI ````yaml /openapi.yaml post /v1/apps/{appId}/git/link openapi: 3.0.3 info: contact: email: hello@agentmark.co url: https://docs.agentmark.co description: >- The AgentMark Gateway API lets you ingest traces, create scores, and retrieve prompt templates programmatically. Most developers should use the [AgentMark SDK](/introduction/overview) for integration. The REST API is for cases where you need direct HTTP access or are building a custom integration. Versioning: every endpoint is prefixed with `/v1/`. Breaking changes ship under a new version prefix (`/v2/`, etc.) with a 90-day-minimum deprecation window — see [API versioning & stability](/api-reference/versioning) for the full policy on what constitutes a breaking vs. additive change. title: AgentMark Gateway API version: '1.0' servers: - description: Production (AgentMark Cloud) url: https://api.agentmark.co - description: Local dev server (`npx @agentmark-ai/cli dev`) url: http://localhost:9418 security: - AppId: [] BearerAuth: [] tags: - description: Ingest, query, and export OpenTelemetry trace data. name: Traces - description: List and retrieve trace sessions. name: Sessions - description: Query individual spans across traces. name: Spans - description: Create, retrieve, list, and delete score records for spans and traces. name: Scoring - description: >- Structured-filter search across observability resources, plus the machine-readable filter schema. name: Search - description: Retrieve aggregated analytics metrics. name: Metrics - description: Retrieve the effective synced project configuration. name: Config - description: List and retrieve datasets. name: Datasets - description: List and retrieve experiment results. name: Experiments - description: List prompt files and look them up by frontmatter name. name: Prompts - description: List and retrieve individual runs within experiments. name: Runs - description: Query server feature availability. name: Capabilities - description: Retrieve prompt templates by path. name: Templates - description: Per-model LLM pricing data. Public, unauthenticated. name: Pricing - description: CRUD for annotation queues — lists, create, update, delete. name: Annotation Queues - description: >- Items enqueued for review + reviewer submissions. LLM-as-judge pipelines post through the reviews endpoint. name: Annotation Queue Items - description: >- Create, list, and revoke tenant API keys. Plaintext returned exactly once at creation. name: API Keys - description: >- List and retrieve score configuration definitions from the synced project config. name: Score Configs - description: >- Trigger and inspect managed deployments. POST returns 202; deployments run asynchronously and progress is observed via GET. name: Deployments - description: >- Per-app named environments (e.g. `dev`, `prod`). CRUD for env lifecycle; promote/rollback routes land alongside in this group as feature 054 lands the saga. name: Environments - description: >- Threshold-based monitors with Slack/webhook triggers. The agent provisioning use case is the primary design target. name: Alerts - description: >- App CRUD — the top-level tenant entity every other resource hangs off. Lets a headless agent provision an app without the dashboard. name: Apps - description: Service health checks. name: Health paths: /v1/apps/{appId}/git/link: post: tags: - Apps summary: Link a repository and branch to an app description: >- Persists the chosen repository + branch onto the app's existing git_connection. The next push to `branch` triggers the deploy webhook which materializes templates and datasets. Requires an existing OAuth install (returns 409 `git_connection_missing` otherwise). A repo+branch pair can be watched by only one app per organization — linking a pair already linked to another app returns 409 `repo_branch_already_linked`. Idempotent — re-linking the same repo+branch is a no-op aside from a commit_sha refresh. operationId: link-app-repository parameters: - in: path name: appId required: true schema: format: uuid type: string requestBody: content: application/json: schema: properties: branch: description: >- Branch to watch for deploys. Must already exist on the remote. maxLength: 255 minLength: 1 type: string repository: description: >- Repository identifier in `owner/repo` form, from the `full_name` field of the repositories list. maxLength: 255 minLength: 1 type: string required: - repository - branch type: object responses: '200': content: application/json: schema: properties: data: properties: branch: type: string branch_id: format: uuid type: string commit_sha: nullable: true type: string repository: type: string required: - repository - branch - branch_id - commit_sha type: object required: - data type: object description: Repository linked. '400': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Invalid request body. '401': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Missing or invalid API key. '403': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: Caller lacks 'app.update' permission. '404': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: App not found. '409': content: application/json: schema: properties: error: properties: code: type: string message: type: string required: - code - message type: object required: - error type: object description: >- No git connection on this app yet (`git_connection_missing`), or the repo+branch is already linked to another app in this organization (`repo_branch_already_linked`). components: securitySchemes: AppId: description: Application ID for tenant scoping in: header name: X-Agentmark-App-Id type: apiKey BearerAuth: description: API key (sk_agentmark_*) scheme: bearer type: http ````