Issue SSL certificate
Start the ACME HTTP-01 flow for a registered domain. ASYNC: synchronously requests authorization from Let’s Encrypt, stores the token + key-authorization, flips status→challenge, and returns the challenge data + a pending ref; the platform then self-checks, validates, finalizes and flips status→active in the background (poll get_ssl_certificate, or await the ssl-certificates.issued / .failed webhook). Use after create. Not idempotent: each call requests a fresh authorization. 409 conflict if the domain is already active (use renew).
Contract:
- MCP tool
issue_ssl_certificate, registry packagemcp.id/ssl_certificates, mountid.platform. - Operation
action, response envelopeaction_async. - Flags: dangerous: the MCP layer gates it behind a preview/commit token, and the effect cannot be undone through this API.
Authorizations
Access token issued by gtm.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.
Team scope for tokens that do not carry one. Ignored when the token already names a team.
Path Parameters
SSL certificate sid (id_sc_…).
18^id_sc_Response
action_async success envelope.