Certificate APIs
These are the services used for certificate enrollment, deletion, update and listing operations.
1. Get All Certificates
Description/Purpose: The credentials in the project whose name is sent as a parameter are listed. If “admin” is sent as the project name, all credentials are listed, if the project name is sent, only the credentials defined in the project are listed.
Authorization: In order to access the services, the user who wants to access the services must have a role in the project with “Manage API Security ‘ or generally ’Admin” authorization.
Endpoint: https://<APINIZER_MANAGER_ADDRESS>/apiops/projects/{projectName}/certificates/
HTTP Method: GET
Request Headers:
Header | Value |
---|---|
Authorization | <ACCESS_TOKEN> Token is required to access this endpoint. For detailed information on how to get a token, you can visit the Authorization API page |
Accept | application/json |
Request Path Parameters:
Parameter | Value |
---|---|
projectName | Full name of the project to be queried |
Request Body: (none)
Response:
Status | Status Code | Description | Body |
---|---|---|---|
Success | 200 | successful operation | { |
Fault | 400 | bad request | { "error": "...", "error_description": "..." } |
Fault | 401 | not authorized for this operation | { |
Fault | 500 | internal error | { "error": "...", "error_description": "..." } |
2. Create Certificate
Description/Purpose: A new certificate is created in the project whose name is sent as a parameter. If “admin” is sent as the project name, the certificate is defined globally.
Authorization: In order to access the services, the user who wants to access the services must have a role in the project with “Manage API Security ‘ or generally ’Admin” authorization.
Endpoint: https://<APINIZER_MANAGER_ADDRESS>/apiops/projects/{projectName}/certificates/
HTTP Method: POST
Request Headers:
Header | Value |
---|---|
Authorization | <ACCESS_TOKEN> Token acquisition is required to access this endpoint. For detailed information on how to get tokens, you can visit the Authorization API page. |
Content-Type | multipart/form-data |
Accept | application/json |
Request Path Parameters:
Parameter | Value |
---|---|
projectName | Full name of the project where the certificate is located |
Request Body: (none)
Request Form Parametreleri:
Parametre | Tip | Zorunluluk | Açıklama |
---|---|---|---|
certificateName | string | Required | Unique name for the certificate |
alias | string | Required | Alias to use for the certificate |
certificateDescription | string | Optional | Description of the certificate |
deploy | boolean | Required | Whether the certificate will be deployed immediately |
environmentList | string | Conditional | This field is mandatory if deploy option is true, comma separated environment list (ex: test,prod) |
pemEncodedFile | file | Required | Certificate file in PEM format |
Response:
Status | Status Code | Description | Body |
---|---|---|---|
Success | 200 | successful operation | { |
Fault | 400 | bad request | { "error": "...", "error_description": "..." } |
Fault | 401 | not authorized for this operation | { |
Fault | 500 | internal error | { "error": "...", "error_description": "..." } |
3. Update Certificate
Description/Purpose: It is provided to update the existing certificate in the project whose name is sent as a parameter. If “admin” is sent as the project name, the certificate is updated globally.
Authorization: In order to access the services, the user who wants to access the services must have a role in the project with “Manage API Security ‘ or generally ’Admin” authorization.
Endpoint: https://<APINIZER_MANAGER_ADDRESS>/apiops/projects/{projectName}/certificates/{certificateName}/
HTTP Method: PUT
Request Headers:
Header | Value |
---|---|
Authorization | <ACCESS_TOKEN> Token acquisition is required to access this endpoint. For detailed information on how to get tokens, you can visit the Authorization API page. |
Content-Type | multipart/form-data |
Accept | application/json |
Request Path Parameters:
Parameter | Value |
---|---|
projectName | Full name of the project where the certificate is located |
certificateName | Full name of the certificate to be updated |
Request Body: (none)
Request Form Parametreleri:
Parametre | Tip | Zorunluluk | Açıklama |
---|---|---|---|
certificateName | string | Required | Unique name for the certificate |
alias | string | Required | Alias to use for the certificate |
certificateDescription | string | Optional | Description of the certificate |
deploy | boolean | Required | Whether the certificate will be deployed immediately |
environmentList | string | Conditional | This field is mandatory if deploy option is true, comma separated environment list (ex: test,prod) |
pemEncodedFile | file | Required | Certificate file in PEM format |
Response:
Status | Status Code | Description | Body |
---|---|---|---|
Success | 200 | successful operation | { |
Fault | 400 | bad request | { "error": "...", "error_description": "..." } |
Fault | 401 | not authorized for this operation | { |
Fault | 500 | internal error | { "error": "...", "error_description": "..." } |
4. Delete Certificate
Description/Purpose: It is ensured that the certificate existing in the project whose name is sent as a parameter is deleted. If “admin” is sent as the project name, the certificate will be deleted from global.
Authorization: In order to access the services, the user who wants to access the services must have a role in the project with “Manage API Security ‘ or generally ’Admin” authorization.
Endpoint: https://<APINIZER_MANAGER_ADDRESS>/apiops/projects/{projectName}/certificates/{certificateName}/
HTTP Method: DELETE
Request Headers:
Header | Value |
---|---|
Authorization | <ACCESS_TOKEN> Token acquisition is required to access this endpoint. For detailed information on how to get tokens, you can visit the Authorization API page. |
Accept | application/json |
Request Path Parameters:
Parameter | Value |
---|---|
projectName | Full name of the project where the certificate is located |
certificateName | Full name of the certificate to be updated |
Request Body: (none)
Response:
Status | Status Code | Description | Body |
---|---|---|---|
Success | 200 | successful operation | { |
Fault | 400 | bad request | { "error": "...", "error_description": "..." } |
Fault | 401 | not authorized for this operation | { |
Fault | 500 | internal error | { "error": "...", "error_description": "..." } |
5. Get an existing Certificate
Description/Purpose: It is provided to retrieve the information of the certificate available in the project whose name is sent as a parameter. If “admin” is sent as the project name, the certificate is retrieved from global.
Authorization: In order to access the services, the user who wants to access the services must have a role in the project with “Manage API Security ‘ or generally ’Admin” authorization.
Endpoint: https://<APINIZER_MANAGER_ADDRESS>/apiops/projects/{projectName}/certificates/{certificateName}/
HTTP Method: GET
Request Headers:
Header | Value |
---|---|
Authorization | <ACCESS_TOKEN> Token acquisition is required to access this endpoint. For detailed information on how to get tokens, you can visit the Authorization API page. |
Accept | application/json |
Request Path Parameters:
Parameter | Value |
---|---|
projectName | Full name of the project where the certificate is located |
certificateName | Full name of the certificate to be updated |
Response:
Status | Status Code | Description | Body |
---|---|---|---|
Success | 200 | successful operation | { |
Fault | 400 | bad request | { "error": "...", "error_description": "..." } |
Fault | 401 | not authorized for this operation | { |
Fault | 500 | internal error | { "error": "...", "error_description": "..." } |
6. Export an existing Certificate
Description/Purpose: The certificate available in the project whose name is sent as a parameter is exported. If “admin” is sent as the project name, the certificate is imported from global.
Authorization: In order to access the services, the user who wants to access the services must have a role in the project with “Manage API Security ‘ or generally ’Admin” authorization.
Endpoint: https://<APINIZER_MANAGER_ADDRESS>/apiops/projects/{projectName}/certificates/{certificateName}/
HTTP Method: GET
Request Headers:
Header | Value |
---|---|
Authorization | <ACCESS_TOKEN> Token acquisition is required to access this endpoint. For detailed information on how to get tokens, you can visit the Authorization API page. |
Accept | application/json |
Request Path Parameters:
Parameter | Value |
---|---|
projectName | Full name of the project where the certificate is located |
certificateName | Full name of the certificate to be updated |
Response:
Status | Status Code | Description | Body |
---|---|---|---|
Success | 200 | successful operation | The file with .cer extension returns the zip file. It can be saved as a file and used by unzipping it. |
Fault | 400 | bad request | { "error": "...", "error_description": "..." } |
Fault | 401 | not authorized for this operation | { |
Fault | 500 | internal error | { "error": "...", "error_description": "..." } |
7. Get Certificates of Truststore of Environment
Description/Purpose: It is provided to return the information of all certificates used by Java in the environment whose name is sent as a parameter.
Authorization: In order to access the services, the user who wants to access the services must have a role in the project with “Manage API Security ‘ or generally ’Admin” authorization.
Endpoint: https://<APINIZER_MANAGER_ADDRESS>/apiops/projects/admin/certificates/truststore/{environmentName}/
HTTP Method: GET
Request Headers:
Header | Value |
---|---|
Authorization | <ACCESS_TOKEN> Token acquisition is required to access this endpoint. For detailed information on how to get tokens, you can visit the Authorization API page. |
Accept | application/json |
Request Path Parameters:
Parameter | Value |
---|---|
environmentName | Truststore's environment |
Response:
Status | Status Code | Description | Body |
---|---|---|---|
Success | 200 | successful operation | { |
Fault | 400 | bad request | { "error": "...", "error_description": "..." } |
Fault | 401 | not authorized for this operation | { |
Fault | 500 | internal error | { "error": "...", "error_description": "..." } |