ACME automation,
for telephone numbers.

An RFC 8555 ACME directory, extended with RFC 9448’s TNAuthList identifier and tkauth-01 challenge per ATIS-1000080.v005, so certificate issuance can be authorized against an OCN instead of a domain name.

Directory

Base URL: https://admin.stirshaken.tel/api/acme

GET /directory
{
  "newNonce": "https://admin.stirshaken.tel/api/acme/new-nonce",
  "newAccount": "https://admin.stirshaken.tel/api/acme/new-account",
  "newOrder": "https://admin.stirshaken.tel/api/acme/new-order",
  "meta": {
    "externalAccountRequired": true,
    "website": "https://admin.stirshaken.tel"
  }
}

External Account Binding

Every account must be bound to a pre-issued EAB credential — there is no anonymous issuance path.

Create an EAB key from API Keys → ACME Credentials in your dashboard (requires a paid plan). You’ll get a keyId and an hmacKey, shown once — most ACME clients that support EAB accept these as --eab-kid and --eab-hmac-key.

Revoking an EAB credential immediately deactivates any ACME account already bound to it.

The TNAuthList identifier & tkauth-01 challenge

Authorization here is against an OCN, not a domain — so issuance looks a little different from a typical ACME flow.

A new order’s identifier must be exactly one TNAuthList type, carrying your OCN as a single SPC:

Order identifier
{
  "identifiers": [
    { "type": "TNAuthList", "value": "<base64url DER TNAuthList containing one SPC>" }
  ]
}

The resulting authorization carries one tkauth-01 challenge. Answer it with an Authority Token (the same SPC token used elsewhere in the dashboard) — its fingerprint claim must match your account key’s JWK thumbprint, per the format RFC 9448 and ATIS-1000080.v005 §6.3.4.1 define:

Challenge response
{ "atc": "<SPC Authority Token JWT>" }

Because this isn’t domain validation, a client needs explicit support for TNAuthList/tkauth-01 to drive the flow — mainstream clients built around DNS validation (certbot, acme.sh) won’t do this out of the box. Full walkthroughs and a reference client are in your dashboard once you sign up.

Workflow

  1. 1GET /directory
  2. 2GET /new-nonce
  3. 3POST /new-account, signed with your account key and EAB credential
  4. 4POST /new-order, with a TNAuthList identifier for your OCN
  5. 5POST /authz/{id} to fetch the tkauth-01 challenge
  6. 6POST /chall/{id} with an Authority Token (ATC) for your SPC
  7. 7POST /order/{id}/finalize with a CSR once the order is ready
  8. 8POST /cert/{id} to download the issued certificate chain

Endpoints

GET/directory

Unauthenticated directory of every other endpoint below.

GET/new-nonce

Fetch a fresh anti-replay nonce.

POST/new-account

Create an account, signed with the account key and an External Account Binding.

POST/new-order

Open an order for a TNAuthList identifier (your OCN).

POST/authz/{id}

Fetch the order’s authorization and its tkauth-01 challenge.

POST/chall/{id}

Answer the challenge with an Authority Token (ATC) for your SPC.

POST/order/{id}/finalize

Submit a CSR once the authorization is valid.

POST/cert/{id}

Download the issued certificate chain (application/pem-certificate-chain).

POST/account/{id}

Check account status, or deactivate it.

Limits, errors & what's not supported

Rate limits

120/min per IP for new-nonce, 20/min per EAB credential for new-account, 60/min per account for everything else signed.

Errors

RFC 8555 problem+json, e.g. urn:ietf:params:acme:error:rejectedIdentifier. Every response carries a fresh Replay-Nonce header.

Not yet supported

ACME-native revokeCert and keyChange aren't implemented — revoke a certificate from the REST API or dashboard instead.

Prefer a direct REST integration?

The same certificates are available through a scoped REST API, for systems that’d rather call an endpoint than run an ACME client.

Read the REST API reference →