# Create one or more GPG public keys in the server's configuration

Create one or more GPG public keys in the server's configuration.

Endpoint: POST /gitops/api/v1/agents/{agentIdentifier}/gpgkeys
Version: 1.0
Security: x-api-key

## Path parameters:

  - `agentIdentifier` (string, required)
    Agent identifier for entity.

## Query parameters:

  - `accountIdentifier` (string)
    Account Identifier for the Entity.

  - `orgIdentifier` (string)
    Organization Identifier for the Entity.

  - `projectIdentifier` (string)
    Project Identifier for the Entity.

## Request fields (application/json):

  - `publickey` (object)

  - `publickey.keyID` (string)

  - `publickey.fingerprint` (string)

  - `publickey.owner` (string)

  - `publickey.trust` (string)

  - `publickey.subType` (string)

  - `publickey.keyData` (string)

  - `upsert` (boolean)

## Response 200 fields (application/json):

  - `created` (object)

  - `created.metadata` (object)
    ListMeta describes metadata that synthetic resources must have, including lists and
various status objects. A resource may have only one of {ObjectMeta, ListMeta}.

  - `created.metadata.selfLink` (string)

  - `created.metadata.resourceVersion` (string)

  - `created.metadata.continue` (string)
    continue may be set if the user set a limit on the number of items returned, and indicates that
the server has more data available. The value is opaque and may be used to issue another request
to the endpoint that served this list to retrieve the next set of available objects. Continuing a
consistent list may not be possible if the server configuration has changed or more than a few
minutes have passed. The resourceVersion field returned when using this continue value will be
identical to the value in the first response, unless you have received this token from an error
message.

  - `created.metadata.remainingItemCount` (string)

  - `created.items` (array)

  - `created.items.keyID` (string)

  - `created.items.fingerprint` (string)

  - `created.items.owner` (string)

  - `created.items.trust` (string)

  - `created.items.subType` (string)

  - `created.items.keyData` (string)

  - `skipped` (array)

## Response default fields (application/json):

  - `error` (string)

  - `code` (integer)

  - `message` (string)

  - `details` (array)

  - `details.type_url` (string)
    A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
). The name should be in a canonical form
(e.g., leading "." is not accepted).

In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme , , or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:

* If no scheme is provided,  is assumed.
* An HTTP GET on the URL must yield a [google.protobuf.Type][]
  value in binary format, or produce an error.
* Applications are allowed to cache lookup results based on the
  URL, or have them precompiled into a binary to avoid any
  lookup. Therefore, binary compatibility needs to be preserved
  on changes to types. (Use versioned type names to manage
  breaking changes.)

Note: this functionality is not currently available in the official
protobuf release, and it is not used for type URLs beginning with
type.googleapis.com. As of May 2023, there are no widely used type server
implementations and no plans to implement one.

Schemes other than ,  (or the empty scheme) might be
used with implementation specific semantics.

  - `details.value` (string)
    Must be a valid serialized protocol buffer of the above specified type.