SSL Checker API + GitHub Integration

Why connect them

The SSL Checker API in GitHub.

GitHub is where developers build software together. Connecting APIs to GitHub enables automated code workflows, intelligent issue management, and CI/CD enhancements. Supercharge your development processes with external data.

What you can build

Workflows worth wiring.

Automatically validate URLs in README files for broken links

Check DNS configurations when deploying to new environments

Verify SSL certificates as part of deployment pipelines

Create issues automatically when external monitoring detects problems

Templates

Ready-made ideas.

New push to repository Check SSL → fail build if certificate is expiring

Check SSL in CI pipeline

Run an SSL check for your project's domain as part of CI. Fail the build if valid_to is within 14 days.

New pull request opened Check SSL → add comment with certificate details

Check SSL on infrastructure PRs

When a PR touches domain or infrastructure config, check SSL and comment with valid_to, issuer CN, bits, and subject CN.

Setup

Connect it in a few steps.

Set up with Zapier

1
Set the trigger. Create a Zap with GitHub as the trigger app and "New issue" as the event. Connect your account.
2
Add the API action. Add APIVerve as the action, select the SSL Checker API, and map your trigger data to the request.
3
Send it back. Add a second GitHub action for "Create issue" and map the returned fields (like subject) into it.
4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.

Set up with Make

1
Add the trigger. Create a scenario and add a GitHub module set to "New issue". Authenticate your account.
2
Call the API. Add an HTTP module pointing at api.apiverve.com/v1/sslchecker with your x-api-key header. Pass the trigger's data as the input.
3
Parse & map. Add a JSON module to read the response, then a GitHub module for "Create issue". Map fields like data.subject into place.
4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.

Set up with n8n

1
Add the trigger node. Start a workflow with a GitHub trigger node for "New issue" and connect your credentials.
2
Add an HTTP Request node. Point it at api.apiverve.com/v1/sslchecker using Header Auth (x-api-key). Feed in the trigger data.
3
Map with expressions. Add a GitHub node for "Create issue" and reference the response with expressions such as {{ $json.data.subject }}.
4
Execute & activate. Execute manually to verify, then activate the workflow for production.

The payload

What GitHub receives.

subjectC, ST, O, CN

issuerC, O, CN

subjectaltname"DNS:ebay.com, DNS:befr.ebay.be, DNS:benl.ebay.be, DNS:caf…"

infoAccessCA Issuers - URI, OCSP - URI

cafalse

bits2048

SSL Checker API + GitHub