Digital Certificates

Edit on GitHub

Through the Digital Certificates API you can retrieve, create, remove or update your SSL certificates.

  1. Retrieving the Digital Certificates list
  2. Retrieving the data of a Digital Certificate by id
  3. Retrieving the data of a Digital Certificate by name
  4. Deleting a Digital Certificate
  5. Creating a new Digital Certificate
  6. Overwriting a Digital Certificate
  7. Updating fields of a Digital Certificate

1. Retrieving the list of Digital Certificates

It returns the list of Digital Certificates of an account.

GET /digital_certificates

Required permission: View Security Settings

Parameter Description Type Type of Data
Authorization
*mandatory
Token authentication previously created through the Token Creation endpoint. header string
Accept
*mandatory
Information about the return type and version. header String;

mandatory:
application/json;version=3

Request Example

GET /digital_certificates 
Accept: application/json; version=3;
Authorization: token 2909f3932069047f4736dc87e72baaddd19c9f75

Response Example

{
    "count": 2,
    "total_pages": 1,
    "schema_version": 3,
    "links": {
        "previous": null,
        "next": null
    },
    "results": [
        {
            "id": 14,
            "name": "Self-signed Certificate"
        },
        {
            "id": 344,
            "name": "Certificado SSL para www.mydomain.com"
        }
    ]
}

2. Retrieving the data of a Digital Certificate

It returns the details of a Digital Certificate.

GET /digital_certificates/:id

Required permission: View Security Settings

Parameter Description Type Type of Data
Authorization
*mandatory
Token authentication previously created through the Token Creation endpoint. header string
Accept
*mandatory
Information about the return type and version. header String;

mandatory:
application/json;version=3
:id
*mandatory
The id of the digital certificate to be consulted. path number

Request Example

GET /digital_certificates/14
Accept: application/json; version=3
Authorization: token 2909f3932069047f4736dc87e72baaddd19c9f75

Response Example

{
    "results": {
        "id": 14,
        "name": "Self-signed Certificate"
    },
    "schema_version": 3
}

3. Retrieving the data of a Digital Certificate by Name

It returns the details of a Digital Certificate using the GET method as a filter through the Certificate Name.

Attention: this endpoint uses Filtering logic, so if your query doesn’t match, an empty list will be returned.

GET /digital_certificates/?name=CertificateName

Required permission: View Security Settings

Parameter Description Type Type of Data
Authorization
*mandatory
Token authentication previously created through the Token Creation endpoint. header string
Accept
*mandatory
Information about the return type and version. header String;

mandatory:
application/json;version=3
:certificate_name
*mandatory
The name of the digital certificate to be consulted. path string

Request Example

GET /digital_certificates/?name=Self-signed Certificate
Accept: application/json; version=3
Authorization: token 2909f3932069047f4736dc87e72baaddd19c9f75

Response Example

{
    "results": {
        "id": 14,
        "name": "Self-signed Certificate"
    },
    "schema_version": 3
}

4. Deleting a Digital Certificate

It removes a Digital Certificate. To be able to be removed the certificate cannot be in use.

DELETE /digital_certificates/:id

Required permission: Edit Security Settings

Parameter Description Tipo Type of Data
Authorization
*mandatory
Token authentication previously created through the Token Creation endpoint. header string
Accept
*mandatory
Information about the return type and version. header String;

mandatory:
application/json;version=3
:id
*mandatory
The id of the digital certificate to be removed. path number

Request Example

DELETE /digital_certificates/14
Accept: application/json; version=3
Authorization: token 2909f3932069047f4736dc87e72baaddd19c9f75

Response Example

HTTP/2 204

5. Creating a new Digital Certificate

It uploads a digital certificate to Azion.

POST /digital_certificates

Required permission: Edit Security Settings

Parameter Description Tipo Type of Data
Authorization
*mandatory
Token authentication previously created through the Token Creation endpoint. header string
Accept
*mandatory
Information about the return type and version. header String;

mandatory:
application/json;version=3
Content-Type
*mandatory
The type of encoding used in Body (application/json).

