Feature Requests

Request for a way that a recipient's credentials could be linked to each other in such a way that if one credential date is updated, the others will automatically update too. Ideally this could be done through an API call out.

The customer would like the "capability to limit certain API methods with a particular key -e.g. a system only needs to create credentials/certificates – and not manage branding or delete credentials etc"

Food Processing Skills (Org ID: 92085) has two separate pathways for two different audiences and doesn’t want the recipient to be placed in both pathways. They don’t want to use separate departments because of the amount of groups they would have to maintain updating over time. So is it possible to set up API end points for closed enrollment pathways?

We would be very eager for our system to listen to the information of a digital credential being deleted from your end, so as to update our side accordingly.

NUS would like to have an API endpoint to assign email templates

Alexander from Valamis would like to have the meta field for all search endpoints on our API as only credentials and groups have this field currently.