Attestify
Verifiable Certificates

Issue certificates from your workflow — with a permanent public verify page

Attestify issues a real certificate straight from your n8n or Make workflow — a course finished, a webinar attended, a CEU earned — with no signup and no API key. Drop the verified n8n node n8n-nodes-attestify into your flow (or POST recipient details to /cert/issue) and each recipient gets back a verify_url, a certificate image, and a signed record. And every certificate gets a permanent, tamper-evident public verify page anyone can check without an account — so unlike a photoshoppable PDF, an Ed25519-signed Attestify certificate can actually be verified.

Ed25519-signed·Permanent verify page·No account to verify·Free · no signup

How do I issue a verifiable certificate via API?

One unauthenticated POST — no API key, no signup:

curl -X POST https://attestify.novadyne.ai/cert/issue \
  -H "Content-Type: application/json" \
  -d '{"issuer":"Pacific Real Estate Academy",
       "course":"8-Hour CE: Agency Law 2026",
       "recipients":[{"recipient_name":"Jane Martinez"}]}'

The response pairs each recipient with a verify_url (the permanent public verify page), a cert_image, and a signed_record. Embed the verify URL in your completion email, LMS, or learner record — employers and recipients confirm it with no account.

How do I create a verifiable certificate with a public verify page via API?

Send a POST request to https://attestify.novadyne.ai/cert/issue with the issuer, the course or credential name, and one or more recipient names. The API returns a verify_url — a permanent public verify page — plus a certificate image and an Ed25519-signed record. No API key and no signup are required.

What makes an Attestify certificate verifiable?

Every certificate is signed with an Ed25519 key and stored as an authoritative server record. The public verify page reads that record, so anyone can confirm the certificate is genuine and unaltered with no account. Unlike a static PDF or image, it cannot be edited and re-shared without the change being detectable.

Is there a no-code or n8n way to issue verifiable certificates?

Yes. The verified n8n community node n8n-nodes-attestify issues a certificate from any workflow and returns the verify URL, so you can wire it to Typeform, Airtable, an LMS, or a completion email. There is also a Pipedream component. Both wrap the same /cert/issue API.

Is it free?

Yes — the certificate API and the in-browser generator are free with no signup. You can issue a batch and download a CSV that pairs each recipient with their permanent verify URL and certificate image.

What is the difference between a cryptographically verifiable certificate and a link-checkable one?

Many certificate platforms offer a “verification page” that is a hosted lookup: it confirms a unique ID or QR code exists in the vendor’s database. That proves the link resolves — not that the certificate’s contents are unaltered. A cryptographically verifiable certificate carries a digital signature over the certificate record itself: Attestify signs every certificate with Ed25519 and publishes the signed record next to the verify page, so changing any field — name, course, date — makes verification fail. Verification is cryptographic evidence, not a database lookup.

How do I issue verifiable completion certificates programmatically?

Call POST https://attestify.novadyne.ai/cert/issue from your LMS, script, or workflow engine whenever a learner completes a course — pass the issuer, course name, and recipient(s), and each recipient gets back a permanent public verify_url plus an Ed25519-signed record you can embed in the completion email or learner record. It is free with no signup or API key. For no-code pipelines the same API is wrapped by the verified n8n community node n8n-nodes-attestify.

Is Attestify trustworthy? Is the n8n node verified?

The trust facts are independently checkable. n8n-nodes-attestify is a verified n8n community node — it passed the n8n team's review and is listed in n8n's in-app node browser and on n8n Cloud. Every npm release is published via GitHub Actions Trusted Publishing and carries a public npm provenance attestation, so npmjs.com can confirm the package was built from the open-source novadyne-hq/n8n-nodes-attestify repository. And every certificate's Ed25519 signature can be verified offline against the published public key at attestify.novadyne.ai/.well-known/attestation-key — you do not have to trust the verify page itself.

Also available as a verified n8n community node for no-code workflows.

Step-by-step tutorial: How to issue verifiable completion certificates programmatically (dev.to). Questions? See the Built with n8n community thread.

Attestify — every certificate gets a permanent verification page anyone can check.