Example:
Content-Type: application/json
header string
Certificate
*mandatory
The certificate to be created must be sent encoded in json format with the following fields:

name (string): mandatory field that defines a name for the digital certificate.

certificate (string): he certificate is the file you received from your Certificate Authority (CA), in ASCII PEM format, replacing all line breaks with “\n”. The certificate must start with the marker “—- BEGIN CERTIFICATE —–” and end with the marker “—– END CERTIFICATE-

private_key (string): he private key is the file you used to generate the CSR request you sent to your CA, replacing all line breaks with “\n”. The private key must start with the marker “—- BEGIN RSA PRIVATE KEY —–” and end with the marker “—– END RSA PRIVATE KEY —–“.
body json

Request Example

POST /digital_certificates
Accept: application/json; version=3
Authorization: token 2909f3932069047f4736dc87e72baaddd19c9f75
Content-Type: application/json
{
    "name": "Certificado SSL para www.mydomain.com",
    "certificate": "-----BEGIN CERTIFICATE-----\nMIIDCTCCAfGgAwIBAgIJAPpMWHKMIGuAMA0GCSqGSIb3DQEBBQUAMBsxGTAXBgNV\nBAMMEHd3dy5teWRvbWFpbi5jb20wHhcNMTgwMzI3MjAwOTA0WhcNMjgwMzI0MjAw\nOTA0WjAbMRkwFwYDVQQDDBB3d3cubXlkb21haW4uY29tMIIBIjANBgkqhkiG9w0B\nAQEFAAOCAQ8AMIIBCgKCAQEAt25cziDBsHbZzZhy9BPLApPf9OmE67k9pr7VezsR\nkIw4trY2xtJXFB7itT1p7HxbLBoL5u8FGmMKssB+XTmztmgty43ogor1KSjUgfZg\nrpAqyXtrbSM5g+14c0VO9S0LkkePlHvul0UiblJj7K+gkvc6sZqXZY+TI1BPqeuO\ns9A4LLCUGziyNv0qJfIL5RZm07Yy35BEBTTxUWVL2msfaUH2uPM5XN5eFC7oKN0/\n3NuYIboRmyk+P7CDC99M8Mp/wOjiB+yVGZVTjeqGPI8nFWJl2waXkc54VvW84xQP\njwtid1v1KENK/ixMAAXi2cQ9gNRX+/USoneuWj5n4QUj6QIDAQABo1AwTjAdBgNV\nHQ4EFgQU2sDgtyYMDXvw79OhdvAFqcLmcwkwHwYDVR0jBBgwFoAU2sDgtyYMDXvw\n79OhdvAFqcLmcwkwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOCAQEAKzCM\niG67IPwJK6MIJ31N734AofnjLf+fffxNtfYmH0XGORHPYUxCxsLxXiSFgPvubWh+\n7vLsKAm67bflMWbnxohuiOR0O/LJhLvhj6F+wgv0aDXpu581Hm8Ob/88ldbF6ND1\nTqzVATS0WDfl+z1QBKtNdDm3Nv45IZ83ob7OhIzD9MwL6tflBPDpWOYtmBDn0xSP\n6ra9d8oa6jK1fe2/5A7LY41acjbbNrLbFDYP7hcx02TmCfSMut+ysaZ/blay4Sbb\nwNlt92KhJw07UEKgXXbgyXGoFQkU8V+r2AZcgt0XM9jvwTc01Sbq/gegd2GMAj3x\nrTwkn5UNzFs56FCgNg==\n-----END CERTIFICATE-----",
    "private_key": "-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQEAt25cziDBsHbZzZhy9BPLApPf9OmE67k9pr7VezsRkIw4trY2\nxtJXFB7itT1p7HxbLBoL5u8FGmMKssB+XTmztmgty43ogor1KSjUgfZgrpAqyXtr\nbSM5g+14c0VO9S0LkkePlHvul0UiblJj7K+gkvc6sZqXZY+TI1BPqeuOs9A4LLCU\nGziyNv0qJfIL5RZm07Yy35BEBTTxUWVL2msfaUH2uPM5XN5eFC7oKN0/3NuYIboR\nmyk+P7CDC99M8Mp/wOjiB+yVGZVTjeqGPI8nFWJl2waXkc54VvW84xQPjwtid1v1\nKENK/ixMAAXi2cQ9gNRX+/USoneuWj5n4QUj6QIDAQABAoIBAQCJRwAPh/ZM8XWp\nZ1lIj3OUN0UZjpZar+SS4Sj1s8w+aKKdIxs1iv9+YGr8hry6LosxI0EbEHC6Qbsk\n8ejgLinv7mGvgEGtSP+XUSZRKSlMGzraVRKduAn4UQWfBxTDanXJgOLUljeGYEgX\nVnPQE9RRiNMVTgPWDzBn8lfcbBz9NigmyaBkKw3yyhOopLpmcyWqMbuSwJotwOKe\nomVnlRck2OsIOz51CDXwdXcM0mogkVuWhPLEM53K7KitQFpbMjS8fS3dyJBBbZaR\nnvXlUPVbaC8pm9TbACDQ8fhSRd/B22B8PXHyYMWdrTxYgkFhlgIPEu3Z0e8GkR7f\nt0GHM3eNAoGBANqJVHgwG/WgJivzhm6VAfVWuSoElDh/JthXUuGbJ9IGcRVvM906\nYb1O70iLJOisq8BcDNv5WU7CSnQzU2oYzvzbMr/3TBwFxJZKKMh1y992YKBIWfzR\nz7JK2USvLdhO/RovD+roQeavXae9p+ml8GgLZqhDlLKWNkW9EUL1xt8nAoGBANbg\nZx8JFzQTDuQrOdSyIVW4A3NXPRiGBf63BGPbzD9PM2dUL13NsrO2tyL2gEXtcAaq\nJsZmHXHip38qFxuA5yPYzdqQPbBWC9WWHL2E63dd9tAnZ0g4a1GnBs6q3Fh6lhzG\nWREgAEOzCv07XVers4magKTaxM3XocS5GZM5n85vAoGAJH1v1E28LWxbU1VragWJ\neSzM6D4xfamFk/Qoy7D7mi8nLLwPve3kqhaHD+bj99H1L75vCz/8cJEym2qCkCGq\nVkBHnhQt6jPwWmPxoV9B9oMuqTTLidKCyrOCydwyXH779iZLkx7K+jjn+31Ij1P8\n63KT5p66MoOwdj6WpkahuVsCgYBvAdUkWmzrUSEzTQV+VVwVTZAyyRHeFncIZQJW\nmFmHJ2J18i7aNgcpAq7P2CridUyXlNWdT2nMyPwhHNx9L/W5Nir6y+OisoFAoWFN\no1qF+zwjwwd/bu46a6B/qhNVflcInIus5ixczSVTN5T8Us7YusHU6NQdR1XiLIIC\n5hUh7wKBgQCWwTSDKm1TUHT7K35GmyHryECQwjJhclzfJZfFoSAudiQY20KgehlS\nnT7GrIb6QIsm7hsauX1Aq76d2TYlgkD1OHmJy/+i9+76ee5ZDFkboqMCwRtcgw1D\nIYA1ocRBfN+xQ7jU9GvuLSbFka9drQwWWdxiXeYSyLRBYlAFIpdLKQ==\n-----END RSA PRIVATE KEY-----"
}

