--- title: "Create a new Certificate" method: POST path: "/v2/control-planes/{controlPlaneId}/core-entities/certificates" tags: ["Certificates"] --- # Create a new Certificate `POST /v2/control-planes/{controlPlaneId}/core-entities/certificates` Create a new Certificate ## Request body - CertificateRequest - `cert` string, nullable — PEM-encoded public certificate chain of the SSL key pair. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `cert_alt` string, nullable — PEM-encoded public certificate chain of the alternate SSL key pair. This should only be set if you have both RSA and ECDSA types of certificate available and would like Kong to prefer serving using ECDSA certs when client advertises support for it. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `created_at` integer, nullable — Unix epoch when the resource was created. - `description` string, nullable — User-defined entity description. Konnect only field, not synced to the Gateway. - `id` string, nullable — A string representing a UUID (universally unique identifier). - `key` string, nullable — PEM-encoded private key of the SSL key pair. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `key_alt` string, nullable — PEM-encoded private key of the alternate SSL key pair. This should only be set if you have both RSA and ECDSA types of certificate available and would like Kong to prefer serving using ECDSA certs when client advertises support for it. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `managed_by` object, nullable — Stores information about what manages this entity, such as the tool or system responsible for its lifecycle (for example, `terraform`). Keys must be 1–63 characters long and start with an alphanumeric character. - `snis` string[], nullable - `tags` string[], nullable — An optional set of strings associated with the Certificate for grouping and filtering. - `updated_at` integer, nullable — Unix epoch when the resource was last updated. - `vault` string, nullable — Shorthand that expands into cert and key; when both vault and cert/key are provided, the vault expansion takes precedence. - `vault_alt` string, nullable — Shorthand that expands into cert_alt and key_alt; when both vault_alt and cert_alt/key_alt are provided, the vault_alt expansion takes precedence. ## Response `201` Successfully created Certificate - Certificate — A certificate object represents a public certificate, and can be optionally paired with the corresponding private key. These objects are used by Kong to handle SSL/TLS termination for encrypted requests, or for use as a trusted CA store when validating peer certificate of client/service. Certificates are optionally associated with SNI objects to tie a cert/key pair to one or more hostnames. If intermediate certificates are required in addition to the main certificate, they should be concatenated together into one string according to the following order: main certificate on the top, followed by any intermediates. - `cert` string, required — PEM-encoded public certificate chain of the SSL key pair. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `cert_alt` string, nullable — PEM-encoded public certificate chain of the alternate SSL key pair. This should only be set if you have both RSA and ECDSA types of certificate available and would like Kong to prefer serving using ECDSA certs when client advertises support for it. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `created_at` integer, nullable — Unix epoch when the resource was created. - `id` string, nullable — A string representing a UUID (universally unique identifier). - `key` string, required — PEM-encoded private key of the SSL key pair. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `key_alt` string, nullable — PEM-encoded private key of the alternate SSL key pair. This should only be set if you have both RSA and ECDSA types of certificate available and would like Kong to prefer serving using ECDSA certs when client advertises support for it. This field is _referenceable_, which means it can be securely stored as a [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started) in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format). - `snis` string[], nullable - `tags` string[], nullable — An optional set of strings associated with the Certificate for grouping and filtering. - `updated_at` integer, nullable — Unix epoch when the resource was last updated. ## Other responses - `401` — Unauthorized ## Changes - **2026-07-06** `36da5cb9a674` — 9 info - added the new optional request property `description` - added the new optional request property `managed_by` - added the new optional request property `vault` - added the new optional request property `vault_alt` - …5 more - **2025-08-22** `96118a9cd7f4` — 2 info - the request optional property `snis` became read-only - the response optional property `snis` became read-only for the status `201` - **2025-07-22** `2c77aeaee5fb` — 1 breaking, 1 info - the response property `tags` became nullable for the status `201` - the request property `tags` became nullable - **2025-04-15** `fc6abbc537f3` — 2 breaking, 6 info - the response property `created_at` became nullable for the status `201` - the response property `updated_at` became nullable for the status `201` - the request optional property `created_at` became not read-only - the request optional property `updated_at` became not read-only - …4 more - **2024-12-06** `426663331655` — 1 breaking - the request property `tags` became not nullable [Full history](https://skmtc.dev/kong/apis/konnect-api/changes/v2/control-planes/:controlPlaneId/core-entities/certificates/post.md) --- [API](https://skmtc.dev/kong/apis/konnect-api.md) · [All operations](https://skmtc.dev/kong/apis/konnect-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/kong/konnect-api/revisions/72502a676a92/schema)