A small introduction on notification actions and how they work
Callback actions allows you to receive notifications from your selected actions to your selected url.
You can add a URL and select which action notifications you'd like to send towards this URL.
The Notification actions can be found in the notifications section, settings on our Game Bulk Action page of the i3D.net website.
We will be sending these notifications from the following IP address:
188.122.94.89
Please make sure you have whitelisted this IP address in your system.
You can also add custom headers for extra validation, for instance you can set authentication headers using KEY => VALUE inputs on the Notification settings page.
An example of the data that is send to your URL is as follows:
JSON
{
"category":"gameserver",
"action":"steam_update",
"gameserverId":123456,
"ip":"123.456.789.001",
"port":1111,
"gameId":001
}
Following below are all possible actions that we are able to return
steam_update no_auto_restart update preload_deploy preload_remove update_cp stop start remove_install_update create ftp_create recreate_ftp create_startup stop_restart_script start_restart_script remove_keep_instance remove_startup remove_ftp update_user_variable
The above actions are all present under the category gameserver, in this case the action create is called whenever a new gameserver is created (for instance when deploying new instances).
Whenever a notification is send to your appointed URL, a log is created on the Callback actions logs page.
Notifications that have failed can be retried, retrying to send the notification again to the URL.
The Notification actions Logs can be found in the notifications section, logs on our Game Bulk Action page of the i3D.net website.