> For the complete documentation index, see [llms.txt](https://divoc.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://divoc.digit.org/divoc-wiki-3.1/platform/divocs-verifiable-certificate-features-3.1/how-to-verify-certificates.md).

# How to Verify Certificates

## Offline Verification

DIVOC supports offline verification of the QR code-based digital certificates to support the verification of certificates in connectivity-restricted regions, and make it more user-friendly.&#x20;

The QR code can also be verified by third-party authorised verifier applications to enable domestic and cross-border verification of DIVOC-issued certificates.&#x20;

## Online Verification

DIVOC provides a public portal that allows verifiers (including self-verification by beneficiaries) to verify certificates.

## Specifications

* Request URL: {{baseUrl}}/vc-certification/v1/certificate/verify &#x20;
* SampleUrl:{{baseUrl}}/vc-certification/v1/certificate/HealthProfessional\_1/614894628867
* Request Method: POST
* Headers:
* Content-Type application/json accept application/json
* Authorisation Bearer \<access-token>

## Steps

* Enter the URL: [{{baseUrl}}/verification-app/](http://3.7.57.244/verification-app/).
* The user can scan the QR code on the document.
* After scanning, the user can see all the details on the screen.
* These details can then be matched and easily verified with those on the printed document.

## Request Body

```
{
    "name": "Neha",
    "dob": "1991-11-29",
    "registrationId": "12345-8",
    "gender": "female",
    "registrationCouncil": "Karnataka",
    "latestQualification": "PostGraduate",
    "university": "Delhi University",
    "degreeYear": "2019",
    "systemOfMedicine": "Ayurveda",
    "registrationDate": "2023-01-09",
    "registrationExpiry": "2025-09-09",
    "issuer": "http://www.india.gov.in",
    "issuedOn": "2023-09-09",
    "validFrom": "2023-09-09T21:01:01.121Z",
    "validTill": "2025-09-09T21:01:01.121Z",
    "issuanceDate": "2023-09-09T21:01:01.121Z",
    "certificateId": "614894628867"
}
```

Sample&#x20;

<figure><img src="https://1377276962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZ3Mr7sicTlPeSsH6Scq%2Fuploads%2FazQlN9vDhbomrGhEzXUU%2FScreenshot%202023-04-05%20at%2011.51.42%20AM.png?alt=media&amp;token=c40a196d-f2d8-48b7-b33e-f109e2379bfe" alt=""><figcaption></figcaption></figure>

[![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://divoc.digit.org/divoc-wiki-3.1/platform/divocs-verifiable-certificate-features-3.1/how-to-verify-certificates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
