How verification works
Why an Incredify badge can't be faked, in plain English — plus did:web, Open Badges 3.0, and the API.
A PDF certificate cannot be checked without contacting whoever issued it, and anyone with an image editor can produce one. The problem digital credentials solve is letting a stranger confirm a credential is real without contacting you.
The short version
- 1When you set up your organization, we generated a keypair: a private signing key (secret, encrypted, never leaves the server) and a public key.
- 2Your public key is published on the web at an address derived from your subdomain, so anyone can fetch it.
- 3Every badge you issue is signed with the private key, producing a signature that could only have been made by the holder of that key, which is Incredify on your behalf.
- 4Anyone can fetch your public key and check the signature. If it matches, the credential was issued from your Incredify account and hasn't been altered — not one character.
Why an altered badge fails verification
The signature covers the entire credential — recipient, badge name, criteria, date, evidence. Change any of it and the signature stops matching. A valid signature needs the private key, which Incredify holds encrypted on its servers.
did:web — your issuer identity
Your organization's identifier is did:web:incredify.net:issuers:<your-subdomain>. A DID is a decentralized identifier. The did:web method resolves it to a document published on the web, listing the public keys your badges are signed with. Incredify serves that document at incredify.net, so checking a signature depends on incredify.net being available.
This is why the subdomain is permanent: it is part of your identity, and every credential you have ever issued points at it.
Open Badges 3.0
Credentials are issued as W3C Verifiable Credentials using the Open Badges 3.0 data model, an open format rather than a proprietary one. If you ever leave, your recipients' credentials keep verifying for as long as Incredify continues to publish your issuer's public key at incredify.net.
What a verification actually reports
- Signature valid — issued by this organization and unmodified.
- Not revoked — the issuer hasn't withdrawn it. This is why revoking beats deleting: the record stays checkable and honestly reports its status.
- Not expired — where the issuer set a valid-until date. A badge with no date does not expire. One past its date is reported as expired; its page and file can still be opened.
Verifying programmatically
Verification is a public endpoint. No key, no account:
Verify a credential
curl https://incredify.net/api/verify/<assertion-id>Rate-limited to 60 requests per minute per IP address. The raw credential and the did:web document are also public:
Credential and issuer identity
curl https://incredify.net/api/assertions/<assertion-id>/credential.json
curl https://incredify.net/api/assertions/<assertion-id>/credential.jwt
curl https://incredify.net/issuers/<your-subdomain>/did.jsondid.json is a machine endpoint
/issuers/<slug>/did.json returns a JSON document for verifiers, not a page for people. Your human-facing public page is at /s/<slug> and <slug>.incredify.net — see Branding.
Related
Still stuck?
Email us at hello@incredify.net — a human will answer.