For each queue there are predefined notifications that we configure for our clients, however notification object can be overridden per each conversion request job POST.
Here is an example of a sample notification object:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
{ "user_notification_targets": { "scrape_status": [ { "type": "api", "uri": "http://mycompany.com/api/callback/status_from_omnirender", "method": "POST", "key": "[removed]" } ], "error_status": [ { "type": "api", "uri": "http://mycompany.com/api/callback/error_from_omnirender", "method": "POST", "key": "[removed]" }, { "type": "email", "address": "internal_support@mycompany.com" } ] } } |
In the above example, when there is a scrape_status update (conversion process and result), you receive an API callback notification in a HTTP POST request made to the URL you specified: http://mycompany.com/api/callback/status_from_omnirender. For each error related issue, you’ll get a notification in a form of email to the given email address: internal_support@mycompany.com but also an API callback to the specified URL: http://mycompany.com/api/callback/status_from_omnirender.