🔗 SSLCI REST API

You can perform SSL certificate operations programmatically with SSLCI.com REST API. All requests are made to https://www.sslci.com/api.

🔐 Authentication

You must send tokens in all API requests. You can send the token in 3 ways:

JSON Body: {"token": "YOUR_TOKEN", ...}
Authorization Header: Authorization: Bearer YOUR_TOKEN
Query String (GET): /api?token=YOUR_TOKEN

📋 endpoints

GET /api — SSL and Order List

It lists all your SSL certificates and pending orders.

curlcurl -X GET "https://www.sslci.com/api?token=YOUR_TOKEN"

Successful Response

json{ "status": true, "certificates": [ { "crt_id": 1, "domains": "example.com", "add_time": 1715000000, "end_time": 1722776000 } ], "pending_orders": [ { "order_id": 5, "domains": "test.com", "status": "pending" } ] }

POST /api — Domain Verification Request

Generates HTTP or DNS verification code for a single domain. Only one domain is accepted.

Parameter

Parameter	Medicine	Compulsory	Description
`token`	string	✅	API token
`domain`	string	✅	Domain to be verified (single)
`method`	string	✅	http or dns

curlcurl -X POST https://www.sslci.com/api \ -H "Content-Type: application/json" \ -d '{"token":"YOUR_TOKEN","domain":"example.com","method":"http"}'

Successful Response

json{ "status": true, "domain": "example.com", "order_id": 42, "verification": { "method": "http", "token": "abc123...", "content": "abc123...thumbprint", "file_path": "/.well-known/acme-challenge/abc123...", "url": "http://example.com/.well-known/acme-challenge/abc123..." } }

PUT /api — Domain Verification Confirmation

Triggers verification after placing the verification file/record. It only authenticates, does not create SSL.

Parameter

Parameter	Medicine	Compulsory	Description
`token`	string	✅	API token
`domain`	string	✅	Domain to be verified
`order_id`	int	❌	Order ID (optional, found automatically)
`method`	string	❌	http or dns (default: http)

curlcurl -X PUT https://www.sslci.com/api \ -H "Content-Type: application/json" \ -d '{"token":"YOUR_TOKEN","domain":"example.com"}'

POST /api (action=finalize) — Creating an SSL Certificate

Creates an SSL certificate with pre-verified domains. All domains must have been verified within the last 29 days.

Parameter

Parameter	Medicine	Compulsory	Description
`token`	string	✅	API token
`action`	string	✅	finalized constant value
`domains`	array	✅	Domain list (pre-verified)

curlcurl -X POST https://www.sslci.com/api \ -H "Content-Type: application/json" \ -d '{"token":"YOUR_TOKEN","action":"finalize","domains":["a.com","b.com","c.com"]}'

Successful Response

json{ "status": true, "key": "-----BEGIN PRIVATE KEY-----\n...", "csr": "-----BEGIN CERTIFICATE REQUEST-----\n...", "crt": "-----BEGIN CERTIFICATE-----\n...", "ca": "-----BEGIN CERTIFICATE-----\n...", "details": { "subject": { "CN": "a.com" }, "valid_from": "2026-05-13 00:00:00", "valid_to": "2026-08-11 00:00:00", "san": "DNS:a.com, DNS:b.com, DNS:c.com" } }

DELETE /api — SSL / Order Deletion

Deletes the SSL certificate or cancels the pending order. Only records belonging to you can be deleted.

Parameter

Parameter	Medicine	Compulsory	Description
`token`	string	✅	API token
`type`	string	✅	ssl or order
`id`	int	✅	crt_id (ssl) or order_id (order)

curlcurl -X DELETE https://www.sslci.com/api \ -H "Content-Type: application/json" \ -d '{"token":"YOUR_TOKEN","type":"ssl","id":15}'

🔄 SAN/Multi-Domain SSL Streaming

To get an SSL certificate with multiple domains, follow these steps:

Get a verification code via POST for each domain separately
Insert verification file/DNS record
Confirm verification with PUT separately for each domain
After all domains are verified, send all domains with POST action=finalize
Your SSL certificate is generated instantly (since the domains are already verified)

⚠️ Error Codes

HTTP Kodu	Anlam
`200`	successful
`400`	Invalid request (missing/incorrect parameter)
`401`	Authentication failed (invalid token)
`403`	Unauthorized access (the recording does not belong to you)
`405`	Unsupported HTTP method
`500`	Server error

SSLCI REST API v1.0 | Informatics Solutions