Automate certificate
issuance and renewal.
A scoped REST API for requesting, renewing, and revoking STIR/SHAKEN certificates from your own systems — Bearer-token auth, per-key scopes, and a stable JSON response shape.
Authentication
Every request is authenticated with a scoped API key, sent as a Bearer token.
Create a key from API Keys in your dashboard (requires a paid plan). The raw token is shown once, at creation — store it somewhere safe, since it can’t be retrieved again.
Authorization: Bearer stir_live_<prefix>.<secret>Every key is scoped to exactly the operations it needs. Available scopes:
certificates:listcertificates:getcertificates:requestcertificates:renewcertificates:deactivatecertificates:revokeEndpoints
Base URL: https://admin.stirshaken.tel/api/v1
/certificatesList the company’s certificates, filterable by status or OCN, paginated. — scope certificates:list
/certificatesRequest a new certificate for one of the company’s OCNs. — scope certificates:request
/certificates/{serial}Look up one certificate by serial, including the full PEM chain. — scope certificates:get
/certificates/{serial}/renewRenew a certificate from its original CSR. — scope certificates:renew
/certificates/{serial}/deactivateRetrieve the certificate’s public x5u URL without revoking it. — scope certificates:deactivate
/certificates/{serial}/revokeTwo-step revoke: returns a 5-minute confirmation token, then executes on the second call. — scope certificates:revoke
Example: request and revoke
The same two-step confirmation the dashboard uses, available from your own systems.
curl https://admin.stirshaken.tel/api/v1/certificates \
-H "Authorization: Bearer stir_live_<prefix>.<secret>" \
-H "Content-Type: application/json" \
-d '{
"ocn": "1234A",
"validityPeriod": "1_year"
}'curl https://admin.stirshaken.tel/api/v1/certificates/<serial>/revoke \
-H "Authorization: Bearer stir_live_<prefix>.<secret>" \
-H "Content-Type: application/json" \
-d '{ "reason": "Key compromised" }'curl https://admin.stirshaken.tel/api/v1/certificates/<serial>/revoke \
-H "Authorization: Bearer stir_live_<prefix>.<secret>" \
-H "Content-Type: application/json" \
-d '{ "confirmationToken": "<token from step 1>" }'A revocation here updates your Telonium account immediately, but iConectiv has no revocation API — you’ll still need to revoke the SPC token manually in the iConectiv portal.
Prefer ACME to a REST integration?
The same certificates are available through a standards-compliant ACME directory, for teams that already run ACME tooling.
Read the ACME reference →