NSX-T Data Center REST API
Associated URIs:
| API Description | API Path | 
|---|---|
Returns information about all the CA bundlesReturns information about all the bundles of trusted CA certificates.  | 
                      
                        GET /policy/api/v1/infra/cabundles
                         | 
                    
Deletes CA bundleDeletes the specified bundle of trusted CA certificates.  | 
                      
                        DELETE /policy/api/v1/infra/cabundles/{cabundle-id}
                         | 
                    
Returns information about a CA bundleReturns information about the specified bundle of trusted CA certificates.  | 
                      
                        GET /policy/api/v1/infra/cabundles/{cabundle-id}
                         | 
                    
Adds or updates a CA bundleAdds or updates a new bundle of trusted CA certificates. The bundle must be a concatenation of one or more PEM-encoded certificates. The PEM-encoded bundle is replaced with the one provided in the request.  | 
                      
                        PATCH /policy/api/v1/infra/cabundles/{cabundle-id}
                         | 
                    
Adds or replaces a CA bundleAdds or replaces a new bundle of trusted CA certificates. The multipart-uploaded file must be a concatenation of one or more PEM-encoded certificates.  | 
                      
                        POST /policy/api/v1/infra/cabundles/{cabundle-id}
                         | 
                    
Adds or replaces a CA bundleAdds or replaces a new bundle of trusted CA certificates. The bundle must be a concatenation of one or more PEM-encoded certificates.  | 
                      
                        PUT /policy/api/v1/infra/cabundles/{cabundle-id}
                         | 
                    
Downloads a CA bundleDownloads the specified PEM-encoded bundle of trusted CA certificates.  | 
                      
                        GET /policy/api/v1/infra/cabundles/{cabundle-id}/pem-file
                         | 
                    
Return All the User-Facing Components' CertificatesReturns all certificate information viewable by the user, including each certificate's id; pem_encoded data; and history of the certificate (who created or modified it and when). For additional information, include the ?details=true modifier at the end of the request URI.  | 
                      
                        GET /policy/api/v1/infra/certificates
                         GET /policy/api/v1/global-infra/certificates  | 
                    
Delete Certificate for the Given Certificate IDRemoves the specified certificate. The private key associated with the certificate is also deleted.  | 
                      
                        DELETE /policy/api/v1/infra/certificates/{certificate-id}
                         | 
                    
Show Certificate Data for the Given Certificate IDReturns information for the specified certificate ID, including the certificate's id; pem_encoded data; and history of the certificate (who created or modified it and when). For additional information, include the ?details=true modifier at the end of the request URI.  | 
                      
                        GET /policy/api/v1/infra/certificates/{certificate-id}
                         GET /policy/api/v1/global-infra/certificates/{certificate-id}  | 
                    
Add a New CertificateAdds a new private-public certificate and, optionally, a private key that can be applied to one of the user-facing components (appliance management or edge). The certificate and the key should be stored in PEM format. If no private key is provided, the certificate is used as a client certificate in the trust store. A private key can be uploaded for a CA certificate only if the "purpose" parameter is set to "signing-ca". A certificate chain will not be expanded into separate certificate instances for reference, but would be pushed to the enforcement point as a single certificate. This patch method does not modify an existing certificate.  | 
                      
                        PATCH /policy/api/v1/infra/certificates/{certificate-id}
                         | 
                    
Add a New CertificateAdds a new private-public certificate and, optionally, a private key that can be applied to one of the user-facing components (appliance management or edge). The certificate and the key should be stored in PEM format. If no private key is provided, the certificate is used as a client certificate in the trust store. A private key can be uploaded for a CA certificate only if the "purpose" parameter is set to "signing-ca". A certificate chain will not be expanded into separate certificate instances for reference, but would be pushed to the enforcement point as a single certificate. This PUT method does not modify an existing certificate.  | 
                      
                        PUT /policy/api/v1/infra/certificates/{certificate-id}
                         |