Connection in 5 minutes, 30 days on tests, try.
Free Turnkey setting, Instructions.
Click on the name of the event to see the available fields.
API documentation — here.
Not
Id | Name |
---|---|
call_id
|
The unique identifier of the call |
start
|
The sign of the main shoulder (the first in the chain): yes (1) or no (0) |
timestamp
|
A timestamp in Unix Timestamp format |
from
|
The caller's number |
to
|
The number of the called subscriber |
account_id
|
The unique identifier of the agreement |
authorizing_id
|
The unique identifier of the device that received the call |
bridge_id
|
Only for start = 0, the unique identifier (call_id) of the previous call shoulder helps to track call transfers |
+ You can add your fields that are in webhuk.
Not
Id | Name |
---|---|
call_id
|
The unique identifier of the call |
start
|
The sign of the main shoulder (the first in the chain): yes (1) or no (0) |
timestamp
|
A timestamp in Unix Timestamp format |
from
|
The caller's number |
to
|
The number of the called subscriber |
account_id
|
The unique identifier of the agreement |
authorizing_id
|
The unique identifier of the device that received the call |
bridge_id
|
Only for start = 0, the unique identifier (call_id) of the previous call shoulder helps to track call transfers |
+ You can add your fields that are in webhuk.
Not
Id | Name |
---|---|
call_id
|
The unique identifier of the call |
start
|
The sign of the main shoulder (the first in the chain): yes (1) or no (0) |
finish
|
The sign of the final leverage: yes (1) or no (0) |
is_success
|
The sign of a successful call: yes (1) or no (0) |
duration
|
Duration of the call |
timestamp
|
A timestamp in Unix Timestamp format |
from
|
The caller's number |
to
|
The number of the called subscriber |
internal
|
Internal (extension) number of the SIP account |
account_id
|
The unique identifier of the agreement |
authorizing_id
|
The unique identifier of the device that received the call |
bridge_id
|
Only for start = 0, the unique identifier (call_id) of the previous call shoulder helps to track call transfers |
+ You can add your fields that are in webhuk.
Not
Id | Name |
---|---|
call_id
|
The unique identifier of the call |
timestamp
|
A timestamp in Unix Timestamp format |
from
|
The caller's number |
to
|
The number of the called subscriber |
account_id
|
The unique identifier of the agreement |
authorizing_id
|
The unique identifier of the device from which the call came |
+ You can add your fields that are in webhuk.
Not
Id | Name |
---|---|
call_id
|
The unique identifier of the call |
is_success
|
The sign of a successful call: yes (1) or no (0) |
duration
|
Duration of the call |
timestamp
|
A timestamp in Unix Timestamp format |
from
|
The caller's number |
to
|
The number of the called subscriber |
internal
|
Internal (extension) number of the SIP account |
account_id
|
The unique identifier of the agreement |
authorizing_id
|
The unique identifier of the device from which the call came |
+ You can add your fields that are in webhuk.
Not
Id | Name |
---|---|
call_id
|
The unique identifier of the call |
is_success
|
The sign of a successful call: yes (1) or no (0) |
duration
|
Duration of the call |
timestamp
|
A timestamp in Unix Timestamp format |
from
|
The caller's number |
to
|
The number of the called subscriber |
internal
|
Internal (extension) number of the SIP account |
account_id
|
The unique identifier of the agreement |
authorizing_id
|
The unique identifier of the device from which the call came |
+ You can add your fields that are in webhuk.
If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.
Click on the name of the action to see the available fields.
API documentation — No.
There are no actions, try Change to replace the services.
1 | Configure the connection for: Service in Apimonster. |
2 | Configure Webhuk in: Service, indicating the link from Apimonster. |
3 | Configure the connection for: Service in Apimonster, indicating the login/password/token for access to the API. |
4 | Create a bunch. |
5 | Indicate as a data source: Service. |
6 | Create the required action for: to_Service, indicating in which fields: to_Service to transmit field values from: from_Service. |
7 | Configure filters for each step if necessary. |
8 | Test the bundles and make sure that they work according to the TOR. |
Or go through the full well on ApiMonster.
Ready-made customized