Order and validate a certificate

This page explains how to choose and buy an SSL certificate, submit the certificate domain, and prove domain ownership with DNS or HTTP validation.

#Choose a certificate

In the console, open Certificates (证书服务) → SSL Certificates (SSL证书) (/ssl/browse). You can filter the catalog by issuing channel at the top of the page. Each product card shows:

• The product name and brand (for example Let's Encrypt, ZeroSSL, DigiCert)
• A type tag: DV, OV, EV, Wildcard or Multi-Domain
• The validity period in days and the price

At the time of writing the catalog contains the following; the catalog page is always authoritative:

How to pick:

• You only need HTTPS encryption: choose DV. 90-day DV certificates need to be renewed regularly.
• You need every first-level subdomain (for example *.example.com): choose Wildcard. Wildcard certificates can only be validated by DNS.
• One certificate for several different names: choose Multi-Domain.
• You want your organization's identity in the certificate: choose OV or EV and have your company details ready.

#Check out and pay

1. On a product card click Add to cart (加入购物车), or Buy now (立即购买) to go straight to the cart (/billing/cart). SSL certificates are a one-time purchase.
2. Review the cart and check out. An invoice is created for the certificate, and a certificate order with status Pending (待处理) appears under My Certificates. No domain is attached yet.
3. Pay the invoice under Billing → Invoices (/billing/invoices).

#Submit the domain and validation method

After payment, submit the certificate domain and validation method for the order; the platform then sends the request to the CA. Currently this step is done through the user API, authenticated with your console login token:

curl -X POST https://api.yeap.cloud/api/user/ssl/orders/create \
  -H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
  -d '{
    "order_id": 123,
    "domain": "example.com",
    "validation_method": "dns"
  }'

Parameters:

On success the order moves to pending validation, and validation_data in the response tells you what to publish. You can fetch it again at any time with GET /api/user/ssl/orders/get?id=<order_id>; the validation_token and validation_value fields carry the record name and value.

#Complete domain validation

#DNS validation (recommended)

Add a TXT record at your DNS provider:

• DV certificates such as Let's Encrypt and ZeroSSL usually use the _acme-challenge prefix. Other CAs may use a different name or record type; always use the data returned for your order.
• Wildcard certificates must use DNS validation.
• If the zone is hosted on Yeap Cloud DNS you can add the record in the console; see the DNS docs.
• DNS changes usually take a few minutes to half an hour to become visible, longer with high TTLs.

#HTTP validation

Publish a validation file on your website so that it is reachable under http://<domain>/.well-known/.... Use the exact path and content returned for your order (for example /.well-known/acme-challenge/<token>). Make sure that:

• The domain resolves to the server hosting the file and port 80 is reachable.
• The URL returns the raw file content and is not intercepted by a login page, firewall or rewrite rule.

#Check validation and issuance

Once your record is live you can trigger a check yourself:

# Re-check validation
curl -X POST https://api.yeap.cloud/api/user/ssl/orders/validate \
  -H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
  -d '{"order_id": 123}'

# Refresh the order status from the CA; fetches the certificate if it has been issued
curl -X POST https://api.yeap.cloud/api/user/ssl/orders/refresh-status \
  -H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
  -d '{"order_id": 123}'

You don't have to poll: the platform automatically checks every order that has been submitted to a CA at regular intervals (about every 30 minutes). When the certificate is issued it is saved automatically, the order changes to Active (生效中), and you can download it from My Certificates.

How long issuance takes depends on the type. DV certificates are usually issued shortly after validation passes. OV and EV certificates also require the CA to vet your organization, which normally takes several business days; the CA may contact you using the details you provided.

#Troubleshooting

• Validation never passes: confirm the record is visible publicly with dig TXT _acme-challenge.example.com and that the value is complete, without extra quotes or spaces. For HTTP validation, open the validation URL with a browser or curl and check the response body.
• The order shows Failed: the CA rejected the request (for example the domain does not meet its issuance policy). The reason is stored on the order and returned by the order lookup endpoint.
• No progress for a long time: contact us with the order ID.