Credential Offers
OpenAPI documentation for the Credential Offers module
Last updated
OpenAPI documentation for the Credential Offers module
Last updated
Endpoint supports bulk credential offers records handling. Once created you are be able to issue a credential offer from agent using /webapp endpoints. If the agent returns error that the action cannot be completed because it is missing credential offer you must first create the resource here and then try again.
<hr /> The endpoint is not available if API is running in DEMO MODE<hr />**Claim-based access control:** <code>Issuer_Admin</code>, <code>Issuer_User</code>/private/credential-offers
Endpoint returns a paginated result of credential offers.
<hr /> The endpoint is not available if API is running in DEMO MODE<hr />**Claim-based access control:** <code>Issuer_Admin</code>, <code>Issuer_User</code>, <code>Issuer_Auditor</code>/private/credential-offers
Page number to retrieve.If you provide invalid value the default page number will applied <p> <b>Example: </b> 1 </p> <p> <b>Default Value: </b> 1 </p>
Number of records per page. <p> <b>Example: </b> 20 </p> <p> <b>Default Value: </b> 20 </p> <p> <b>Max Value: </b> 100 </p>
If provided value is greater than max value, max value will be applied.
Filter by id query param. <p> <b>Format: </b> filter.id={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.id=$not:$like:John Doe&filter.id=like:John </p> <h4>Available Operations</h4><ul><li>$in</li></ul>
Filter by credentialId query param. <p> <b>Format: </b> filter.credentialId={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.credentialId=$not:$like:John Doe&filter.credentialId=like:John </p> <h4>Available Operations</h4><ul><li>$eq</li></ul>
Filter by credentialNames query param. <p> <b>Format: </b> filter.credentialNames={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.credentialNames=$not:$like:John Doe&filter.credentialNames=like:John </p> <h4>Available Operations</h4><ul><li>$contains</li></ul>
Filter by credentialTypes query param. <p> <b>Format: </b> filter.credentialTypes={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.credentialTypes=$not:$like:John Doe&filter.credentialTypes=like:John </p> <h4>Available Operations</h4><ul><li>$contains</li></ul>
Filter by correlationId query param. <p> <b>Format: </b> filter.correlationId={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.correlationId=$not:$like:John Doe&filter.correlationId=like:John </p> <h4>Available Operations</h4><ul><li>$eq</li></ul>
Filter by search query param. <p> <b>Format: </b> filter.search={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.search=$not:$like:John Doe&filter.search=like:John </p> <h4>Available Operations</h4><ul><li>$fulltext</li></ul>
Filter by subject query param. <p> <b>Format: </b> filter.subject={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.subject=$not:$like:John Doe&filter.subject=like:John </p> <h4>Available Operations</h4><ul><li>$contains</li>
<li>$eq</li></ul>Filter by issuer query param. <p> <b>Format: </b> filter.issuer={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.issuer=$not:$like:John Doe&filter.issuer=like:John </p> <h4>Available Operations</h4><ul><li>$contains</li>
<li>$eq</li></ul>Filter by status query param. <p> <b>Format: </b> filter.status={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.status=$not:$like:John Doe&filter.status=like:John </p> <h4>Available Operations</h4><ul><li>$eq</li></ul>
Filter by createdBy query param. <p> <b>Format: </b> filter.createdBy={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.createdBy=$not:$like:John Doe&filter.createdBy=like:John </p> <h4>Available Operations</h4><ul><li>$eq</li></ul>
Filter by updatedBy query param. <p> <b>Format: </b> filter.updatedBy={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.updatedBy=$not:$like:John Doe&filter.updatedBy=like:John </p> <h4>Available Operations</h4><ul><li>$eq</li></ul>
Filter by createdAt query param. <p> <b>Format: </b> filter.createdAt={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.createdAt=$not:$like:John Doe&filter.createdAt=like:John </p> <h4>Available Operations</h4><ul><li>$gt</li>
<li>$lt</li> <li>$gte</li> <li>$lte</li> <li>$eq</li></ul>Filter by updatedAt query param. <p> <b>Format: </b> filter.updatedAt={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.updatedAt=$not:$like:John Doe&filter.updatedAt=like:John </p> <h4>Available Operations</h4><ul><li>$gt</li>
<li>$lt</li> <li>$gte</li> <li>$lte</li> <li>$eq</li></ul>Filter by issuedAt query param. <p> <b>Format: </b> filter.issuedAt={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.issuedAt=$not:$like:John Doe&filter.issuedAt=like:John </p> <h4>Available Operations</h4><ul><li>$gt</li>
<li>$lt</li> <li>$gte</li> <li>$lte</li> <li>$eq</li></ul>Filter by revokedAt query param. <p> <b>Format: </b> filter.revokedAt={$not}:OPERATION:VALUE </p> <p> <b>Example: </b> filter.revokedAt=$not:$like:John Doe&filter.revokedAt=like:John </p> <h4>Available Operations</h4><ul><li>$gt</li>
<li>$lt</li> <li>$gte</li> <li>$lte</li> <li>$eq</li></ul>Parameter to sort by. <p>To sort by multiple fields, just provide query param multiple types. The order in url defines an order of sorting</p> <p> <b>Format: </b> fieldName:DIRECTION </p> <p> <b>Example: </b> sortBy=id:DESC&sortBy=createdAt:ASC </p> <p> <b>Default Value: </b> updatedAt:DESC </p> <h4>Available Fields</h4><ul><li>createdAt</li>
<li>updatedAt</li> <li>issuedAt</li> <li>status</li></ul>Returns an array of objects with the latest usage date of each credential type.
<hr /> The endpoint is not available if API is running in DEMO MODE<hr />**Claim-based access control:** <code>Issuer_User</code>, <code>Issuer_Admin</code>, <code>Issuer_Auditor</code>/private/credential-offers/type-usage
Fetch one credential offer from issuer
<hr /> The endpoint is not available if API is running in DEMO MODE<hr />**Claim-based access control:** <code>Issuer_Admin</code>, <code>Issuer_User</code>, <code>Issuer_Auditor</code>/private/credential-offers/{id}
Processes the credential offer id passed and creates the information needed to generate a QR code.
<hr /> The endpoint is not available if API is running in DEMO MODE<hr />**Claim-based access control:** <code>Issuer_Admin</code>, <code>Issuer_User</code>/private/credential-offers/{id}/claim
Revokes the credential offer using the credential revocation txId stored. You will need to supply the revocation reason to be stored alongside it. When completed the credential will display revoked on the users wallet and also the verifier will return revoked status if user tries to verify with it.
<hr /> The endpoint is not available if API is running in DEMO MODE<hr />**Claim-based access control:** <code>Issuer_Admin</code>, <code>Issuer_User</code>/private/credential-offers/revoke