> ## 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. # List signing keys > Lists the project's signing keys, active and revoked. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/projects/{id}/signing-keys 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/{id}/signing-keys: get: tags: - Signing keys summary: List signing keys description: | Lists the project's signing keys, active and revoked. operationId: listSigningKeys parameters: - name: id in: path required: true description: The project's id. schema: type: string format: uuid example: 9b1d6e2f-4a3c-4f8b-a7e5-0c9d2b4f6e81 responses: '200': description: The project's signing keys. content: application/json: schema: $ref: '#/components/schemas/SigningKeyList' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' security: - token: [] - cliSession: [] - sessionCookie: [] components: schemas: SigningKeyList: type: object required: - signing_keys properties: signing_keys: type: array items: $ref: '#/components/schemas/SigningKey' SigningKey: type: object description: A registered signing key. required: - kid - project_id - name - prefix - public_key - state - created_at - revoked_at properties: kid: type: string description: The key's RFC 7638 JWK thumbprint, the `kid` your credentials carry. example: NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs project_id: type: string format: uuid description: The project the key belongs to. example: 9b1d6e2f-4a3c-4f8b-a7e5-0c9d2b4f6e81 name: type: string description: Display name. example: api-server prefix: type: string description: > Every path a credential signed with this key grants must lie within this prefix: the project root `/`, or a narrower path under it. example: acme/live/cameras public_key: $ref: '#/components/schemas/SigningKeyPublicJwk' state: type: string enum: - active - revoked description: Whether managed relays trust the key. example: active created_at: type: string format: date-time description: When the key was registered. example: '2026-10-20T14:03:52Z' revoked_at: type: - string - 'null' format: date-time description: When the key was revoked, or null. example: null Error: type: object required: - error properties: error: type: string description: A human-readable message. example: organization_id is required SigningKeyPublicJwk: type: object description: The public half of an Ed25519 key, as a JWK (RFC 8037). required: - kty - crv - x properties: kty: type: string enum: - OKP example: OKP crv: type: string enum: - Ed25519 example: Ed25519 x: type: string description: The 32-byte public key, base64url without padding. example: 11qYAYKxCrfVS_7TyWQHOg7hcvPapiMlrwIaaPcHURo responses: Unauthorized: description: Missing or invalid credentials. 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' 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`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.