certificate.issued
Fires when a certificate is emitted to a recipient (via API or platform).certificate_url and certificate_hash are null at this stage.
They become available after the recipient accepts the certificate (certificate.accepted).certificate.accepted
Fires when the recipient accepts the certificate. The certificate is now on their public profile.certificate.rejected
Fires when the recipient declines the certificate.certificate.expired
Fires when a certificate passes its expiration date (checked daily).Looking for a
recipient.registered event (fired when a recipient signs up)?
It’s on the roadmap but not yet implemented. Subscribe to certificate.accepted —
it fires when a recipient accepts a certificate, which only happens after they have a profile.