SSL monitoring API · Certificate monitoring API · Expiry alerts

SSL Monitoring API for Certificate Expiry Alerts

Need a certificate monitoring API for expiry checks, CI/CD gates, uptime monitors, or alert routing? Certimon already monitors public HTTPS certificates, sends expiry alerts through Telegram, Microsoft Teams, and PagerDuty, and provides a limited one-shot SSL check for public domains on port 443. A self-serve monitoring REST API is planned, and this page explains what you can use today without overpromising what is not live yet.

Start free monitoring Contact us for API early access

Free SSL monitoring · Public-domain checks · Telegram, Teams, and PagerDuty alerts · REST monitoring API planned

What Certimon's SSL monitoring API supports today

Certimon is not yet a self-serve, token-authenticated monitoring REST API. There are no public /v1/domains, /v1/check, API-key, or bearer-token endpoints for customers to manage certificate monitoring programmatically today.

What is live today is the monitoring core teams usually want behind an SSL monitoring API: Certimon checks public HTTPS certificates, tracks expiry windows, and sends alerts before certificates become an outage. You can add domains through the web dashboard or Telegram bot, then route notifications to the alerting channel your team already uses.

For one-off checks, Certimon also exposes a limited public SSL check capability for public domains on port 443. If your need is a single request/response lookup rather than continuous monitoring, compare the request and response shape on the SSL Checker API page.

Short version: use Certimon now for free certificate expiry monitoring and alert delivery. If you need full programmatic create/read/update endpoints, contact us for API early access and share the workflow you want to automate.

Current API status at a glance

What is available now, what is limited, and what is planned for the certificate monitoring API.

Capability	Status	Notes
Free SSL certificate monitoring	Available now	Add public domains through the dashboard or Telegram bot.
Expiry polling and reminders	Available now	Certimon checks monitored certificates and sends reminder-window alerts.
Telegram alerts	Available now	Bot-based alerts for configured domains.
Microsoft Teams alerts	Available now	Delivered through Teams Workflows webhook integration.
PagerDuty alerts	Available now	Delivered through PagerDuty Events API v2.
One-shot public SSL check	Available now, limited	Public domains on port 443 only. No arbitrary ports or private hostnames.
Self-serve monitoring REST API	Planned	Token-authenticated `/v1` endpoints are not live yet.
Bulk inventory exports	Not available today	Treat as a future API requirement, not a current feature.
Compliance or SLA guarantees	Not claimed	Certimon is a lightweight monitoring and alerting service.

Use cases for a certificate monitoring API

Teams search for an SSL monitoring API when certificate state needs to feed another workflow. Certimon covers the alerting workflow today and is shaping its planned REST API around the following use cases.

Certificate inventory checks

Keep a list of public hostnames and know which certificates are valid, expiring soon, expired, or misconfigured. Today, Certimon helps by monitoring domains you add in the dashboard or Telegram bot. A future certificate monitoring API should make this inventory easier to read and update from asset-management systems.

For one-off certificate metadata such as issuer, expiry date, and hostname validity, see the SSL Checker API guide.

Expiry polling

A good SSL monitoring API should poll certificates on a schedule, normalize the result, and avoid duplicate noisy alerts. Certimon already handles expiry reminders for monitored public domains so you do not need to maintain a cron job around openssl, curl, or custom TLS scripts.

If you only need to check an expiry date manually, use the free check SSL certificate expiration date tool.

CI/CD checks

Deployment pipelines often need a fast certificate sanity check before promoting a domain, changing DNS, or shipping a customer-facing endpoint. Certimon's current public one-shot check is suitable for simple public-domain checks on port 443. Full CI/CD automation with API tokens, private hostnames, arbitrary ports, and structured build failures belongs to the planned monitoring API rather than the current product surface.

Uptime monitors

Uptime monitors catch HTTP failures, but certificate failures can break users before application code is involved. Certimon complements uptime monitoring by watching the TLS certificate itself and sending alerts when renewal windows are reached or a certificate becomes invalid.

Alert integrations

The fastest way to make certificate monitoring useful is to send expiry events where incidents already live. Certimon supports Telegram, Microsoft Teams Workflows, and PagerDuty Events API v2 alerts today, so teams can wire certificate expiry into chat or incident response without building their own monitoring worker.

When to use Certimon now, and when to wait for the REST API

Use Certimon now if your goal is to avoid surprise certificate expirations on public websites and APIs. Add domains, choose reminder windows, and send alerts to Telegram, Microsoft Teams, or PagerDuty. This covers most operational teams that want dependable certificate expiry monitoring without owning another integration.

Wait for the planned REST API, or contact Certimon for early access, if you need to:

create, update, or delete monitored domains from code;
pull certificate inventory into an internal CMDB or asset database;
run build-time certificate gates in CI/CD with API tokens;
check non-standard ports or private/internal hostnames;
export bulk certificate state for compliance reporting;
embed certificate checks into a customer-facing product.

Certimon is collecting API requirements before locking the public endpoint shape. If your workflow depends on an SSL monitoring API, share the endpoints, payloads, and limits you need.

