As we profile APIs available across many different industries, one of the things we keep an eye on is the event-driven architecture in use by leading API providers. Whenever we come across webhooks, we always document the event types in use by providers to help define the types of subscriptions their users can tune into to help understand what is happening across a platform. Allowing them to receive notifications and pushes of data when interesting events occur with specific APIs they are interested in. As we were profiling the digital badge provider Acclaim, we found the event types they used for their webhook subscriptions worth documenting. Acclaim webhooks will notify you of the following events when you are integrated with their platform.
– badge.created: This event is triggered whenever a badge is issued. A badge might be created via the web service or via the Acclaim user interface.
– badge.deleted: This event is triggered whenever a badge is deleted. This should rarely occur. Usually, a badge will change its state to revoked or replaced instead.
– badge.state.changed: This event is triggered whenever the state of a badge changes. When the user accepts a badge, for example, the state changes from pending to accepted.
– badge_template.created: This event is triggered whenever a badge template is created.
– badge_template.changed: This event is triggered whenever a badge template is changed.
– badge_template.deleted: This event is triggered whenever a badge template is deleted.
– pending_badge_notification.sent: This event is triggered whenever a user is notified of a pending badge.
– pending_badge_notification.no_user.sent: This event is triggered whenever an email is sent to a non-registered user for a pending badge.
– pending_badge_notification.unconfirmed_email.sent: This event is triggered whenever an unconfirmed user is notified of a pending badge.
These event types are allowing specific applications, as well as users to tune into events that are happening across the digital badging platform, as well as with specific users, or badge events. Painting another picture of the event-driven architectural landscape, but specifically as it applies to badges, and human resource access and security across companies, organizations, institutions, and government agencies. Enabling integrators to tune into exactly the types of events they want, and tune out the rest of the noise that may be occurring via a platform.
Acclaim digital badging event types add to our vocabulary of event types that are in use by leading API providers. Helping us understand how the most active, and mature API platforms are evolving their infrastructure to be more event-driven, building upon the request/response structure they already have in place. Showing us how the API sector is continuing to evolve, becoming more real-time, and allowing end-users, and platform operators to tune into what matters in an increasingly busy digital world.