> For the complete documentation index, see [llms.txt](https://sunbird.gitbook.io/sunbird-spark/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sunbird.gitbook.io/sunbird-spark/learn/components/verifiable-credentials-and-certificates.md). # Verifiable credentials and certificates #### Certificate issuance Certificates in Spark are issued automatically when a learner meets the completion criteria for a course batch. A certificate: * Is generated as an `SVG` file * Contains the learner's name, course name, batch name, issue date, and a unique certificate ID * Is stored in **Sunbird RC** (Registry and Credentialing) * Is publicly verifiable through a unique verification URL #### Certificate download Learners can download their certificate as a `PDF` from the User Report page or learning passbook. The `SVG` is converted to `PDF` locally in the browser. #### Certificate reissue If a learner's certificate was issued incorrectly, such as because of a name mismatch, administrators can trigger a certificate reissue from the batch management interface. #### Public verification Every certificate has a public verification URL. Anyone, including employers and institutions, can visit that URL to confirm that the certificate is genuine and platform-issued. No account is required. {% hint style="info" %} **Upcoming:** Sunbird RC `v2`, with support for the `W3C Verifiable Credentials (VC)` standard, is planned for the April to June 2026 release. `RC v1` is the current implementation. {% endhint %} --- # 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://sunbird.gitbook.io/sunbird-spark/learn/components/verifiable-credentials-and-certificates.md?ask=&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.