Planned certificate monitoring API shape

The REST monitoring API is planned, not currently self-serve. The examples below show the direction Certimon is considering so teams searching for a certificate monitoring API can evaluate the fit and request early access.

List monitored hostnames

GET /v1/domains
Authorization: Bearer ***

{
  "data": [
    {
      "host": "example.com",
      "port": 443,
      "last_checked_at": "2026-05-25T22:00:00Z",
      "valid_until": "2026-07-25T23:59:59Z",
      "days_remaining": 61,
      "issuer": "Let's Encrypt",
      "status": "ok"
    }
  ]
}

Create or update a monitor

PUT /v1/domains/example.com
Authorization: Bearer ***
Content-Type: application/json

{
  "port": 443,
  "reminder_windows_days": [30, 7, 1],
  "destinations": ["telegram", "pagerduty", "teams"]
}

Run an on-demand check

GET /v1/check?host=example.com&port=443
Authorization: Bearer ***

{
  "host": "example.com",
  "port": 443,
  "checked_at": "2026-05-25T22:01:13Z",
  "status": "ok",
  "days_remaining": 61,
  "valid_until": "2026-07-25T23:59:59Z",
  "issuer": "Let's Encrypt",
  "hostname_matches": true,
  "chain_valid": true,
  "error": null
}

Important: these /v1 endpoints are the planned API shape and are not live customer endpoints today. Current customer workflows should use the dashboard, Telegram bot, supported alert integrations, and the limited public one-shot checker for public domains on port 443.

Alert integrations you can use today

Certimon's current integration surface is alert delivery. That means you can monitor certificates now and receive events through the tools your team already watches.

Use the Certimon bot to add domains, run checks, and receive certificate expiry reminders in a direct chat or group.

Set up Telegram →

Microsoft Teams Workflows

Send certificate expiry alerts into Microsoft Teams using a Workflows webhook, visible where your team discusses incidents.

Set up Teams →

PagerDuty Events API v2

Route expiry warnings into PagerDuty when certificate failures should page the on-call team.

Set up PagerDuty →

One-shot SSL checks are not the same as monitoring

A one-shot certificate check tells you what is true right now: issuer, expiry date, days remaining, hostname match, and validity. Continuous monitoring keeps checking and alerts you when that result changes or crosses a renewal threshold.

Use a one-shot check when you are debugging a domain, validating a deployment, or enriching a single record. Use continuous monitoring when you want to prevent outages. Certimon supports both patterns at different levels today: a limited public check for public domains on port 443, plus ongoing monitoring and alerts through the dashboard and Telegram bot.

For a user-facing lookup flow, send readers to check SSL certificate expiration date. For API request/response design details, link to SSL Checker API.

SSL monitoring API FAQ

Does Certimon have a public SSL monitoring API?

Not as a self-serve monitoring REST API yet. Certimon currently supports free SSL certificate monitoring through the dashboard and Telegram bot, alert delivery through Telegram, Microsoft Teams, and PagerDuty, and a limited one-shot SSL check for public domains on port 443. Token-authenticated /v1 monitoring endpoints are planned.

What is the difference between an SSL monitoring API and an SSL checker API?

An SSL checker API returns certificate details for a single request, such as issuer, expiry date, days remaining, and validity. An SSL monitoring API keeps a list of domains, checks them over time, and sends alerts when certificates approach expiry or become invalid. Certimon's current product focuses on monitoring and alerting, with limited one-shot checks available today.

Can I use Certimon for certificate inventory checks?

Yes for monitored public domains added through Certimon's current dashboard or Telegram workflows. If you need to read or update a large certificate inventory programmatically through an API, that belongs to the planned REST API and is not self-serve today.

Can I run SSL expiry checks from CI/CD?

You can use Certimon's limited public one-shot check for simple public-domain checks on port 443. Full CI/CD automation with API tokens, structured build failures, private hostnames, or arbitrary ports is a planned API use case rather than a current live monitoring API feature.

Which alert integrations are available now?

Certimon supports Telegram alerts, Microsoft Teams Workflows webhooks, and PagerDuty Events API v2 delivery today. These integrations let teams route certificate expiry events into chat or incident response without building their own polling job.

Does Certimon support arbitrary ports or private hostnames?

Not as a public customer capability today. Current public checks are limited to public domains on port 443, and monitored domains should be publicly reachable. Arbitrary ports, private hostnames, and internal network checks should be treated as future API requirements unless explicitly shipped later.

How do I request API early access?

Email info@certimon.com with the workflow you want to automate, expected volume, whether you need reads or writes, required alert destinations, and whether you need CI/CD, inventory, or uptime-monitor integrations. Certimon is using early requirements to shape the monitoring REST API.

Start monitoring certificates now

You do not need to wait for a full certificate monitoring API to prevent expired SSL certificates. Add your public domains to Certimon, choose reminder windows, and send expiry alerts to Telegram, Microsoft Teams, or PagerDuty today. If your team needs programmatic access, contact Certimon and help shape the planned REST API.

Start free monitoring Contact us for API early access