← Blog
·2 min readTechnologyAutomation

ACME vs REST API vs Dashboard: Picking the Right Certificate Workflow

TL;DR
  • A dashboard is the simplest option for a provider with one or two OCNs and infrequent renewal needs.
  • A REST API suits teams that already script around other infrastructure and want certificate operations to be one more scripted call.
  • ACME automation is built for set-it-and-forget-it renewal, but needs a client that understands the TNAuthList identifier — not every generic ACME client does.
  • The right choice depends more on your team’s existing tooling than on OCN count alone.
  • If you’re missing renewal deadlines, evaluate ACME first; if your team already scripts other infrastructure, check a REST API fit; and if you do go ACME, confirm your client actually supports the TNAuthList identifier.

Most STI-CAs offer three ways to manage certificates: a web dashboard, a REST API, or an ACME directory. For a small provider, picking the right one comes down to how your team already operates, not just how many OCNs you have.

The Dashboard: Simple and Manual

For a provider with one or two OCNs and certificates that renew on a predictable annual schedule, a dashboard is often genuinely enough. There's no integration to build or maintain — Telonium already sends automated expiration reminders starting 30 days out, so it's just a few clicks when renewal comes due.

The REST API: Scripted, On Your Terms

A REST API makes sense once certificate operations need to plug into something else you're already doing programmatically — provisioning a new OCN's certificate as part of an onboarding script, for example, or pulling certificate status into an internal dashboard. It's a good fit for teams with some engineering capacity who'd rather script a known, documented API than click through a UI repeatedly.

ACME: Built for Automatic Renewal

ACME (the protocol behind most automated TLS certificate renewal on the web) exists specifically to make renewal a non-event — a client checks in periodically, requests a new certificate before the old one expires, and nothing is left to a human remembering a date. For STIR/SHAKEN, this requires a client that understands the TNAuthList identifier type and the tkauth-01 challenge used to authorize against an OCN rather than a domain name — generic, DNS-oriented ACME clients built for website certificates typically don't support this out of the box.

Making the Call

If missed renewals have been a real problem, ACME is worth the setup investment. If your team already scripts other infrastructure tasks, a REST API probably fits more naturally. And if neither of those describes your situation, there's no shame in sticking with the dashboard — automated expiration reminders already cover the tracking, and it works fine at a small enough scale.

Conclusion

There's no universally "right" certificate workflow — there's the one that matches how your team already works. Pick based on that, not on which option sounds most sophisticated.

This article is provided for general informational purposes only and does not constitute legal or compliance advice. Consult a qualified attorney or compliance professional about your organization’s specific obligations under FCC rules and the STIR/SHAKEN framework.

Need a STIR/SHAKEN certificate?

Telonium is an approved STI-CA — request your first certificate today.