Integration Calltouch (Kolltach) and Bitrix24 (Bitrix24) по API без программиста
Connection in 5 minutes, 30 days on tests, try.
74 834 561
132 198 360
2000+
Free Turnkey setting, Instructions.
What data can be transmitted from: from_Service to: to_Service
If you cannot independently determine whether these events and actions will be able to solve your problem; contact support or use the Full construction setting.
Events c Calltouch
Click on the name of the event to see the available fields.
API documentation — here.
Description
Not
Available fields
| Id | Name |
|---|---|
id
|
The unique identifier of the call in Calltouch. |
ctCallerId
|
Unique client ID in Calltouch |
callerphone
|
The phone number of the client from whom he makes the call |
phonenumber
|
The tracked number that the customer is calling |
subPoolName
|
The name of the subpool that the advertising number is associated with |
redirectNumber
|
The forwarding number to which the customer's call was directed |
duration
|
The duration of a telephone conversation in seconds |
waiting_time
|
Waiting time (beeps before the operator picks up the handset) in seconds |
calltime
|
Date and time of the call the start of the call |
timestamp
|
Date and time of the start of the call in Unix Time Stamp format in seconds |
status
|
Call status (successful - successful call, unsuccessful - unsuccessful call) |
statusDetails
|
Call status details |
unique
|
The flag of the uniqueness of the call. true - unique, false - repeated |
targetcall
|
The flag of the target call. target - target, non-target - non-target call |
uniqtargetcall
|
The flag of a uniquely targeted call. uniqtarget - unique-target call, non-uniqtarget - not unique-target call |
callback
|
Callback or not. callback - callback, non-callback - direct call |
worktime
|
The working or non-working time at which the call came in. worktime - working, non-worktime - non-working |
pool
|
The type of pool the number is assigned to |
rating
|
The rating assigned to the call or request (0 - not assigned, 1-5 - from 1 to 5) |
comment
|
A comment |
tags_auto_pr
|
Calltouch Predict Tags |
tags_auto_af
|
Calltouch Anti-fraud Tags |
tags_auto_gr
|
Tags by client's gender |
tags_auto_ct
|
Tags by extension |
tags_auto_pn
|
Tags by numbers |
tags_manual
|
Manually inserted tags |
tags_api
|
Tags set using the API |
attribution
|
Attribution model. 1 is the last indirect, 0 is the last interaction |
source
|
A source |
medium
|
Channel |
utm_source
|
utm_source tag |
utm_medium
|
utm_medium label |
utm_campaign
|
utm_campaign label |
utm_content
|
The utm_content label |
utm_term
|
utm_term label |
gcid
|
Google Client ID |
yaClientId
|
Yandex Client ID |
sessionId
|
Calltouch session ID |
hostname
|
The monitored site |
url
|
The site login page |
attrs
|
Third-party cookies |
callUrl
|
The call page |
callback_request_id
|
The ID of the callback request |
callback_final_attempt
|
The flag for the end of the call chain |
ref
|
The source of the referral link |
city
|
City |
browser
|
Browser |
os
|
The operating system |
device
|
Device |
ip
|
IP address |
sip_call_id
|
SIP Session ID |
callReferenceNumber
|
The ID of the call from the PBX |
reclink
|
Recording a conversation |
orderId
|
Transaction ID |
siteId
|
Site ID |
siteName
|
The name of the site |
userAgent
|
User agent |
sendingTimestamp
|
Date and time of sending the webhook in Unix Time Stamp format |
text
|
Transcript of the call to text |
manager
|
Call or Request Manager |
spam
|
The spam flag. true - the call is marked as, false - the call is unmarked |
callback_custom_fields
|
Custom fields of Callback widgets |
callback_request_facebook_lead_id
|
Facebook Lead ID |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
id
|
id |
ctCallerId
|
ctCallerId |
callerphone
|
callerphone |
phonenumber
|
phonenumber |
sessionId
|
sessionId |
reclink
|
reclink |
text
|
text |
+ 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.
Actions in Bitrix24
Click on the name of the action to see the available fields.
API documentation — No.
Request fields
| Id | Name |
|---|---|
TITLE
|
The name of the lead |
EMAIL
|
Email address |
PHONE
|
Contact's phone number |
NAME
|
Name |
SECOND_NAME
|
Middle name |
ADDRESS
|
Contact address |
ADDRESS_2
|
The second page of the address |
ADDRESS_CITY
|
City |
ADDRESS_COUNTRY
|
A country |
ADDRESS_COUNTRY_CODE
|
Country code |
ADDRESS_POSTAL_CODE
|
Postal code |
ADDRESS_PROVINCE
|
Area |
ADDRESS_REGION
|
District |
ASSIGNED_BY_ID
|
Associated with the user by ID |
COMMENTS
|
Comments |
CURRENCY_ID
|
Currency identifier |
OPPORTUNITY
|
Estimated amount |
COMPANY_ID
|
Linking a lead to a company |
COMPANY_TITLE
|
The name of the company linked to the lead |
CONTACT_ID
|
Linking a lead to a contact |
BIRTHDATE
|
Date of birth |
HONORIFIC
|
Type of treatment |
IM
|
Messengers |
LAST_NAME
|
Surname |
OPENED
|
Available to everyone |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
Date of birth |
ORIGIN_VERSION
|
The original version |
POST
|
Post |
SOURCE_DESCRIPTION
|
Description of the source |
SOURCE_ID
|
Source ID |
STATUS_DESCRIPTION
|
The original version |
STATUS_ID
|
The original version |
STATUS_SEMANTIC_ID
|
The original version |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
WEB
|
The URL of the lead resources |
Answer fields
| Id | Name |
|---|---|
ID
|
Lead ID |
Request fields
| Id | Name |
|---|---|
ID
|
Lead ID |
Answer fields
| Id | Name |
|---|---|
ADDRESS
|
Contact address |
ADDRESS_2
|
The second page of the address |
ADDRESS_CITY
|
City |
ADDRESS_COUNTRY
|
A country |
ADDRESS_COUNTRY_CODE
|
Country code |
ADDRESS_POSTAL_CODE
|
Postal code |
ADDRESS_PROVINCE
|
Area |
ADDRESS_REGION
|
District |
ASSIGNED_BY_ID
|
Associated with the user by ID |
COMMENTS
|
Comments |
CURRENCY_ID
|
Currency identifier |
OPPORTUNITY
|
Estimated amount |
COMPANY_ID
|
Linking a lead to a company |
COMPANY_TITLE
|
The name of the company linked to the lead |
CONTACT_ID
|
Linking a lead to a contact |
BIRTHDATE
|
Date of birth |
EMAIL
|
Email address |
HONORIFIC
|
Type of treatment |
IM
|
Messengers |
NAME
|
Name |
LAST_NAME
|
Surname |
OPENED
|
Available to everyone |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
Date of birth |
ORIGIN_VERSION
|
The original version |
PHONE
|
Contact's phone number |
POST
|
Post |
SECOND_NAME
|
Middle name |
SOURCE_DESCRIPTION
|
Description of the source |
SOURCE_ID
|
Source ID |
STATUS_DESCRIPTION
|
The original version |
STATUS_ID
|
The original version |
STATUS_SEMANTIC_ID
|
The original version |
TITLE
|
The name of the lead |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
WEB
|
The URL of the lead resources |
Request fields
| Id | Name |
|---|---|
TITLE
|
Name |
CATEGORY_ID
|
The Funnel ID |
ADDITIONAL_INFO
|
Additional information |
ASSIGNED_BY_ID
|
Associated with the user by ID |
BANK_DETAIL_ID
|
Bank account ID |
BEGINDATE
|
Start date |
CLOSED
|
Completed |
CLOSEDATE
|
Completion date |
COMMENTS
|
Comments |
COMPANY_ID
|
ID of the linked company |
CONTACT_IDS
|
ID of the linked contact |
CURRENCY_ID
|
The identifier of the transaction currency |
IS_NEW
|
Flag of a new transaction (i.e. a transaction in the first stage) |
IS_RECURRING
|
The flag of the regular deal template (if it is Y, then it is not a deal, but a template) |
IS_RETURN_CUSTOMER
|
A sign of a repeated lead |
OPENED
|
Available to everyone |
OPPORTUNITY
|
Sum |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
ID of the item in the data source |
PROBABILITY
|
Probability |
REQUISITE_ID
|
The ID of the props |
STAGE_ID
|
Stage ID |
STAGE_SEMANTIC_ID
|
Name |
SOURCE_ID
|
The source ID. Determines the source of the transaction (callback, advertisement, email, etc.). |
SOURCE_DESCRIPTION
|
Additional information about the source. |
TAX_VALUE
|
The tax rate |
TYPE_ID
|
Type of transaction |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
ADDITIONAL_INFO
|
Additional information |
ASSIGNED_BY_ID
|
Associated with the user by ID |
BANK_DETAIL_ID
|
Bank account ID |
BEGINDATE
|
Start date |
CLOSED
|
Completed |
CLOSEDATE
|
Completion date |
COMMENTS
|
Comments |
COMPANY_ID
|
ID of the linked company |
CONTACT_IDS
|
ID of the linked contact |
CURRENCY_ID
|
The identifier of the transaction currency |
IS_NEW
|
Flag of a new transaction (i.e. a transaction in the first stage) |
IS_RECURRING
|
The flag of the regular deal template (if it is Y, then it is not a deal, but a template) |
IS_RETURN_CUSTOMER
|
A sign of a repeated lead |
OPENED
|
Available to everyone |
OPPORTUNITY
|
Sum |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
ID of the item in the data source |
PROBABILITY
|
Probability |
REQUISITE_ID
|
The ID of the props |
STAGE_ID
|
Stage ID |
STAGE_SEMANTIC_ID
|
Name |
SOURCE_ID
|
The source ID. Determines the source of the transaction (callback, advertisement, email, etc.). |
SOURCE_DESCRIPTION
|
Additional information about the source. |
TAX_VALUE
|
The tax rate |
TITLE
|
Name |
CATEGORY_ID
|
The Funnel ID |
TYPE_ID
|
Type of transaction |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
PHONE
|
Contact's phone number |
EMAIL
|
Email address |
HONORIFIC
|
Type of treatment |
NAME
|
Name |
LAST_NAME
|
Surname |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
ADDITIONAL_INFO
|
Additional information |
ASSIGNED_BY_ID
|
Associated with the user by ID |
BANK_DETAIL_ID
|
Bank account ID |
BEGINDATE
|
Start date |
CLOSED
|
Completed |
CLOSEDATE
|
Completion date |
COMMENTS
|
Comments |
COMPANY_ID
|
ID of the linked company |
CONTACT_IDS
|
ID of the linked contact |
CURRENCY_ID
|
The identifier of the transaction currency |
IS_NEW
|
Flag of a new transaction (i.e. a transaction in the first stage) |
IS_RECURRING
|
The flag of the regular deal template (if it is Y, then it is not a deal, but a template) |
IS_RETURN_CUSTOMER
|
A sign of a repeated lead |
OPENED
|
Available to everyone |
OPPORTUNITY
|
Sum |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
ID of the item in the data source |
PROBABILITY
|
Probability |
REQUISITE_ID
|
The ID of the props |
STAGE_ID
|
Stage ID |
STAGE_SEMANTIC_ID
|
Name |
SOURCE_ID
|
The source ID. Determines the source of the transaction (callback, advertisement, email, etc.). |
SOURCE_DESCRIPTION
|
Additional information about the source. |
TAX_VALUE
|
The tax rate |
CATEGORY_ID
|
The Funnel ID |
TYPE_ID
|
Type of transaction |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
PHONE
|
Contact's phone number |
EMAIL
|
Email address |
HONORIFIC
|
Type of treatment |
NAME
|
Name |
LAST_NAME
|
Surname |
TITLE
|
The name of the lead |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
ID
|
Transaction ID |
Answer fields
| Id | Name |
|---|---|
ADDITIONAL_INFO
|
Additional information |
ASSIGNED_BY_ID
|
Associated with the user by ID |
BANK_DETAIL_ID
|
Bank account ID |
BEGINDATE
|
Start date |
CLOSED
|
Completed |
CLOSEDATE
|
Completion date |
COMMENTS
|
Comments |
COMPANY_ID
|
ID of the linked company |
CONTACT_IDS
|
ID of the linked contact |
CURRENCY_ID
|
The identifier of the transaction currency |
IS_NEW
|
Flag of a new transaction (i.e. a transaction in the first stage) |
IS_RECURRING
|
The flag of the regular deal template (if it is Y, then it is not a deal, but a template) |
IS_RETURN_CUSTOMER
|
A sign of a repeated lead |
OPENED
|
Available to everyone |
OPPORTUNITY
|
Sum |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
ID of the item in the data source |
PROBABILITY
|
Probability |
REQUISITE_ID
|
The ID of the props |
STAGE_ID
|
Stage ID |
CATEGORY_ID
|
Funnel (Direction) |
STAGE_SEMANTIC_ID
|
Name |
SOURCE_ID
|
The source ID. Determines the source of the transaction (callback, advertisement, email, etc.). |
SOURCE_DESCRIPTION
|
Additional information about the source. |
TAX_VALUE
|
The tax rate |
TITLE
|
Name |
TYPE_ID
|
Type of transaction |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
Request fields
| Id | Name |
|---|---|
ID
|
Case ID |
Answer fields
| Id | Name |
|---|---|
ID
|
ID |
OWNER_ID
|
OWNER_ID |
OWNER_TYPE_ID
|
OWNER_TYPE_ID |
TYPE_ID
|
TYPE_ID |
PROVIDER_ID
|
PROVIDER_ID |
PROVIDER_TYPE_ID
|
PROVIDER_TYPE_ID |
PROVIDER_GROUP_ID
|
PROVIDER_GROUP_ID |
ASSOCIATED_ENTITY_ID
|
ASSOCIATED_ENTITY_ID |
SUBJECT
|
SUBJECT |
CREATED
|
CREATED |
LAST_UPDATED
|
LAST_UPDATED |
START_TIME
|
START_TIME |
END_TIME
|
END_TIME |
DEADLINE
|
DEADLINE |
COMPLETED
|
COMPLETED |
STATUS
|
STATUS |
RESPONSIBLE_ID
|
RESPONSIBLE_ID |
PRIORITY
|
PRIORITY |
NOTIFY_TYPE
|
NOTIFY_TYPE |
NOTIFY_VALUE
|
NOTIFY_VALUE |
DESCRIPTION
|
DESCRIPTION |
DESCRIPTION_TYPE
|
DESCRIPTION_TYPE |
DIRECTION
|
DIRECTION |
LOCATION
|
LOCATION |
ORIGINATOR_ID
|
ORIGINATOR_ID |
ORIGIN_ID
|
ORIGIN_ID |
AUTHOR_ID
|
AUTHOR_ID |
EDITOR_ID
|
EDITOR_ID |
PROVIDER_DATA
|
PROVIDER_DATA |
RESULT_MARK
|
RESULT_MARK |
RESULT_VALUE
|
RESULT_VALUE |
RESULT_SUM
|
RESULT_SUM |
RESULT_CURRENCY_ID
|
RESULT_CURRENCY_ID |
RESULT_STATUS
|
RESULT_STATUS |
RESULT_STREAM
|
RESULT_STREAM |
RESULT_SOURCE_ID
|
RESULT_SOURCE_ID |
AUTOCOMPLETE_RULE
|
AUTOCOMPLETE_RULE |
Request fields
| Id | Name |
|---|---|
entityTypeId
|
ID of the entity type |
title
|
Element Name |
assignedById
|
ID of the responsible person |
categoryId
|
ID of the funnel of the smart process element |
stageId
|
String ID of the element stage |
sourceId
|
String ID of the source |
sourceDescription
|
Additional information about the source |
opportunity
|
Sum |
parentId1
|
ID of the linked lead |
parentId2
|
ID of the related transaction |
customField1.name
|
User field code 1 |
customField1.value
|
The value of the user field is 1 |
customField2.name
|
User field code 2 |
customField2.value
|
The value of the user field is 2 |
customField3.name
|
User field code 3 |
customField3.value
|
The value of the user field is 3 |
customField4.name
|
User field code 4 |
customField4.value
|
The value of the user field is 4 |
customField5.name
|
User field code 5 |
customField5.value
|
The value of the user field is 5 |
Answer fields
| Id | Name |
|---|---|
id
|
Entity ID |
Request fields
| Id | Name |
|---|---|
PARENT_ID
|
ID of the parent task |
TITLE
|
Name |
DESCRIPTION
|
Description |
MARK
|
Evaluation |
PRIORITY
|
Priority (High, Low, Medium) |
STATUS
|
Status (Pending, In Progress, Awaiting Control, Completed, Postponed) |
MULTITASK
|
Multiple task |
REPLICATE
|
A repeatable task |
GROUP_ID
|
Project |
STAGE_ID
|
Stage |
CREATED_BY
|
The director |
RESPONSIBLE_ID
|
Executor |
DATE_START
|
Start date |
DEADLINE
|
Deadline |
START_DATE_PLAN
|
Planned start |
END_DATE_PLAN
|
Planned completion |
Answer fields
| Id | Name |
|---|---|
id
|
Task ID |
Request fields
| Id | Name |
|---|---|
TITLE
|
Contact Name |
ADDRESS
|
Contact address |
ADDRESS_2
|
The second page of the address |
ADDRESS_CITY
|
City |
ADDRESS_COUNTRY
|
A country |
ADDRESS_COUNTRY_CODE
|
Country code |
ADDRESS_POSTAL_CODE
|
Postal code |
ADDRESS_PROVINCE
|
Area |
ADDRESS_REGION
|
District |
ASSIGNED_BY_ID
|
Associated with the user by ID |
BIRTHDATE
|
Date of birth |
COMMENTS
|
Comments |
COMPANY_IDS
|
Linking a lead to a company |
EMAIL
|
Email address |
EXPORT
|
Whether the contact is involved in the export. If N, then it is impossible to unload it. |
FACE_ID
|
Linking to faces from the faceid module |
HONORIFIC
|
Type of treatment |
IM
|
Messengers |
NAME
|
Name |
LAST_NAME
|
Surname |
OPENED
|
Available to everyone |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
Date of birth |
ORIGIN_VERSION
|
The original version |
PHONE
|
Contact's phone number |
POST
|
Post |
SECOND_NAME
|
Middle name |
SOURCE_DESCRIPTION
|
Description of the source |
SOURCE_ID
|
Source ID |
STATUS_DESCRIPTION
|
STATUS_DESCRIPTION |
TYPE_ID
|
Type identifier |
STATUS_ID
|
STATUS_ID |
STATUS_SEMANTIC_ID
|
STATUS_SEMANTIC_ID |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
WEB
|
The URL of the lead resources |
Answer fields
| Id | Name |
|---|---|
id
|
Contact ID |
Request fields
| Id | Name |
|---|---|
ADDRESS
|
Contact address |
ADDRESS_2
|
The second page of the address |
ADDRESS_CITY
|
City |
ADDRESS_COUNTRY
|
A country |
ADDRESS_COUNTRY_CODE
|
Country code |
ADDRESS_POSTAL_CODE
|
Postal code |
ADDRESS_PROVINCE
|
Area |
ADDRESS_REGION
|
District |
ASSIGNED_BY_ID
|
Associated with the user by ID |
BANKING_DETAILS
|
Bank requisites |
COMMENTS
|
Comments |
COMPANY_TYPE
|
Type of company |
CURRENCY_ID
|
Currency |
PHONE
|
Telephone |
EMAIL
|
E-mail address |
IM
|
Messengers |
INDUSTRY
|
Scope of activity |
IS_MY_COMPANY
|
Am I the owner of the company |
LOGO
|
Logo |
OPENED
|
Available to all users |
REVENUE
|
Annual revenue |
TITLE
|
The name of the lead |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_MEDIUM
|
Type of traffic |
UTM_SOURCE
|
The advertising system |
UTM_TERM
|
Campaign Search Condition |
WEB
|
The URL of the lead resources |
Answer fields
| Id | Name |
|---|---|
id
|
Company ID |
Request fields
| Id | Name |
|---|---|
EMAIL
|
|
PHONE
|
Telephone |
STATUS_ID
|
Status |
Answer fields
| Id | Name |
|---|---|
id
|
Lead ID |
Request fields
| Id | Name |
|---|---|
EMAIL
|
|
PHONE
|
Telephone |
STAGE_ID
|
Stage ID |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
ID
|
Transaction ID |
TITLE
|
Name |
STAGE_ID
|
Stage ID |
OPPORTUNITY
|
Sum |
TAX_VALUE
|
The tax rate |
COMMENTS
|
Comments |
SOURCE_ID
|
The source ID. Determines the source of the transaction (callback, advertisement, email, etc.). |
SOURCE_DESCRIPTION
|
Additional information about the source. |
UTM_SOURCE
|
The advertising system |
UTM_MEDIUM
|
Type of traffic |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_TERM
|
Campaign Search Condition |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
ID
|
Lead ID |
TITLE
|
The name of the lead |
CONTACT_ID
|
Linking a lead to a contact |
SOURCE_ID
|
Source ID |
SOURCE_DESCRIPTION
|
Description of the source |
STATUS_ID
|
The original version |
STATUS_DESCRIPTION
|
The original version |
COMMENTS
|
Comments |
CURRENCY_ID
|
Currency identifier |
OPPORTUNITY
|
Estimated amount |
UTM_SOURCE
|
The advertising system |
UTM_MEDIUM
|
Type of traffic |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_TERM
|
Campaign Search Condition |
Answer fields
| Id | Name |
|---|---|
id
|
Lead ID |
Request fields
| Id | Name |
|---|---|
ID
|
Contact ID |
Answer fields
| Id | Name |
|---|---|
POST
|
Post |
COMMENTS
|
Comments |
HONORIFIC
|
Type of treatment |
NAME
|
Name |
SECOND_NAME
|
Middle name |
LAST_NAME
|
Surname |
PHOTO
|
PHOTO |
LEAD_ID
|
ID of the linked lead |
TYPE_ID
|
Type identifier |
SOURCE_ID
|
Source ID |
SOURCE_DESCRIPTION
|
Description of the source |
COMPANY_ID
|
ID of the linked company |
BIRTHDATE
|
Date of birth |
EXPORT
|
Whether the contact is involved in the export. If N, then it is impossible to unload it. |
HAS_PHONE
|
The flag of the contact's phone number |
HAS_EMAIL
|
The flag of the contact's email address |
HAS_IMOL
|
The flag for the presence of an im at the contact |
DATE_CREATE
|
The date the contact was created |
DATE_MODIFY
|
Date of contact modification |
ASSIGNED_BY_ID
|
Associated with the user by ID |
CREATED_BY_ID
|
ID of the user who created the contact |
MODIFY_BY_ID
|
The ID of the user who changed the contact |
OPENED
|
Available to everyone |
ORIGINATOR_ID
|
ID of the data source |
ORIGIN_ID
|
Date of birth |
ORIGIN_VERSION
|
The original version |
FACE_ID
|
Linking to faces from the faceid module |
ADDRESS
|
Contact address |
ADDRESS_2
|
The second page of the address |
ADDRESS_CITY
|
City |
ADDRESS_POSTAL_CODE
|
Postal code |
ADDRESS_REGION
|
District |
ADDRESS_PROVINCE
|
Area |
ADDRESS_COUNTRY
|
A country |
ADDRESS_LOC_ADDR_ID
|
ADDRESS_LOC_ADDR_ID |
UTM_SOURCE
|
The advertising system |
UTM_MEDIUM
|
Type of traffic |
UTM_CAMPAIGN
|
The designation of the advertising campaign |
UTM_CONTENT
|
Campaign content |
UTM_TERM
|
Campaign Search Condition |
PHONE.ID
|
Phone ID |
PHONE.VALUE_TYPE
|
Phone value type |
PHONE.TYPE_ID
|
Phone type |
PHONE.VALUE
|
Telephone |
EMAIL.ID
|
ID email |
EMAIL.VALUE_TYPE
|
Email value type |
EMAIL.VALUE
|
|
EMAIL.TYPE_ID
|
Email type |
UF_CRM_TELEGRAMUSERNAME_WZ
|
UF_CRM_TELEGRAMUSERNAME_WZ |
UF_CRM_TELEGRAMID_WZ
|
UF_CRM_TELEGRAMID_WZ |
Request fields
| Id | Name |
|---|---|
NAME
|
Product Name |
PRICE
|
Price |
CODE
|
Article number |
CURRENCY_ID
|
Currency identifier |
SORT
|
Sorting |
Answer fields
| Id | Name |
|---|---|
id
|
Product ID |
Request fields
| Id | Name |
|---|---|
ID
|
Product ID |
Answer fields
| Id | Name |
|---|---|
NAME
|
Product Name |
PRICE
|
Price |
CODE
|
Article number |
CURRENCY_ID
|
Currency identifier |
SORT
|
Sorting |
Request fields
| Id | Name |
|---|---|
DEAL_ID
|
Transaction ID |
PRODUCT_ID
|
Product ID |
PRICE
|
Sale price |
QUANTITY
|
Quantity |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
DEAL_ID
|
Transaction ID |
wbBarcodesData
|
Array with Wildberries products |
subject_field_id
|
Field ID for the product category (subject) |
brand_field_id
|
ID of the field for the product brand (brand) |
name_field_id
|
ID of the field for the product name (name) |
article_field_id
|
ID of the field for the article of the product (article) |
barcode_field_id
|
The ID of the field for the barcode of the product (barcode) |
size_field_id
|
ID of the field for the product size (size) |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
DEAL_ID
|
Transaction ID |
mc_product_data
|
The array with the goods is My warehouse |
subject_field_id
|
Field ID for the product category (subject) |
brand_field_id
|
ID of the field for the product brand (brand) |
name_field_id
|
ID of the field for the product name (name) |
article_field_id
|
ID of the field for the article of the product (article) |
barcode_field_id
|
The ID of the field for the barcode of the product (barcode) |
size_field_id
|
ID of the field for the product size (size) |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
DEAL_ID
|
Transaction ID |
article_field_id
|
Product Code field |
items
|
Array of items from the Avito order |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
DEAL_ID
|
Transaction ID |
FIELD_CODE
|
Field code |
FILE_NAME
|
File Name |
FILE_CONTENT
|
The contents of the file in base64 format |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Integration setup plan Calltouch with Bitrix24
| 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.
Check out other ApiMonster features
Popular automation tasks that we know how to solve
-
Dynamic call tracking based on your phone numbers and telephony -
End-to-end analytics based on yandex.metrica with free data analyst consultation -
Anti-sticking protection. Search for bots and target audience in paid traffic. -
Automating the processing of applications from Vkontakte lead forms -
Automating the processing of applications from Facebook lead forms
They trust us.
Or go through the full well on ApiMonster.
Customer reviews
The service specialists really understand the need and try to implement it. Because the available tools were not enough, they even made improvements for me - very cool!
Despite my misunderstanding of the connection process, the team helped me figure it out and the integration was set up successfully. Thanks!
Integration was set up quickly and clearly. Everything works like clockwork.
Excellent, the integration of SDEC with Ozone was set up quickly enough.
We quickly set up synchronization between Ozone and SDEC. Operational support.
It was necessary to set up the integration of cyanogen with AMO, the guys coped with the task perfectly! And most importantly, clearly and quickly! Now the leads will not pass by)
There are quite large free (regular) features. It is intuitive how to work and configure data exchange. Additionally, I would like to mention the loyal support service, which even in demo mode provides all possible assistance with tips.
I made the integration of OZONE-SDEK to automatically create shipments according to the RFBS work scheme. Now I save about 4 hours of time, instead of manually creating invoices. Everything works. Thank you very much!
We contacted you promptly and promptly to set up the integration. High-quality service.
The specialists of the Apimonstr company promptly configured all the necessary parameters. The interaction was carried out via WhatsApp chat. The whole process took one day after the bill was paid. So far, as a beginner, everything is clear and accessible to me. The tincture is completed, the system works smoothly, I hope for long-term and fruitful cooperation. Thank you for your work.
Prompt solution of assigned tasks. They will prompt and help you with all your questions. There are also detailed instructions for typical tasks. There are video instructions.
1) Fast connection 2) Intuitive interface 3) Reasonable price of services 4) Active support service
Ready connectors and tools
If the desired service is not in the list, then the universal connector "Incoming webhooks" can be used to receive webhooks and further create bundles, and the connector %2 can be used to send outgoing get/post requests%
Connectors
Tools
Widgets for the site
Didn't find the right service?
If the service has an API and webhooks, then it can be connected via universal connectors
Pricing
We give you 30 days for a free test, all the functionality is available.
Tariff plans
There is no discount
Discount 5%
Discount 10%
Discount 25%
Free
$0 / month.
-
200 transactions / month.
Approximately67of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
2 000 webhooks / month.
-
1 days is the storage period for the history of webhooks
-
Before 10 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
-
Ozon Parsing period/Wildberries/Kaspi: 0 days.
Tariff 1
$14 / month.
-
1 100 transactions / month.
Approximately367of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
10 000 webhooks / month.
-
1 days is the storage period for the history of webhooks
-
Before 30 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Tariff 2
$39 / month.
-
5 000 transactions / month.
Approximately1667of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
50 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 50 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
-
Ozon Parsing period/Wildberries/Kaspi: 14 days.
Tariff 3
$69 / month.
-
10 000 transactions / month.
Approximately3333of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
100 000 webhooks / month.
-
4 days is the storage period for the history of webhooks
-
Before 70 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
-
Ozon Parsing period/Wildberries/Kaspi: 21 days.
Calculate the benefits of using ApiMonster
How much does an hour cost-yours, the employee's, or the programmer's?
How many hours per month do you spend on a task?
How many orders/requests per month?
| Without Apimonster | With Apimonster | A comment | |
|---|---|---|---|
| The cost of the service | |||
| Salary savings / month | |||
| Saving time / month. | |||
| Money benefit / month. | |||
| Money benefit / year. |
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Tariff 4
$99 / month.
-
15 000 transactions / month.
Approximately5000of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
150 000 webhooks / month.
-
5 days is the storage period for the history of webhooks
-
Before 100 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 30 days.
Tariff 5
$159 / month.
-
25 000 transactions / month.
Approximately8333of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
250 000 webhooks / month.
-
7 days is the storage period for the history of webhooks
-
Before 150 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 6
$299 / month.
-
50 000 transactions / month.
Approximately16667of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
500 000 webhooks / month.
-
14 days is the storage period for the history of webhooks
-
Before 200 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 7
$399 / month.
-
100 000 transactions / month.
Approximately33333of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
1 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Calculate the benefits of using ApiMonster
How much does an hour cost-yours, the employee's, or the programmer's?
How many hours per month do you spend on a task?
How many orders/requests per month?
| Without Apimonster | With Apimonster | A comment | |
|---|---|---|---|
| The cost of the service | |||
| Salary savings / month | |||
| Saving time / month. | |||
| Money benefit / month. | |||
| Money benefit / year. |
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Tariff 8
$499 / month.
-
150 000 transactions / month.
Approximately50000of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
1 500 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 9
$599 / month.
-
200 000 transactions / month.
Approximately66667of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
2 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Tariff 10
$699 / month.
-
300 000 transactions / month.
Approximately100000of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
3 000 000 webhooks / month.
-
30 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Calculate the benefits of using ApiMonster
How much does an hour cost-yours, the employee's, or the programmer's?
How many hours per month do you spend on a task?
How many orders/requests per month?
| Without Apimonster | With Apimonster | A comment | |
|---|---|---|---|
| The cost of the service | |||
| Salary savings / month | |||
| Saving time / month. | |||
| Money benefit / month. | |||
| Money benefit / year. |
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Are there a lot of customers and it's difficult to make sure that everything is paid and within the tariff limits? Connect customer accounts to your account and pay for them with one check. Everything will look free to customers..
Agency 1
$99 / month.
-
10 000 transactions / month.
Approximately3333of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
100 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 100 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Agency 2
$149 / month.
-
20 000 transactions / month.
Approximately6667of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
200 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 100 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Agency 3
$199 / month.
-
30 000 transactions / month.
Approximately10000of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
300 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 100 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Agency 4
$249 / month.
-
40 000 transactions / month.
Approximately13333of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
400 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 100 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Calculate the benefits of using ApiMonster
How much does an hour cost-yours, the employee's, or the programmer's?
How many hours per month do you spend on a task?
How many orders/requests per month?
| Without Apimonster | With Apimonster | A comment | |
|---|---|---|---|
| The cost of the service | |||
| Salary savings / month | |||
| Saving time / month. | |||
| Money benefit / month. | |||
| Money benefit / year. |
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
With these tariffs, you can make ApiMonster free for your customers - you will pay for them..
This can be beneficial to increase the value of your product or service in the eyes of customers..
Whitelable 1
$600 / month.
-
75 000 transactions / month.
Approximately25000of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
750 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Whitelable 2
$1,200 / month.
-
150 000 transactions / month.
Approximately50000of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
1 500 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 14 days.
Whitelable 3
$2,400 / month.
-
300 000 transactions / month.
Approximately100000of orders/requests/deals/leads/messages per month, depends on the complexity of the bundles.
-
3 000 000 webhooks / month.
-
2 days is the storage period for the history of webhooks
-
Before 250 incoming webhuks / sec.
-
Unlimited the number of connections and accounts per service
-
The ability to automatically change the tariff if the limits are reached
-
Support via tickets/email
-
Constant support in chat
-
Free Settings
turnkey -
-
Ozon Parsing period/Wildberries/Kaspi: 21 days.
Calculate the benefits of using ApiMonster
How much does an hour cost-yours, the employee's, or the programmer's?
How many hours per month do you spend on a task?
How many orders/requests per month?
| Without Apimonster | With Apimonster | A comment | |
|---|---|---|---|
| The cost of the service | |||
| Salary savings / month | |||
| Saving time / month. | |||
| Money benefit / month. | |||
| Money benefit / year. |
FAQ
Why is it profitable to pay for ApiMonster?
An alternative to ApiMonster is to work directly with programmers whose salaries start from 150,000 rubles/month. You will spend significantly more money and time to solve a problem that has already been solved in ApiMonster. Also, working through ApiMonster, you get maximum stability in solving your problem - ApiMonster works offline 24/7, will not disappear, will not get sick.
I'm not sure if the service is suitable for me, does it make sense to test?
The service performs thousands of different actions every day. If your task can be solved through the service, we guarantee that everything will work. If you find it difficult to set up yourself, there is a turnkey setup.
What is a webhook?
Any http request included in ApiMonster get/post. For example, a notification from amoCRM about the creation of a new deal.
What is a transaction?
This is any outgoing webhook (api request): send a conversion, create/find a deal/contact/task, and so on.
How many transactions do you need?
Multiply the number of applications per month by 3-4. For example, if applications are 100, then transactions will be about 300-400 & mdash; Create transactions, send conversions, notifications. For personal calculation of the tariff, use calculator.
How many incoming webhooks do I need per month?
Usually 2-5 times the number of transactions. This restriction was introduced to reduce the load from projects with an abnormal number of webhooks that create unnecessary load. If you don't send 10 webhooks per second, then the limit is probably not relevant for you.
What is the retention period of the webhook history?
The webhook history is needed in case you find errors in the bundle and want to see what came in the webhook for debugging. The content of webhooks can require a lot of storage resources, so a restriction has been introduced. This parameter does not affect the work of the bundles.
1-3 days are enough to set up the bundles.
How many incoming webhuks do you need per second?
Usually incoming webhuk is the creation or update of the application. This event rarely occurs more often than 1 time per second, so there is more than enough limit of 5-30 webhuk per second.
Check out the possibilities of integrating Calltouch with other services
Click on the service to see how it works in conjunction with Calltouch.
Check out the possibilities of integrating Bitrix24 with other services
Click on the service to see how it works in conjunction with Bitrix24.