Assign Endpoint Certificate
Override the TLS certificate served on an endpoint that uses a custom domain. By default the platform serves a Let's Encrypt cert it manages itself (auto-renewed via ACME); this endpoint lets you swap in a certificate you've uploaded via POST /v1/certificates/self instead.
Restricted to custom-domain endpoints only (the linked domain must be one you own — shared domains always use platform-managed certs). Also gated behind the custom_ssl entitlement on your plan.
Set use_default: true (or omit certificate_uuid) to revert to the auto-managed cert. The previous custom certificate row is detached but not deleted from your library — it's still available to assign to another endpoint.
Path parameters
Request body
uuid of a certificate from /certificates/assignable. This is one of your uploaded certificates, or a certificate provided by ngris for your account. Must be active and not expired. Omit it together with use_default: true to revert.true = revert to platform-managed ACME cert. false = use the supplied certificate_uuid. Either explicit certificate_uuid with use_default: false or use_default: true works.Deprecated: certificate_id (integer) is still accepted until the sunset. Send certificate_uuid; sending both for different objects is a 400 id_uuid_mismatch.
Response (200 OK)
true on success.uuid of the newly attached certificate, or null if reverted to default.Deprecated: until the sunset this response also carries the legacy integer certificate_id. Don't use it; read certificate_uuid.
Errors
certificate_uuid, or certificate_id and certificate_uuid naming different certificates (id_uuid_mismatch).custom_ssl entitlement.endpoint not found or certificate not found — an unknown uuid and one you can't use read the same.