Link Search Menu Expand Document (external link)

Order Create

V6.0.10

The Order Create API will create an order for a SSL/TLS certificate.

Authorization

An access token must be acquired to make requests to the API. Please follow the instructions in the link below to acquire the token.

Access Token

Subscription Id

Each request must include the Subscription Id of the user’s subscription in the RCL Portal as a parameter in the request url. You can acquire the Subscription Id in the Subscription Details section in the RCL Portal.

image

  • Scroll down and copy the ‘Subscription Id’

image

Base URI

The base URI for the RCL Core API is :

https://rclapi.azure-api.net

API Endpoint and Method

The endpoint for the Order Create API is :

/production/ssl/core/v1/order/subscription/{subscriptionid}/create

where the placeholder : {subscriptionid} is the Subscription Id of the user’s subscription in the RCL Portal.

A POST request must be made to the endpoint.

Request Body

The request body should include a JSON of the CertificateRequest class.

Example Request

POST /production/ssl/core/v1/order/subscription/subscr9836/create HTTP/1.1
Host: rclapi.azure-api.net
Authorization: Bearer eyJ0eXAiOi..p1tiXcUnFA
Content-Type: application/json

{
    "hostName" : "www.shopeneur.com",
    "rootDomain" : "shopeneur.com",
    "email":"support@rclapp.com",
    "challengeType":"DNS",
    "isSAN":false
}

Notes

  • hostName - the hostName is the domain you are requesting the certificate for. Example: apex domain - contoso.com, sub domain - store.contoso.com, www sub domain www.contoso.com, wild card domain - *.contoso.com

  • rootDomain - the root domain is the ‘apex’ domain for the hostName. For instance, the root domain for the hostName: ‘shop.contoso.com’ is ‘contoso.com’. Similarly, the root domain for the hostName : ‘contoso.com’ is also ‘contoso.com’

  • challengeType - The challenge type used to validate your domain. To validate your domain with the HTTP challenge, you will be required to place a file in the root of your website and ensure that this file can be accessed publicly on the web. To validate your domain with the DNS challenge, you will be required to create a DNS TXT record in your domain settings with your domain registrar. The DNS challenge supports wildcard domains (*.contoso.com).

  • isSAN - specify if the certificate is a SAN certificate. A Subject Alternative Name (SAN) SSL/TLS certificate will contain multiple domains in a single certificate. A SAN certificate created with the HTTP Challenge will contain the naked apex domain (e.g. contoso.com) and the www subdomain (e.g. www.contoso.com) in a single SSL/TLS certificate. A SAN certificate created with the DNS Challenge will contain the naked apex domain (e.g. contoso.com) and a wild card domain (e.g. *.contoso.com) in a single SSL/TLS certificate. For a SAN certificate, the hostName MUST be an apex domain (eg: contoso.com) AND the rootDomain MUST be the same as the hostName. Host names must not include multiple domains, sub-domains, commas (,) and asterisk (*).

Response

200 Ok

This represents success in making an authorized request to the RCL Core API. An Order entity to represent the certificate order is provided in the body of the response in JSON format.

Example Response Body

{
    "status": "pending",
    "validationTokens": [
        {
            "tokenName": "_acme-challenge.www",
            "tokenValue": "hW9A7-hOZw1WQxLaxZbZRtrn5r3Tq9ufJ5IYxCODB3w",
            "challengeType": "DNS"
        }
    ],
    "challenges": [
        {
            "challengeType": "http-01",
            "status": "pending",
            "token": "OavU5bQv41k5885ofozqxSJs5TgCulc4THtfdixGWdQ"
        },
        {
            "challengeType": "dns-01",
            "status": "pending",
            "token": "OavU5bQv41k5885ofozqxSJs5TgCulc4THtfdixGWdQ"
        },
        {
            "challengeType": "tls-alpn-01",
            "status": "pending",
            "token": "OavU5bQv41k5885ofozqxSJs5TgCulc4THtfdixGWdQ"
        }
    ],
    "orderUri": "https://acme-v02.api.letsencrypt.org/acme/order/527702946/93863252796",
    "certificateUri": null
}

401 Unauthorized

The authorization failed for the request. Check the body of the response for additional error details in text/plain format.

400 Bad Request

An error occurred while processing the request. Check the body of the response for additional error details in text/plain format.