Credential ID

Where to find yours

If you have been asked for a credential ID, most often by LinkedIn and sometimes on a job application, it is on the credential itself. Look in this order:

• The verification page. If your certificate links to a page that confirms it, the ID is shown there and is usually the last part of that page's web address.
• The certificate document. Printed near the bottom or beside the QR code, labelled certificate number, credential ID, or reference.
• The issuing email. Frequently included in the message that delivered the credential, which is worth searching before contacting anybody.

If none of those has one, your certificate may simply not have an ID. Plenty of legitimate certificates do not. Adding a certificate to LinkedIn covers what to put in the field when that is the case.

What it is for

An ID converts a general claim into a specific one. "I hold a project management certificate from this academy" is a statement somebody has to take on trust. "I hold credential 8740592c-0a1d-47fc-be79-6c9ab400626e" points at one record, which either exists and matches, or does not.

That is the whole function. It is not a security feature, and it is not secret: an ID that anyone can look up is an ID doing its job. What it provides is a precise thing to check. Verifying a certificate online is largely the business of turning an ID into an answer.

What a good one looks like

For issuers choosing a format, the requirements are short and unforgiving.

• Unique across everything you have ever issued, not just within a cohort. IDs that restart each intake collide the first time two batches are compared.
• Not guessable. Sequential numbers leak how many credentials you have issued, and let anyone who holds one enumerate the rest by counting. CERT-2026-0001 tells a stranger where to look for CERT-2026-0002.
• Permanent. An ID that changes when a detail is corrected breaks every link already shared, which defeats the purpose of having issued one.
• Transcribable. Someone will read it over the phone or copy it off a printed page. Long strings are fine; ambiguous ones are not.

How ours work

Every credential issued here gets a UUID: a 36-character random identifier with enough range that collisions are not a practical concern and enumeration is not possible. The verification URL is derived directly from it, which is what makes it stable: correcting a spelling changes what the page says, never where the page is. A link shared on LinkedIn two years ago still resolves to the corrected credential.

The consequence is one worth stating plainly, because it is the practical argument for the whole arrangement: fixing a name after issuance costs nothing that has already been shared.

An ID on its own proves nothing

A credential ID is a pointer, not evidence. Anyone can invent a plausible-looking one, and a forged certificate with a convincing reference number is a common enough object. The ID is only worth anything when it resolves, meaning that looking it up at the issuer produces a matching record, ideally one carrying a digital signature that can be checked. An ID that leads nowhere is decoration.