> ## Documentation Index > Fetch the complete documentation index at: https://docs.qumo-deploy.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a project > Creates a project in the organization. A `prod` project's credentials work on the managed relay network, which needs a paid plan; a `dev` project's work only on a relay you run yourself, and an organization has at most one. The slug used in broadcast paths is derived from the name and never changes. ## OpenAPI ````yaml /api-reference/openapi.yaml post /v1/projects openapi: 3.1.0 info: title: Qumo Deploy REST API description: > The Qumo Deploy control plane: organizations, projects, signing keys, machine identities, access control, audit and billing. Relay credentials are not issued here: your app signs them with its own [signing keys](/guides/signing-keys). Every operation here is generated against the routes the server registers and checked in CI, so an operation in this reference exists and a route missing from it is deliberately internal (relay mesh, webhooks, probes, operator-only and browser sign-in routes). Errors are JSON objects with one `error` field. What each status code means is in [Error codes](/guides/error-codes); the token scope each permission needs is in [Scopes and permissions](/guides/scopes-permissions). version: 1.0.0 servers: - url: https://api.qumo-deploy.com description: Public API (Bearer tokens only; cookies are ignored) security: [] tags: - name: Account description: The signed-in user's own sessions, tokens, security settings and data. - name: Device flow description: OAuth 2.0 device authorization, used by `qumod login`. - name: Organizations description: Organizations, their members and usage. - name: Projects description: Projects inside an organization. - name: Signing keys description: Keys your app signs relay credentials with. - name: Relays description: Where clients of a broadcast path connect. - name: Identities description: Machine identities, their tokens and IP allowlists. - name: Access control description: Roles, IAM bindings and invitations. - name: Audit description: The audit log and its webhook. - name: Notifications description: Notification policies. - name: Billing description: Plans, usage cost, budgets, invoices and payment methods. - name: Pricing description: Public price list. paths: /v1/projects: post: tags: - Projects summary: Create a project description: > Creates a project in the organization. A `prod` project's credentials work on the managed relay network, which needs a paid plan; a `dev` project's work only on a relay you run yourself, and an organization has at most one. The slug used in broadcast paths is derived from the name and never changes. operationId: createProject parameters: - $ref: '#/components/parameters/OrganizationIdQuery' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ProjectCreateRequest' responses: '201': description: The project was created. content: application/json: schema: $ref: '#/components/schemas/Project' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '402': $ref: '#/components/responses/PaymentRequired' '403': $ref: '#/components/responses/Forbidden' '409': $ref: '#/components/responses/Conflict' security: - token: [] - cliSession: [] - sessionCookie: [] csrfToken: [] components: parameters: OrganizationIdQuery: name: organization_id in: query required: false description: > The organization the request acts in. Required with a personal token or a session, which name no organization themselves; an identity token's organization is implied. schema: type: string format: uuid example: 3f8c2a1e-7b4d-4e9a-9c61-2d5e8f0a1b7c schemas: ProjectCreateRequest: type: object required: - name properties: name: type: string minLength: 1 description: Display name. The project's slug is derived from it. example: Live environment: type: string enum: - prod - dev - production - test default: prod description: | `prod` (the default) or `dev`. `production` and `test` are accepted as older names for them. example: prod Project: type: object description: >- A project inside an organization; signing keys and identities belong to one. required: - id - organization_id - name - slug - environment - created_at - suspended_at properties: id: type: string format: uuid description: The project's id. example: 9b1d6e2f-4a3c-4f8b-a7e5-0c9d2b4f6e81 organization_id: type: string format: uuid description: The organization that owns the project. example: 3f8c2a1e-7b4d-4e9a-9c61-2d5e8f0a1b7c name: type: string description: Display name. example: Live slug: type: string description: > The project's name in broadcast paths, after the organization's slug. Unique within the organization, derived from the name at creation, and unchanged when the name changes. example: live environment: type: string enum: - prod - dev description: | Which relays the project's credentials work on: `prod` on the managed relay network, `dev` on a relay you run yourself. example: prod created_at: type: string format: date-time description: When the project was created. example: '2026-09-14T08:21:37Z' suspended_at: type: - string - 'null' format: date-time description: | When Qumo took the project off the managed relays, or null. While set, credentials signed with the project's keys are refused there. example: null Error: type: object required: - error properties: error: type: string description: A human-readable message. example: organization_id is required responses: BadRequest: description: >- Malformed request or failed validation. See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' Unauthorized: description: Missing or invalid credentials. See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' PaymentRequired: description: >- The organization's plan does not include this. See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- Authenticated but not allowed (permission, token scope, IP allowlist or CSRF). See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' Conflict: description: >- Conflicts with the current state. See [Error codes](/guides/error-codes). content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: token: type: http scheme: bearer bearerFormat: qumo_pat_ description: > A personal access token (`POST /v1/auth/tokens`) or a machine identity token (`POST /v1/projects/{project_id}/identities/{identity_id}/tokens`), both prefixed `qumo_pat_`. A token's scopes cap what it can do; see [Scopes and permissions](/guides/scopes-permissions). A personal token names no organization: on a route whose path names no project or organization, pass `?organization_id=`. cliSession: type: http scheme: bearer description: | The session token `qumod login` obtains through the device flow (`POST /v1/auth/device/token`). It acts as the signed-in user, like a console session, and needs no CSRF token. sessionCookie: type: apiKey in: cookie name: __Host-qumo_session description: | The console's browser session. Accepted only on the console origin (`https://console.qumo-deploy.com`), never on `api.qumo-deploy.com`. A request that changes state must also send `X-CSRF-Token`. csrfToken: type: apiKey in: header name: X-CSRF-Token description: | CSRF token paired with `sessionCookie` on POST, PUT, PATCH and DELETE. Bearer requests do not send it. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.