> ## Documentation Index > Fetch the complete documentation index at: https://docs.sandywp.com/llms.txt > Use this file to discover all available pages before exploring further. # Connect a Git repository for deploys > Connects a Git repository to a sandbox for deploys. Private repos need an SSH URL; add the returned `deployKeyPublic` as a deploy key on the git host. A sandbox may have only one connected repository at a time (`409 repository_limit`). Only available on account-owned (not guest) sandboxes. ## OpenAPI ````yaml /openapi.yaml post /api/app/sites/{id}/repositories openapi: 3.1.0 info: title: SandyWP API version: 0.1.0 summary: Complete supported customer API for SandyWP automation. description: > This is the complete supported customer API for automating SandyWP sandboxes, reusable Templates and Blueprints, Imports, Workspaces, account credentials, and OAuth connection setup. It is the stable HTTP contract for developer integrations; browser, provider, and operations routes on the same host are deliberately not part of this document. **Exclusions ledger.** The specification excludes guest/launcher creation (`POST /api/sites`), account profile/avatar/password/support and GitHub UI handlers, billing checkout/portal/sync, public launch routes, plugin/theme search proxies, storage, activity telemetry, newsletter, health, metrics, impersonation, Slack/GitHub callbacks, Git/Polar webhooks, all `/api/admin/**`, and all `/api/internal/**` worker or SSH-control routes. Those endpoints are browser backends, provider callbacks, or operational control-plane interfaces rather than supported developer APIs. ## Conventions - Requests and responses are JSON. Send `Content-Type: application/json` on writes (the file upload and plugin-ZIP-upload endpoints instead use `multipart/form-data`, as noted on those operations). - Sandboxes and Templates are addressed by their opaque `id` in the API (for example `site_abc123`, `tpl_xyz789`). - Errors use a consistent envelope — see the `Error` schema. Some actions require a paid plan and fail with HTTP `402` and a specific error code (for example `template_sharing_requires_paid_plan`); each is called out on the operation that returns it. - **Async by default.** Provisioning and other slow sandbox mutations happen on a worker, not inline in the HTTP request. An endpoint that starts one either returns a `jobId` to poll (see the `Job` / `JobSummary` schemas and each operation's description), returns the resource in a non-terminal state (a site `"creating"`, a Template `"building"`) to re-fetch until it settles, or both. - A personal bearer token can call the authenticated operations below. A scoped OAuth token is accepted only by `GET /api/account/me` and the Imports family; it needs `import:read` or `import:write` for the matching import operation. Other REST operations treat scoped tokens as unauthenticated. contact: name: SandyWP url: https://app.sandywp.com/docs/api servers: - url: https://app.sandywp.com security: - bearerAuth: [] tags: - name: Templates description: >- A Template is a snapshot of a finished sandbox — WordPress/PHP versions, plugins, themes, content, and database — ready to restore in seconds. Templates come from saving a ready sandbox, and can optionally be published as a public "launch this demo" link. - name: Sites description: >- A Site is a disposable WordPress sandbox: its lifecycle (create/restore/reset/delete) and the per-sandbox tools built on top of it (PHP runtime & ini config, WordPress debug settings, database access, outgoing-email capture, plugin deploys, the file manager, Git deployment, and SSH access). - name: Blueprints description: >- Reviewable WordPress build recipes that can be validated, saved, run on a sandbox, or baked into a Template. - name: Imports description: >- Archive-upload workflows for cloning a live WordPress site or pushing a local installation. Scoped OAuth tokens may use only this family, with `import:read` for reads and `import:write` for mutations. - name: Workspaces description: Workspace selection plus member and custom-role administration. - name: Account description: Identity, usage, personal API tokens, and account SSH public keys. - name: OAuth description: >- Public-client registration and PKCE authorization-code token exchange for supported connectors. paths: /api/app/sites/{id}/repositories: post: tags: - Sites summary: Connect a Git repository for deploys description: >- Connects a Git repository to a sandbox for deploys. Private repos need an SSH URL; add the returned `deployKeyPublic` as a deploy key on the git host. A sandbox may have only one connected repository at a time (`409 repository_limit`). Only available on account-owned (not guest) sandboxes. operationId: connectSiteRepository parameters: - $ref: '#/components/parameters/SiteIdParam' - $ref: '#/components/parameters/WorkspaceHeaderParam' requestBody: required: true content: application/json: schema: type: object required: - repoUrl - destination - folderName properties: repoUrl: type: string description: >- Required. `https://` URL with no embedded credentials for a public repo, or an SSH URL (`git@host:owner/repo.git` or `ssh://git@host/owner/repo.git`) for a private one — which grammar is enforced depends on `isPrivate`. example: https://github.com/you/my-plugin.git destination: $ref: '#/components/schemas/GitDeployDestination' description: >- Required. Where inside `wp-content` the repository is synced: `plugin` → `wp-content/plugins/`, `theme` → `wp-content/themes/`, `wp_content` → `wp-content/`. folderName: type: string pattern: ^[A-Za-z0-9][A-Za-z0-9._-]{0,99}$ description: >- Required. A single path segment (no slashes) under the destination — the target folder name. example: my-plugin branch: type: string pattern: ^[A-Za-z0-9][A-Za-z0-9._/-]{0,200}$ description: Branch to deploy. Defaults to `main`. isPrivate: type: boolean description: >- Whether the repo is private. When true, a per-repository SSH deploy key is generated. Defaults to false. autoDeploy: type: boolean description: >- Deploy automatically on push, via the returned `webhookUrl`. Defaults to false. responses: '200': description: The connected repository and its webhook URL. content: application/json: schema: type: object required: - repository - webhookUrl properties: repository: $ref: '#/components/schemas/GitRepository' webhookUrl: type: string format: uri description: >- One-time-shown URL (carries an opaque token) to configure as the git host's push webhook for `autoDeploy`. '400': description: >- `invalid_request` — `repoUrl`/`branch`/`folderName` fails its grammar check, or `repoUrl` doesn't match the URL shape required by `isPrivate`. content: application/json: schema: $ref: '#/components/schemas/Error' '401': $ref: '#/components/responses/Unauthorized' '403': description: >- `capability_required` — the workspace Role lacks the `integrations` capability. `git_requires_user_site` — the sandbox is guest-owned. content: application/json: schema: $ref: '#/components/schemas/Error' '404': $ref: '#/components/responses/SiteNotFound' '409': description: >- `repository_limit` — this sandbox already has a connected repository. content: application/json: schema: $ref: '#/components/schemas/Error' components: parameters: SiteIdParam: name: id in: path required: true description: The sandbox id. schema: type: string example: site_abc123 WorkspaceHeaderParam: name: X-SandyWP-Workspace in: header required: false description: >- Selects which of the caller's workspaces to act in, for accounts belonging to more than one (legacy alias: `X-SandyWP-Organization`). Defaults to the caller's own personal workspace when omitted. Every id in this API (sandboxes, Templates, repositories) is scoped to a single workspace, so this header changes which set of resources is visible. schema: type: string schemas: GitDeployDestination: type: string description: >- Where inside `wp-content` a connected repository is synced. Note the third value is `wp_content` (underscore) even though it denotes the `wp-content` folder itself. enum: - plugin - theme - wp_content GitRepository: type: object description: >- The owner-facing view of a connected Git repository. Strips the webhook secret — the plaintext webhook URL is only ever returned once, at connect time. required: - id - siteId - repoUrl - branch - destination - folderName - authKind - deployKeyPublic - autoDeploy - lastDeployedSha - createdAt - updatedAt properties: id: type: string example: repo_1 siteId: type: string repoUrl: type: string branch: type: string destination: $ref: '#/components/schemas/GitDeployDestination' folderName: type: string authKind: $ref: '#/components/schemas/GitRepoAuthKind' deployKeyPublic: type: - string - 'null' description: >- OpenSSH public key to add as a deploy key on the git host. Set only when `authKind` is `ssh`. autoDeploy: type: boolean lastDeployedSha: type: - string - 'null' createdAt: type: string format: date-time updatedAt: type: string format: date-time Error: type: object description: >- The standard error envelope returned by every endpoint on a non-2xx response. required: - error properties: error: type: object required: - code - message properties: code: type: string description: >- A stable, machine-readable error code (e.g. `invalid_request`, `site_not_found`, `plan_limit_reached`). See each operation for the codes it can return. example: invalid_request message: type: string description: A human-readable message. Safe to display to an end user. details: type: object description: >- Optional structured context (e.g. `{"plan": "free", "limit": 2}` for a plan-limit error). Omitted entirely on the generic internal-error fallback; `{}` when an error has no extra context. additionalProperties: true GitRepoAuthKind: type: string enum: - https - ssh responses: Unauthorized: description: >- No valid bearer token was presented, or a scoped OAuth token was used outside its allowed Imports and account-identity routes. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: auth_required message: A logged-in user is required. details: {} SiteNotFound: description: >- No such sandbox, or it is not visible to the caller. Ownership failures are intentionally indistinguishable from a missing sandbox. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: site_not_found message: Site not found. details: {} securitySchemes: bearerAuth: type: http scheme: bearer description: >- Personal API token, sent as `Authorization: Bearer `. Obtain one from the dashboard account menu (API keys), `sandywp auth login`, or `POST /api/account/tokens`. A missing or invalid token returns `401 auth_required`. Scoped OAuth tokens are limited to the Imports family and `GET /api/account/me`; see the top-level conventions. ````