# G2P OpenID VCI: Rest API

### Module name

g2p\_openid\_vci\_rest\_api

### Module title

G2P OpenID VCI: Rest API

### Technology base

[Odoo](https://www.odoo.com/)

### Functionality

This module exposes the following [OpenID for VCI](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html) REST APIs.

The endpoints and their descriptions are given below.

<table><thead><tr><th width="417">Endpoint</th><th>Description</th></tr></thead><tbody><tr><td><code>/api/v1/vci/credential</code></td><td><p>The main credential request API.</p><ol><li>Gets the issuer based on scope, credential type, and supported format.</li><li>Verifies and validates auth JWT based on issuer config.</li><li>Retrieves registrant data based on issuer config and auth JWT sub.</li><li>Issues the credential based on credential format.</li></ol></td></tr><tr><td><code>/api/v1/vci/.well-known/openid-credential-issuer</code></td><td><p>Issuer metadata API.</p><ul><li>collates the <code>issuer_metadata</code> of all issuers and return</li></ul></td></tr><tr><td><code>/api/v1/vci/.well-known/openid-credential-issuer/</code><mark style="color:orange;"><code>{SafetyNetIssuer}</code></mark></td><td><p>Specific Issuer metadata API.</p><ul><li>Gets individual metadata of each issuer by suffixing the API with Issuer Name.</li></ul></td></tr><tr><td><code>/api/v1/vci/.well-known/contexts.json</code></td><td>All the contexts from all the Issuers are collated and returned on this API. This path will be included in as context path within the VC.</td></tr></tbody></table>

### Source code

<https://github.com/openg2p/openg2p-vci>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.openg2p.org/1.3/pbms/developer-zone/odoo-modules/g2p-openid-vci-rest-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.