Response Example

{
    "results": {
        "id": 37,
        "name": "SSL Certificate for www.mydomain.com"
    },
    "schema_version": 3
}

6. Overwriting a Digital Certificate

It overwrites all fields of a Digital Certificate, while preserving the id. Consider using the PATCH method instead of PUT, to update only some fields of a Digital Certificate, without changing the value of the others.

PUT /digital_certificates/:id

Required permission: Edit Security Settings

Parameter Description Type Type of Data
Authorization
*mandatory
Token authentication previously created through the Token Creation endpoint header string
Accept
*mandatory
Information about the return type and version header String;

mandatory:
application/json;version=3
Content-Type
*mandatory
The type of encoding used in Body (application/json).

Example:
Content-Type: application/json
header string
:id
*mandatory
Id of the Digital Certificate to be overwritten. path number
Certificate
*mandatory
The new values for each Digital Certificate field. If you want to change only one of the fields, use the PATCH method instead of the PUT.

name (string): mandatory field that defines a name for the digital certificate.

certificate (string): the certificate is the file you received from your Certificate Authority (CA), in ASCII PEM format, replacing all line breaks with “\n”. The certificate must start with the marker “—- BEGIN CERTIFICATE —–” and end with the marker “—– END CERTIFICATE—”.

private_key (string): the private key is the file you used to generate the CSR request you sent to your CA, replacing all line breaks with “\n”. The private key must start with the marker “—- BEGIN RSA PRIVATE KEY —–” and end with the marker “—– END RSA PRIVATE KEY —–“.
body json

