---
title: "POST /v1/{+name}:activate"
method: POST
path: "/v1/{+name}:activate"
tags: ["projects"]
---

# POST /v1/{+name}:activate

`POST /v1/{+name}:activate`

Activate a CertificateAuthority that is in state AWAITING_USER_ACTIVATION and is of type SUBORDINATE. After the parent Certificate Authority signs a certificate signing request from FetchCertificateAuthorityCsr, this method can complete the activation process.

## Path parameters

- `name` string, required

## Request body

- ActivateCertificateAuthorityRequest — Request message for CertificateAuthorityService.ActivateCertificateAuthority.
  - `subordinateConfig` SubordinateConfig — Describes a subordinate CA's issuers. This is either a resource name to a known issuing CertificateAuthority, or a PEM issuer certificate chain.
    - `certificateAuthority` string — Required. This can refer to a CertificateAuthority that was used to create a subordinate CertificateAuthority. This field is used for information and usability purposes only. The resource name is in the format `projects/*/locations/*/caPools/*/certificateAuthorities/*`.
    - `pemIssuerChain` SubordinateConfigChain — This message describes a subordinate CA's issuer certificate chain. This wrapper exists for compatibility reasons.
      - `pemCertificates` string[] — Required. Expected to be in leaf-to-root order according to RFC 5246.
  - `requestId` string — Optional. An ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
  - `pemCaCertificate` string — Required. The signed CA certificate issued from FetchCertificateAuthorityCsrResponse.pem_csr.

## Response `200`

Successful response

---

[API](https://skmtc.dev/google/apis/privateca.md) · [All operations](https://skmtc.dev/google/apis/privateca/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/google/privateca/revisions/23453098738d/schema)