git.deploy-keys.list

List deploy keys

GET /git/api/repositories/{repoId}/deploy-keysIAM git:ListDeployKeysRead

Request syntax

GET /git/api/repositories/{repoId}/deploy-keys

Path parameters

  • repoIdRequired

    string

    Constraints: uuid

Response

200 with the keys: id, name, publicKey, fingerprint, readOnly, lastUsedAt and createdAt.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Fields of data

  • [].​idAlways

    string

    The key's id
  • [].​orgIdAlways

    string

    Your organization
  • [].​repoIdAlways

    string

    The repository the record belongs to
  • [].​nameAlways

    string

    The name the key was given
  • [].​publicKeyAlways

    string

    The OpenSSH public key line
  • [].​fingerprintAlways

    string

    The key's SHA256 fingerprint, as `ssh-keygen -l` shows it
  • [].​readOnlyAlways

    boolean

    true: clone and fetch only; false: it may push too
  • [].​lastUsedAtAlways

    string, may be null

    When the key last opened the repository (ISO 8601); null when never
  • [].​createdAtAlways

    string

    When the key was added (ISO 8601)

Checked against the handlers: every route test validates their answers against this schema.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow git:ListDeployKeys on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud git deploy-keys list repoId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_deploy-keys_list.