Request Example

PUT /digital_certificates/37
Accept: application/json; version=3
Authorization: token 2909f3932069047f4736dc87e72baaddd19c9f75
Content-Type: application/json
{
    "name": "NEW SSL Certificate for www.mydomain.com",
    "certificate": "-----BEGIN CERTIFICATE-----\nMIIDCTCCAfGgAwIBAgIJAPpMWHKMIGuAMA0GCSqGSIb3DQEBBQUAMBsxGTAXBgNV\nBAMMEHd3dy5teWRvbWFpbi5jb20wHhcNMTgwMzI3MjAwOTA0WhcNMjgwMzI0MjAw\nOTA0WjAbMRkwFwYDVQQDDBB3d3cubXlkb21haW4uY29tMIIBIjANBgkqhkiG9w0B\nAQEFAAOCAQ8AMIIBCgKCAQEAt25cziDBsHbZzZhy9BPLApPf9OmE67k9pr7VezsR\nkIw4trY2xtJXFB7itT1p7HxbLBoL5u8FGmMKssB+XTmztmgty43ogor1KSjUgfZg\nrpAqyXtrbSM5g+14c0VO9S0LkkePlHvul0UiblJj7K+gkvc6sZqXZY+TI1BPqeuO\ns9A4LLCUGziyNv0qJfIL5RZm07Yy35BEBTTxUWVL2msfaUH2uPM5XN5eFC7oKN0/\n3NuYIboRmyk+P7CDC99M8Mp/wOjiB+yVGZVTjeqGPI8nFWJl2waXkc54VvW84xQP\njwtid1v1KENK/ixMAAXi2cQ9gNRX+/USoneuWj5n4QUj6QIDAQABo1AwTjAdBgNV\nHQ4EFgQU2sDgtyYMDXvw79OhdvAFqcLmcwkwHwYDVR0jBBgwFoAU2sDgtyYMDXvw\n79OhdvAFqcLmcwkwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOCAQEAKzCM\niG67IPwJK6MIJ31N734AofnjLf+fffxNtfYmH0XGORHPYUxCxsLxXiSFgPvubWh+\n7vLsKAm67bflMWbnxohuiOR0O/LJhLvhj6F+wgv0aDXpu581Hm8Ob/88ldbF6ND1\nTqzVATS0WDfl+z1QBKtNdDm3Nv45IZ83ob7OhIzD9MwL6tflBPDpWOYtmBDn0xSP\n6ra9d8oa6jK1fe2/5A7LY41acjbbNrLbFDYP7hcx02TmCfSMut+ysaZ/blay4Sbb\nwNlt92KhJw07UEKgXXbgyXGoFQkU8V+r2AZcgt0XM9jvwTc01Sbq/gegd2GMAj3x\nrTwkn5UNzFs56FCgNg==\n-----END CERTIFICATE-----",
    "private_key": "-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQEAt25cziDBsHbZzZhy9BPLApPf9OmE67k9pr7VezsRkIw4trY2\nxtJXFB7itT1p7HxbLBoL5u8FGmMKssB+XTmztmgty43ogor1KSjUgfZgrpAqyXtr\nbSM5g+14c0VO9S0LkkePlHvul0UiblJj7K+gkvc6sZqXZY+TI1BPqeuOs9A4LLCU\nGziyNv0qJfIL5RZm07Yy35BEBTTxUWVL2msfaUH2uPM5XN5eFC7oKN0/3NuYIboR\nmyk+P7CDC99M8Mp/wOjiB+yVGZVTjeqGPI8nFWJl2waXkc54VvW84xQPjwtid1v1\nKENK/ixMAAXi2cQ9gNRX+/USoneuWj5n4QUj6QIDAQABAoIBAQCJRwAPh/ZM8XWp\nZ1lIj3OUN0UZjpZar+SS4Sj1s8w+aKKdIxs1iv9+YGr8hry6LosxI0EbEHC6Qbsk\n8ejgLinv7mGvgEGtSP+XUSZRKSlMGzraVRKduAn4UQWfBxTDanXJgOLUljeGYEgX\nVnPQE9RRiNMVTgPWDzBn8lfcbBz9NigmyaBkKw3yyhOopLpmcyWqMbuSwJotwOKe\nomVnlRck2OsIOz51CDXwdXcM0mogkVuWhPLEM53K7KitQFpbMjS8fS3dyJBBbZaR\nnvXlUPVbaC8pm9TbACDQ8fhSRd/B22B8PXHyYMWdrTxYgkFhlgIPEu3Z0e8GkR7f\nt0GHM3eNAoGBANqJVHgwG/WgJivzhm6VAfVWuSoElDh/JthXUuGbJ9IGcRVvM906\nYb1O70iLJOisq8BcDNv5WU7CSnQzU2oYzvzbMr/3TBwFxJZKKMh1y992YKBIWfzR\nz7JK2USvLdhO/RovD+roQeavXae9p+ml8GgLZqhDlLKWNkW9EUL1xt8nAoGBANbg\nZx8JFzQTDuQrOdSyIVW4A3NXPRiGBf63BGPbzD9PM2dUL13NsrO2tyL2gEXtcAaq\nJsZmHXHip38qFxuA5yPYzdqQPbBWC9WWHL2E63dd9tAnZ0g4a1GnBs6q3Fh6lhzG\nWREgAEOzCv07XVers4magKTaxM3XocS5GZM5n85vAoGAJH1v1E28LWxbU1VragWJ\neSzM6D4xfamFk/Qoy7D7mi8nLLwPve3kqhaHD+bj99H1L75vCz/8cJEym2qCkCGq\nVkBHnhQt6jPwWmPxoV9B9oMuqTTLidKCyrOCydwyXH779iZLkx7K+jjn+31Ij1P8\n63KT5p66MoOwdj6WpkahuVsCgYBvAdUkWmzrUSEzTQV+VVwVTZAyyRHeFncIZQJW\nmFmHJ2J18i7aNgcpAq7P2CridUyXlNWdT2nMyPwhHNx9L/W5Nir6y+OisoFAoWFN\no1qF+zwjwwd/bu46a6B/qhNVflcInIus5ixczSVTN5T8Us7YusHU6NQdR1XiLIIC\n5hUh7wKBgQCWwTSDKm1TUHT7K35GmyHryECQwjJhclzfJZfFoSAudiQY20KgehlS\nnT7GrIb6QIsm7hsauX1Aq76d2TYlgkD1OHmJy/+i9+76ee5ZDFkboqMCwRtcgw1D\nIYA1ocRBfN+xQ7jU9GvuLSbFka9drQwWWdxiXeYSyLRBYlAFIpdLKQ==\n-----END RSA PRIVATE KEY-----"
}

