> 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/divoc-demo/issue-and-verify-certificates.md).

# Issue and Verify Certificates

## What does this module allow? 

* It allows issuing authorities to issue digitally verifiable certificates. 
* The [**facility app**](/divoc-wiki-3.1/divoc-demo/facility-app.md) can be used to generate digital certificates, as well as distribute them.
* The staff of a particular facility can use the [**facility app**](/divoc-wiki-3.1/divoc-demo/facility-app.md) to verify a beneficiary.
* Certificates can also be verified and downloaded via the [**citizen portal**](https://divoc.digit.org/divoc-wiki-3.1/divoc-demo/pages/ZewaVGl8Ggsp0imFvYlb#3.-for-certificate-verification).  
* If the country has an authorised third-party app, it can be integrated with DIVOC's credentialing module to fetch certificates from the certificate registry and view/download them.
* Click [**here**](/divoc-wiki-3.1/platform/divocs-verifiable-certificate-features-2.0.md) to know more on the certificate generation service of DIVOC.

*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/divoc-demo/issue-and-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.