Connection in 5 minutes, 30 days on tests, try.
74 834 561
132 198 360
2000+
Free Turnkey setting, Instructions.
Click on the name of the event to see the available fields.
API documentation — No.
There are no events, try Change to replace the services.
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.
Id | Name |
---|---|
Inn
|
The INN of your organization or the sole proprietor for which the cashier is registered |
Type
|
The sign of calculation |
InvoiceId
|
The order number in your system |
AccountId
|
The user ID in your system |
CustomerReceipt.Items.0.Label
|
Name of the product or service |
CustomerReceipt.Items.0.Price
|
Price per unit of goods/services |
CustomerReceipt.Items.0.Quantity
|
Quantity |
CustomerReceipt.Items.0.Vat
|
The VAT rate of the service/product |
CustomerReceipt.Items.0.Amount
|
Price * Quantity including discount |
CustomerReceipt.Items.0.Method
|
Calculation method |
CustomerReceipt.Items.0.Object
|
The subject of the calculation |
CustomerReceipt.Items.0.MeasurementUnit
|
Unit of measurement |
CustomerReceipt.Items.0.Excise
|
The amount of the excise tax |
CustomerReceipt.Items.0.CountryOriginCode
|
The code of the country of origin of the goods in accordance with the All-Russian classifier of the countries of the world 3 characters, the OFD tag 1230 |
CustomerReceipt.Items.0.CustomsDeclarationNumber
|
The registration number of the customs declaration is 32 characters, the OFD tag is 1231 |
CustomerReceipt.Items.0.AgentSign
|
Agent's attribute, OFD tag 1222 |
CustomerReceipt.Items.0.AgentData.AgentOperationName
|
Name of the operation of the bank payment agent or bank payment subagent, OFD 1044 tag |
CustomerReceipt.Items.0.AgentData.PaymentAgentPhone
|
Phone number of the payment agent, OFD tag 1073 |
CustomerReceipt.Items.0.AgentData.PaymentReceiverOperatorPhone
|
Phone number of the payment acceptance operator, OFD tag 1074 |
CustomerReceipt.Items.0.AgentData.TransferOperatorPhone
|
Phone number of the transfer operator, OFD tag 1075 |
CustomerReceipt.Items.0.AgentData.TransferOperatorName
|
Name of the transfer operator, OFD 1026 tag |
CustomerReceipt.Items.0.AgentData.TransferOperatorAddress
|
Address of the transfer operator, OFD tag 1005 |
CustomerReceipt.Items.0.AgentData.TransferOperatorInn
|
TIN of the transfer operator, OFD tag 1016 |
CustomerReceipt.Items.0.PurveyorData.Name
|
Supplier's name, OFD 1225 tag |
CustomerReceipt.Items.0.PurveyorData.Inn
|
Supplier's INN, OFD tag 1226 |
CustomerReceipt.Items.0.PurveyorData.Phone
|
Supplier's phone number, OFD tag 1171 |
CustomerReceipt.Items.0.AdditionalPositionInfo
|
Additional information inside the specific position of the receipt |
CustomerReceipt.Items.0.SaleObjectData
|
Additional details of the calculation subject, OFD tag 1191 |
CustomerReceipt.Items.0.IndustryRequisiteCollection
|
Industry details of the calculation subject, OFD 1260 tag (ffd 1.2) |
CustomerReceipt.Items.0.ProductCodeData.CodeProductNomenclature
|
Product labeling data, OFD 1162 tag (HEX representation of the barcode/bar marking code in its entirety) |
CustomerReceipt.Items.0.MarkPartQuantity.Numerator
|
Fractional quantity of the marked product, OFD tag 1291 (ffd 1.2). Numerator, OFD tag 1293 |
CustomerReceipt.Items.0.MarkPartQuantity.Denominator
|
Fractional quantity of the marked product, OFD tag 1291 (ffd 1.2). Denominator, OFD tag 1294 |
CustomerReceipt.Items.0.RawMarkCode
|
Marking code, OFD 2000 tag |
CustomerReceipt.Items.0.GroupSeparator
|
GS Separator (ffd 1.2) |
CustomerReceipt.Items.0.UnitCode
|
A measure of the quantity of the calculation object, OFD 2108 tag |
CustomerReceipt.TaxationSystem
|
Tax system (optional if you have one tax system) |
CustomerReceipt.Amounts.Electronic
|
The amount of payment in electronic money |
CustomerReceipt.Amounts.AdvancePayment
|
The amount of the prepayment |
CustomerReceipt.Amounts.Credit
|
Post-payment amount |
CustomerReceipt.Amounts.Provision
|
The amount is counter-provided |
CustomerReceipt.CalculationPlace
|
Place of settlement |
CustomerReceipt.Email
|
Buyer's e-mail address for sending the receipt |
CustomerReceipt.Phone
|
The buyer's phone number in the format without brackets and hyphens for sending a link to the receipt |
CustomerReceipt.CustomerInfo
|
Buyer, name of the organization or surname, first name, patronymic (if any), series and passport number of the buyer (client), OFD tag 1227 |
CustomerReceipt.CustomerInn
|
Buyer's INN, OFD tag 1228 |
CustomerReceipt.isBso
|
true if the receipt is a strict reporting form |
CustomerReceipt.AgentSign
|
The agent's attribute, the OFD 1057 tag |
CustomerReceipt.CashierName
|
The name of the cashier, if not passed, the value specified in the cashier's settings in the LC will be used, otherwise “System. The administrator” |
CustomerReceipt.AdditionalReceiptInfos
|
Additional information common to the receipt, multi-line |
CustomerReceipt.AdditionalReceiptRequisite
|
Additional details of the receipt (tag 1192) |
CustomerReceipt.CustomerBirthday
|
Date of birth of the buyer (client), OFD tag 1243 (ffd 1.2) |
CustomerReceipt.CustomerStateCode
|
Citizenship, OFD tag 1244 (ffd 1.2) |
CustomerReceipt.CustomerDocType
|
Identification document type code, OFD tag 1245 (ffd 1.2) |
CustomerReceipt.CustomerDoc
|
Data of the identity document, OFD 1246 tag (ffd 1.2) |
CustomerReceipt.CustomerPlace
|
Buyer's (customer's) address, OFD 1254 tag (ffd 1.2) |
CustomerReceipt.UserRequisiteData.RequisiteKey
|
The name of the additional user's account, the OFD 1085 tag |
CustomerReceipt.UserRequisiteData.RequisiteValue
|
The value of the user's additional account details, OFD tag 1086 |
CustomerReceipt.OperationReceiptRequisite.OperationIdentifier
|
Operation ID, OFD tag 1271 |
CustomerReceipt.OperationReceiptRequisite.OperationDate
|
Date, time of operation, OFD tag 1273 |
CustomerReceipt.OperationReceiptRequisite.OperationData
|
Operation data, OFD tag 1272 |
CustomerReceipt.IndustryRequisiteCollection.Code
|
FOIV ID, OFD tag 1262 |
CustomerReceipt.IndustryRequisiteCollection.DocumentDate
|
Date of the foundation document, OFD tag 1263 |
CustomerReceipt.IndustryRequisiteCollection.DocumentNumber
|
The number of the foundation document, the OFD tag 1264 |
CustomerReceipt.IndustryRequisiteCollection.RequisiteValue
|
The value of the industry props, OFD tag 1265 |
Id | Name |
---|---|
Model.Id
|
Receipt ID |
Model.ErrorCode
|
Error code |
Model.ReceiptLocalUrl
|
Link to the receipt |
InnerResult
|
InnerResult |
Success
|
Operation success flag |
Message
|
Message |
Warning
|
Warning |
Id | Name |
---|---|
Inn
|
The INN of your organization or the sole proprietor for which the cashier is registered |
Type
|
The sign of calculation |
InvoiceId
|
The order number in your system |
CustomerReceipt.Items
|
Array of goods/services in the receipt (json) |
AccountId
|
The user ID in your system |
CustomerReceipt.TaxationSystem
|
Tax system (optional if you have one tax system) |
CustomerReceipt.Amounts.Electronic
|
The amount of payment in electronic money |
CustomerReceipt.Amounts.AdvancePayment
|
The amount of the prepayment |
CustomerReceipt.Amounts.Credit
|
Post-payment amount |
CustomerReceipt.Amounts.Provision
|
The amount is counter-provided |
CustomerReceipt.CalculationPlace
|
Place of settlement |
CustomerReceipt.Email
|
Buyer's e-mail address for sending the receipt |
CustomerReceipt.Phone
|
The buyer's phone number in the format without brackets and hyphens for sending a link to the receipt |
CustomerReceipt.CustomerInfo
|
Buyer, name of the organization or surname, first name, patronymic (if any), series and passport number of the buyer (client), OFD tag 1227 |
CustomerReceipt.CustomerInn
|
Buyer's INN, OFD tag 1228 |
CustomerReceipt.isBso
|
true if the receipt is a strict reporting form |
CustomerReceipt.AgentSign
|
The agent's attribute, the OFD 1057 tag |
CustomerReceipt.CashierName
|
The name of the cashier, if not passed, the value specified in the cashier's settings in the LC will be used, otherwise “System. The administrator” |
CustomerReceipt.AdditionalReceiptInfos
|
Additional information common to the receipt, multi-line |
CustomerReceipt.AdditionalReceiptRequisite
|
Additional details of the receipt (tag 1192) |
CustomerReceipt.CustomerBirthday
|
Date of birth of the buyer (client), OFD tag 1243 (ffd 1.2) |
CustomerReceipt.CustomerStateCode
|
Citizenship, OFD tag 1244 (ffd 1.2) |
CustomerReceipt.CustomerDocType
|
Identification document type code, OFD tag 1245 (ffd 1.2) |
CustomerReceipt.CustomerDoc
|
Data of the identity document, OFD 1246 tag (ffd 1.2) |
CustomerReceipt.CustomerPlace
|
Buyer's (customer's) address, OFD 1254 tag (ffd 1.2) |
CustomerReceipt.UserRequisiteData.RequisiteKey
|
The name of the additional user's account, the OFD 1085 tag |
CustomerReceipt.UserRequisiteData.RequisiteValue
|
The value of the user's additional account details, OFD tag 1086 |
CustomerReceipt.OperationReceiptRequisite.OperationIdentifier
|
Operation ID, OFD tag 1271 |
CustomerReceipt.OperationReceiptRequisite.OperationDate
|
Date, time of operation, OFD tag 1273 |
CustomerReceipt.OperationReceiptRequisite.OperationData
|
Operation data, OFD tag 1272 |
CustomerReceipt.IndustryRequisiteCollection.Code
|
FOIV ID, OFD tag 1262 |
CustomerReceipt.IndustryRequisiteCollection.DocumentDate
|
Date of the foundation document, OFD tag 1263 |
CustomerReceipt.IndustryRequisiteCollection.DocumentNumber
|
The number of the foundation document, the OFD tag 1264 |
CustomerReceipt.IndustryRequisiteCollection.RequisiteValue
|
The value of the industry props, OFD tag 1265 |
Id | Name |
---|---|
Model.Id
|
Receipt ID |
Model.ErrorCode
|
Error code |
Model.ReceiptLocalUrl
|
Link to the receipt |
InnerResult
|
InnerResult |
Success
|
Operation success flag |
Message
|
Message |
Warning
|
Warning |
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.
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
Or go through the full well on ApiMonster.
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
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%
If the service has an API and webhooks, then it can be connected via universal connectors
We give you 30 days for a free test, all the functionality is available.
200 transactions / month.
Approximately 67
of 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.
1 100 transactions / month.
Approximately 367
of 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.
5 000 transactions / month.
Approximately 1667
of 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.
10 000 transactions / month.
Approximately 3333
of 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.
Without Apimonster | With Apimonster | A comment | |
---|---|---|---|
The cost of the service | |||
Salary savings / month | |||
Saving time / month. | |||
Money benefit / month. | |||
Money benefit / year. |
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.
15 000 transactions / month.
Approximately 5000
of 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
Ozon Parsing period/Wildberries/Kaspi: 30 days.
25 000 transactions / month.
Approximately 8333
of 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
Ozon Parsing period/Wildberries/Kaspi: 45 days.
50 000 transactions / month.
Approximately 16667
of 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
Ozon Parsing period/Wildberries/Kaspi: 45 days.
100 000 transactions / month.
Approximately 33333
of 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
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Without Apimonster | With Apimonster | A comment | |
---|---|---|---|
The cost of the service | |||
Salary savings / month | |||
Saving time / month. | |||
Money benefit / month. | |||
Money benefit / year. |
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.
150 000 transactions / month.
Approximately 50000
of 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
Ozon Parsing period/Wildberries/Kaspi: 45 days.
200 000 transactions / month.
Approximately 66667
of 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
Ozon Parsing period/Wildberries/Kaspi: 45 days.
300 000 transactions / month.
Approximately 100000
of 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
Ozon Parsing period/Wildberries/Kaspi: 45 days.
Without Apimonster | With Apimonster | A comment | |
---|---|---|---|
The cost of the service | |||
Salary savings / month | |||
Saving time / month. | |||
Money benefit / month. | |||
Money benefit / year. |
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..
10 000 transactions / month.
Approximately 3333
of 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
Ozon Parsing period/Wildberries/Kaspi: 5 days.
20 000 transactions / month.
Approximately 6667
of 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
Ozon Parsing period/Wildberries/Kaspi: 5 days.
30 000 transactions / month.
Approximately 10000
of 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
Ozon Parsing period/Wildberries/Kaspi: 5 days.
40 000 transactions / month.
Approximately 13333
of 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
Ozon Parsing period/Wildberries/Kaspi: 5 days.
Without Apimonster | With Apimonster | A comment | |
---|---|---|---|
The cost of the service | |||
Salary savings / month | |||
Saving time / month. | |||
Money benefit / month. | |||
Money benefit / year. |
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..
75 000 transactions / month.
Approximately 25000
of 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
Ozon Parsing period/Wildberries/Kaspi: 5 days.
150 000 transactions / month.
Approximately 50000
of 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
Ozon Parsing period/Wildberries/Kaspi: 14 days.
300 000 transactions / month.
Approximately 100000
of 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
Ozon Parsing period/Wildberries/Kaspi: 21 days.
Without Apimonster | With Apimonster | A comment | |
---|---|---|---|
The cost of the service | |||
Salary savings / month | |||
Saving time / month. | |||
Money benefit / month. | |||
Money benefit / year. |
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.
Click on the service to see how it works in conjunction with Suite CRM.
Click on the service to see how it works in conjunction with CloudKassir.