Create alias
Changed onCreate an alias: a hostname you own that is served with the settings of one of your CDN resources and with its own SSL certificate.
By default, a Let's Encrypt certificate is issued for the alias automatically. Choose how its domain is validated with challenge_type.
To use your own certificate instead, pass its ID in ssl_id. The certificate must cover the alias hostname; a Let's Encrypt certificate issued for one of your CDN resources cannot be used.
The hostname must be unique across all CDN resources, additional CNAMEs and aliases.
The DNS record the hostname needs for Let's Encrypt domain validation is returned in ssl_provisioning of the alias details.
Request
- Base URLhttps://api.gcore.com
- URLhttps://api.gcore.com/cdn/aliases
- AuthHTTP apikey
Request body
Example request
{
"cname": "shop.example.com",
"resource_id": 4567,
"ssl_id": 890,
"automated": true,
"challenge_type": "http_01",
"active": true
}Response
Successful.
Example response
{
"id": 123,
"cname": "shop.example.com",
"resource_id": 4567,
"automated": true,
"challenge_type": "http_01",
"ssl_id": 890,
"active": true,
"enabled": true,
"status": "active",
"ssl_status": "issued",
"ssl_validity_not_after": "2027-01-01T10:00:00Z",
"created": "2026-09-01T10:00:00Z",
"updated": "2026-09-01T10:05:00Z"
}Changes
- warning
added the new
http_onlyenum value to theresponse property for the response status - info
added the new optional request property
- info
added the optional property
to the response with the status - info
removed the
ssl_errorenum value from theresponse property for the response status - info
removed the
ssl_issuingenum value from theresponse property for the response status
- warning
- breaking
the response property
became nullable for the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- breaking