Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-05

Verify an Ingestia Academy credential

How to check whether an Ingestia Academy credential is authentic and valid — through the validation page, the code, the fingerprint, the certificate's QR code or the signed JSON (Open Badges 3.0) — and what each state means.

On this page (12)

Verification is public and free.

Every Ingestia Academy credential (the ICF badge and the ICED Data, ICBI BI, ICIA AI Agents and ICSA Solutions Architect certifications) has a public code, a fingerprint and a verification page. The page is the source of truth: what it shows prevails over any PDF, image or post — including over the digital signature.

Permissions#

  • Verifying does not require an account: anyone with the code or the link can check.
  • Only the holder decides whether the name appears on the page (consent at issuance and the option to hide it later). Without consent, the page shows only the credential and the state — and that does not make it any less valid.

How to verify#

1. Through the validation page (fastest)

Open https://ingestia.io/academy/validar and paste the code or the fingerprint. The page finds the credential and takes you to its page, which states the state. It requires neither an account nor JavaScript.

If nothing is found, the answer is always the same — "We couldn't find a credential with that code or fingerprint" — both for a code that does not exist and for a mistyped code. That is deliberate: the uniform answer prevents anyone from discovering valid codes by trial and error.

2. Through the code

  1. Take the code from the certificate, from the e-mail or from the LinkedIn profile (format ABCD-EFGH-JKLM-NP; hyphens, spaces and capitals do not matter).
  2. Open https://ingestia.io/academy/credencial/<code>.
  3. Read the status banner at the top (valid, expired or revoked), the holder, the certification, the dates and the Technical verification block.

3. Through the fingerprint

Every credential has a fingerprint: the cryptographic digest (SHA-256) of the signed document, shown in eight groups of four characters.

text
A1B2 C3D4 E5F6 7890 1A2B 3C4D 5E6F 7081

It appears in three places, always the same: in the footer of the printed certificate, in the Technical verification block of the credential's page and in the JSON from the API (field fingerprint; the full 64-character digest goes in fingerprintSha256).

What it is for: checking whether the paper in your hand is this record. Whoever receives a printed certificate or a screenshot compares the eight groups with what the page shows — if they match, the document corresponds to the signed record. If they don't match, the paper is not from that credential.

How to use it:

What you haveWhat to do
The paper and the linkCompare the eight groups in the footer with those on the page. They must be identical.
Only the paperType the groups into https://ingestia.io/academy/validar (spaces do not matter; the first 16 characters are already enough).
The signed fileRecompute it: the fingerprint is the SHA-256 of the jws in UTF-8 — for example shasum -a 256 over the token.

4. Through the certificate's QR code

Point the camera at the printed QR code: it opens the same verification page. A printed certificate proves nothing on its own — the proof is the page opened right then.

5. Through the signed JSON (integrations)

  • GET https://ingestia.io/api/academy/credencial/<code> returns { v, status, revokedReason, credential, jws, verifyUrl, fingerprint, fingerprintSha256 } — credential is the Verifiable Credential (Open Badges 3.0 / VC 2.0) and jws is the signed token (EdDSA/Ed25519, header with kid).
  • With the header Accept: application/vc+jwt, the response is the raw JWS.
  • Public keys: GET https://ingestia.io/api/academy/jwks. Issuer profile: GET https://ingestia.io/api/academy/issuer.
  • The JSON does not contain the holder's name or e-mail: only a salted hash of the e-mail (IdentityObject, hashed: true).

What each state means#

StateMeaningWhat to do
ValidActive record at the Ingestia Academy, within its validity period (1 year).Nothing — the credential is up to date.
ExpiredPast the expiry date; the holder can recertify (short recertification exam, charged like the original).Treat it as history, not as a current qualification.
RevokedCancelled by the Academy or at the holder's request. The page states the reason (holder's request, account deleted, fraud, issuance error).Do not accept the credential. A revoked one still has a valid signature — which is why the page is what counts.

States of the signature ("Technical verification" block):

  • Valid — the JWS checks out against the public key of the kid indicated.
  • Invalid — the content was altered or was not signed by us.
  • Not verifiable — unknown or momentarily unavailable key; the state on the page still holds.

Example#

A recruiter receives a PDF titled "Analista de Dados Ingestia". They open the QR code, and the page shows Revoked — at the holder's request. The PDF is correct as a document, but the credential is no longer valid: the decision belongs to the page, not to the paper.

Another case: the recruiter receives only a photo of the certificate, with no working link. They type the eight groups of the fingerprint into https://ingestia.io/academy/validar, land on the credential's page and see Valid — the photo corresponds to a real record. If the fingerprint led nowhere, the photo would not be of a credential of ours.

Cost#

  • Verifying (validation page, link, QR code, fingerprint, JSON): R$ 0, with no sign-in.

Security#

  • Codes are neither sequential nor guessable; a nonexistent code, an invalid code and a fingerprint that does not match all answer the same thing — both on the credential's page and on the validation page.
  • The fingerprint shown has 128 bits (32 hexadecimal characters) and is derived from the signed document: altering any byte of the credential changes the whole digest. It reveals nothing about the holder.
  • The credential's page is not indexed by search engines (noindex), but it does generate a preview when shared (LinkedIn). The preview does not carry the name when it is hidden. The validation page (with no query) is public and indexable; with a query in the address, it drops out of the index.
  • Verification is rate-limited by IP address to prevent scanning.

Limits#

  • The page and the JSON reflect the record at the moment of access; the JSON may be cached for up to 5 minutes.
  • Searching by fingerprint finds the credentials issued from October 2026 onwards. Older credentials display the fingerprint normally (it is computed from the signed document), but they are looked up by code until the backfill load runs.
  • The issuance e-mail is a courtesy (it may not arrive in every environment); the verification page is the official channel.

Next steps: Support Center · Status and known limitations.

Related links