Response Example

{
    "id": 37,
    "name": "NEW SSL Certificate for www.mydomain.com"
}

7. Updating fields of a Digital Certificate

It updates one or more fields of a Digital Certificate, preserving the value of the fields not informed. The “certificate” and “private_key” fields cannot be updated separately, they are always sent in pairs.

PATCH /digital_certificates/:id

Required permission: Edit Security Settings

Parameter Description Type Type of Data
Authorization
*mandatory
Token authentication previously created through the Token Creation endpoint header string
Accept
*mandatory
Information about the return type and version header String;

mandatory:
application/json;version=3
Content-Type
*mandatory
The type of encoding used in Body (application/json).

Example:
Content-Type: application/json
header string
:id
*mandatory
Id of the Digital Certificate to be overwritten. path number
Certificate
*mandatory
The new values for each Digital Certificate field. If you want to change only one of the fields, use the PATCH method instead of the PUT.

name (string): mandatory field that defines a name for the digital certificate.

certificate (string): the certificate is the file you received from your Certificate Authority (CA), in ASCII PEM format, replacing all line breaks with “\n”. The certificate must start with the marker “—- BEGIN CERTIFICATE —–” and end with the marker “—– END CERTIFICATE—”.

private_key (string): the private key is the file you used to generate the CSR request you sent to your CA, replacing all line breaks with “\n”. The private key must start with the marker “—- BEGIN RSA PRIVATE KEY —–” and end with the marker “—– END RSA PRIVATE KEY —–“.
body json

