Map internal bbb messages to external messages to easily build an API to receive events;
Permanent hook:
Can't be deleted via API;
Won't expire even if callback fails for a long time;
URL defined in configs;
Global;
Receive either raw¹ or mapped² messages (configurable);
Send up to X (configurable) messages on a single request (when they are simultaneously at the same queue);
Limit queue to a defined size;
Add new parameter to hooks/create: "getRaw=true/false" allowing hooks to receive raw messages instead of mapped ones;
Each hook has it's own event queue and emit events asynchronously;
Map userID;
Update packages;
Convert to JS ES6;
"auth2_0" (configurable : true = use this method, false = use checksum method): Send data as a JSON with a bearer authorization (which is the shared secret), to the defined callbackURL, without the checksum.
The "config.js" file is initially set in a way it'll not use the features until properly configured, to allow compatibility, which means created hooks will get:
Raw messages;
Only 1 message per POST;
Use checksum auth.
¹ - a message in the exact format sent by BBB.
² - few preset messages that are mapped to a different format, available at: http://docs.mconf.org/apis/webhooks-api/ .
Web Hooks Features:
The "config.js" file is initially set in a way it'll not use the features until properly configured, to allow compatibility, which means created hooks will get:
¹ - a message in the exact format sent by BBB. ² - few preset messages that are mapped to a different format, available at: http://docs.mconf.org/apis/webhooks-api/ .