Feature Requests

Be able to create collections via API instead of manually.

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.

Malicious actors can use our API calls to pull credentials based on its current structure (first name + last name + six digits) and grab credentials accredited to users with the same name. They can then share this credential on LinkedIn / use it on their CVs.

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

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"

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.

You can currently update a team member by API and give them access to specific groups by providing the relevant group IDs. However, NUS would like to be able to give them access using group tags, not group IDs. This cannot be done currently using API.