Request Example

PUT /digital_certificates/37
Accept: application/json; version=3
Authorization: token 2909f3932069047f4736dc87e72baaddd19c9f75
Content-Type: application/json
{
    "name": "NEW SSL Certificate for www.mydomain.com",
    Certificate: "-----BEGIN CERTIFICATE-----\nMIIDCTCCAfGgAwIBAgIJAPpMWHKMIGuAMA0GCSqGSIb3DQEBBQUAMBsxGTAXBgNV\nBAMMEHd3dy5teWRvbWFpbi5jb20wHhcNMTgwMzI3MjAwOTA0WhcNMjgwMzI0MjAw\nOTA0WjAbMRkwFwYDVQQDDBB3d3cubXlkb21haW4uY29tMIIBIjANBgkqhkiG9w0B\nAQEFAAOCAQ8AMIIBCgKCAQEAt25cziDBsHbZzZhy9BPLApPf9OmE67k9pr7VezsR\nkIw4trY2xtJXFB7itT1p7HxbLBoL5u8FGmMKssB+XTmztmgty43ogor1KSjUgfZg\nrpAqyXtrbSM5g+14c0VO9S0LkkePlHvul0UiblJj7K+gkvc6sZqXZY+TI1BPqeuO\ns9A4LLCUGziyNv0qJfIL5RZm07Yy35BEBTTxUWVL2msfaUH2uPM5XN5eFC7oKN0/\n3NuYIboRmyk+P7CDC99M8Mp/wOjiB+yVGZVTjeqGPI8nFWJl2waXkc54VvW84xQP\njwtid1v1KENK/ixMAAXi2cQ9gNRX+/USoneuWj5n4QUj6QIDAQABo1AwTjAdBgNV\nHQ4EFgQU2sDgtyYMDXvw79OhdvAFqcLmcwkwHwYDVR0jBBgwFoAU2sDgtyYMDXvw\n79OhdvAFqcLmcwkwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOCAQEAKzCM\niG67IPwJK6MIJ31N734AofnjLf+fffxNtfYmH0XGORHPYUxCxsLxXiSFgPvubWh+\n7vLsKAm67bflMWbnxohuiOR0O/LJhLvhj6F+wgv0aDXpu581Hm8Ob/88ldbF6ND1\nTqzVATS0WDfl+z1QBKtNdDm3Nv45IZ83ob7OhIzD9MwL6tflBPDpWOYtmBDn0xSP\n6ra9d8oa6jK1fe2/5A7LY41acjbbNrLbFDYP7hcx02TmCfSMut+ysaZ/blay4Sbb\nwNlt92KhJw07UEKgXXbgyXGoFQkU8V+r2AZcgt0XM9jvwTc01Sbq/gegd2GMAj3x\nrTwkn5UNzFs56FCgNg==\n-----END CERTIFICATE-----",
    "private_key": "-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQEAt25cziDBsHbZzZhy9BPLApPf9OmE67k9pr7VezsRkIw4trY2\nxtJXFB7itT1p7HxbLBoL5u8FGmMKssB+XTmztmgty43ogor1KSjUgfZgrpAqyXtr\nbSM5g+14c0VO9S0LkkePlHvul0UiblJj7K+gkvc6sZqXZY+TI1BPqeuOs9A4LLCU\nGziyNv0qJfIL5RZm07Yy35BEBTTxUWVL2msfaUH2uPM5XN5eFC7oKN0/3NuYIboR\nmyk+P7CDC99M8Mp/wOjiB+yVGZVTjeqGPI8nFWJl2waXkc54VvW84xQPjwtid1v1\nKENK/ixMAAXi2cQ9gNRX+/USoneuWj5n4QUj6QIDAQABAoIBAQCJRwAPh/ZM8XWp\nZ1lIj3OUN0UZjpZar+SS4Sj1s8w+aKKdIxs1iv9+YGr8hry6LosxI0EbEHC6Qbsk\n8ejgLinv7mGvgEGtSP+XUSZRKSlMGzraVRKduAn4UQWfBxTDanXJgOLUljeGYEgX\nVnPQE9RRiNMVTgPWDzBn8lfcbBz9NigmyaBkKw3yyhOopLpmcyWqMbuSwJotwOKe\nomVnlRck2OsIOz51CDXwdXcM0mogkVuWhPLEM53K7KitQFpbMjS8fS3dyJBBbZaR\nnvXlUPVbaC8pm9TbACDQ8fhSRd/B22B8PXHyYMWdrTxYgkFhlgIPEu3Z0e8GkR7f\nt0GHM3eNAoGBANqJVHgwG/WgJivzhm6VAfVWuSoElDh/JthXUuGbJ9IGcRVvM906\nYb1O70iLJOisq8BcDNv5WU7CSnQzU2oYzvzbMr/3TBwFxJZKKMh1y992YKBIWfzR\nz7JK2USvLdhO/RovD+roQeavXae9p+ml8GgLZqhDlLKWNkW9EUL1xt8nAoGBANbg\nZx8JFzQTDuQrOdSyIVW4A3NXPRiGBf63BGPbzD9PM2dUL13NsrO2tyL2gEXtcAaq\nJsZmHXHip38qFxuA5yPYzdqQPbBWC9WWHL2E63dd9tAnZ0g4a1GnBs6q3Fh6lhzG\nWREgAEOzCv07XVers4magKTaxM3XocS5GZM5n85vAoGAJH1v1E28LWxbU1VragWJ\neSzM6D4xfamFk/Qoy7D7mi8nLLwPve3kqhaHD+bj99H1L75vCz/8cJEym2qCkCGq\nVkBHnhQt6jPwWmPxoV9B9oMuqTTLidKCyrOCydwyXH779iZLkx7K+jjn+31Ij1P8\n63KT5p66MoOwdj6WpkahuVsCgYBvAdUkWmzrUSEzTQV+VVwVTZAyyRHeFncIZQJW\nmFmHJ2J18i7aNgcpAq7P2CridUyXlNWdT2nMyPwhHNx9L/W5Nir6y+OisoFAoWFN\no1qF+zwjwwd/bu46a6B/qhNVflcInIus5ixczSVTN5T8Us7YusHU6NQdR1XiLIIC\n5hUh7wKBgQCWwTSDKm1TUHT7K35GmyHryECQwjJhclzfJZfFoSAudiQY20KgehlS\nnT7GrIb6QIsm7hsauX1Aq76d2TYlgkD1OHmJy/+i9+76ee5ZDFkboqMCwRtcgw1D\nIYA1ocRBfN+xQ7jU9GvuLSbFka9drQwWWdxiXeYSyLRBYlAFIpdLKQ==\n-----END RSA PRIVATE KEY-----"
}

Response Example

{
    "id": 37,
    "name": "NEW SSL Certificate for www.mydomain.com"
}

Didn’t find what you were looking for? Open a ticket.