It is possible for consumers to register listeners to certain events. This means that when a certain event occurs, Hyves will call a url you supplied with some information on the change. It is absolutely not necessary to register any listerers if you're not interested in the events, it's just an extra service for those interested.

For information on how to manage your listeners, see the methods list.

Callback

The callback is done using an oAuth POST call. Singing is based on oAuth, this means that all the parameters of the callback are signed with your consumer secret (note: no oauth_token_secret) using oAuth "HMAC-SHA1" signing.

Example post on callback-url

# listenertype bound parameters:
revoked_oauth_token = {oauth_token that was revoked}
 
# always included:
oauth_consumer_key = {your apiconsumer key}
oauth_signature_method = HMAC-SHA1
oauth_timestamp = {timestamp of callback}
oauth_nonce = {random number between 0 and 1000000}
oauth_version = 1.0
oauth_signature = {the oauth signature of above parameters and your apiconsumer secret}

Listeners

At this moment the only type of event you can add a listener for is revoking of an accesstoken.

accesstoken_revoke

A callback from this listenertype will fire only when the user revokes an access token (on the site), not when the accesstoken expires, nor when it is revoked by the consumer. The postbody of the callback will contain the accesstoken that was revoked in post parameter "revoked_oauth_token".

If you have any thoughts on these issues, please discuss them with us in the Hyves API Hyve or send an email to hyves-api[at]hyves[dot]nl