POST
/v1/certificate/orderOrder SSL certificate
Create a standalone SSL certificate order.
API v1 · Updated 2026-10-21View .md
Call it through the gateway https://api.tino.vn/v1 with a token that has the services:write scope; see Calling the Tino API.
Authentication
Send the token in the header Authorization:
Authorization: Bearer <token>
Tokens that can call it: app tokens (tinoat_, Sign in with Tino) or personal API tokens (tinopat_).
Scopes
services:writeService management
Parameters
Body (JSON)
| Name | Type | Required | Description |
|---|---|---|---|
product_id | integer | Optional | Certificate product ID |
csr | string | Optional | Domain name |
years | integer | Optional | Number of years |
pay_method | integer | Optional | Payment method ID |
approver_email | string | Optional | Email addres used in domain validation |
admin | integer | Optional | Admin contact ID |
tech | integer | Optional | Tech contact ID |
billing | integer | Optional | Billing contact ID |
organization | array | Optional | Organization details |
software | integer | Optional | Server/Software ID |
data | array | Optional | Addditional data required for some products |
aff_id | integer | Optional | Affiliate ID |
Response
No live sample: the route changes real data or the test account has no data for it. The answer is a JSON object; errors follow the common shape in Calling the Tino API.
Error codes
| Error code | Description |
|---|---|
401 · invalid_token | The token is wrong, expired or revoked. |
403 · insufficient_scope | The token lacks the services:write scope. |
403 · ip_not_allowed | A personal API token called from an IP outside its allow-list. |
Business errors of a route usually come as HTTP 200 with {"error": ["<code>"]}; see common error codes.