API integrations

What we connect

For us, an integration is a connection that works every day without human intervention: an order from the store enters the warehouse, a Stripe payment closes the invoice, a waybill is created from the order, a website enquiry becomes a deal in the CRM, and a call is recorded under the customer. We connect anything with an API or data export: couriers, payments, banks, telephony, messengers, advertising, CMS and ERP systems, and accounting software.

In the Akbari Perfume store, Econt works through the official module, Speedy through its API with offices, lockers and live pricing, while Meta receives server-side events with duplicates removed. Pelikan DTM’s WooCommerce online store communicates with the company’s ERP system. On the Hristiyanski tsentar Sofia website, the donation goes through Stripe and is recorded once, even if the notification arrives twice. Q-Parts.bg calculates shipping and creates waybills through the Econt API. LiftexPro collects subscriptions through Stripe. Elite Call Center communicates over an A1 SIP line, while the NAK and FastPool.bg websites send every enquiry to Telegram.

The 3DPrintX solution shows a store and warehouse with shared stock, while Testen Dom imports B2B requests directly from email.

How the project works

First, you describe the systems: which programs you use, which data needs to move between them and in which direction. We read both sides’ documentation and check what access, test accounts and permissions are required; then we give you an estimated price. The price depends on the number of connections and how good the documentation on the other side is, not on the volume of data.

The quote describes every connection: what moves, when, what happens in case of an error, how we test it, the exact price and the timeline. It is approved online. We build in the provider’s test environment and run the connection through real scenarios: order, payment, return and cancellation. Only then do we put it live and monitor the log of sent data during the first few weeks.

One connection takes days to two or three weeks; several connected systems take one or two months. We describe and price any change in scope before starting it.

What you get

Working connections, their code in a repository in your name, the access details and a document describing every connection: what moves, when, what happens in case of an error and where the log can be viewed. Every connection records what was sent and alerts you when something goes wrong, so an order does not disappear silently.

Post-launch support is optional (€100-€350 per month, based on our quotes). It makes sense for integrations because providers change their API versions, and a connection nobody monitors can stop working silently.

What is not included

Provider fees, such as Stripe’s fee for each payment, Econt and Speedy’s fees for shipments, and the operator’s fee for minutes, are paid to the providers. Access to your accounts and your contracts with providers remain yours; we request them, but we do not enter into them. We price a connection to a system without an API or data export separately, after we see what is possible. We do not promise compliance with the laws of another country where this must be monitored continuously; we describe exactly what the connection does today.

When integration is not the solution

When there are more than three programs you want to connect and each holds part of the truth, the connections become more expensive than one system that holds everything. That is when we say it is time for an ERP or custom business software, with connections only to the outside world: couriers, payments and the bank. Conversely, when one off-the-shelf program does the job, connecting to it is cheaper than building a new system. We tell you which of the two applies to you in the first conversation.

What a connection looks like inside

Every connection we build has three parts that are invisible but determine whether it will still work a year from now. Logging: every message sent and received is recorded with the time and response, so you can see what happened to a specific order. Retries: when the other system does not respond, the connection tries again shortly afterwards instead of losing the request. Duplicate protection: when a provider sends the same notification twice, as Stripe does, the payment is recorded once. These three things are included in the quote by default, because a connection without them works until the first problem, and then nobody knows where the order disappeared.