Service

API and integrations

Public and internal APIs, integration with payment aggregators, SMS and email services, cloud storage and 1C. Documentation, sandbox, monitoring.

See case studies

Our integration expertise

Most of our projects in recent years have been services that connect other services. These include a processing system for bank payments via batch registers and APIs, which we’ve maintained for 7.5 years; a transaction system for API clients with product creation and code uploads; a multichannel messaging service integrated with MTS, Unisender, DashaMail, and Mailchimp; a data connector with a sandbox and public documentation; and APIs for mobile apps and electronic gift certificates.

What we build

  • Public product APIs. REST APIs with versioning, token-based authentication, rate limits, and OpenAPI/Swagger documentation that clients can use without having to call you. We have our own documentation service: docs.vpodarok.ru.
  • Payment integrations. Merchant acquiring, payment aggregators, ERIP, installment payments, and custom payment processing with reporting and reconciliation.
  • Messaging and notifications. SMS, email, push notifications, and messaging platforms, with a template builder, queues, and delivery statuses.
  • Data exchange. Integrations with 1C and business management systems, cloud storage, CRMs, marketplaces, and mapping services.
  • Mobile app backends. APIs with authentication, purchases, analytics, and remote app management through an admin panel.
  • Microservices and queues. RabbitMQ and Redis for background tasks, webhooks, retries, and idempotency to ensure no transaction is lost.

Reliability built in

Integrations don’t break on launch day—they break six months later when a partner changes its response format. That’s why we build in logging for every request, monitoring in Grafana and alerting through Loki, a sandbox for client testing, and automated contract tests. This is what separates an integration that works for years from “a script a contractor wrote.”

How we work

Integrations are often the starting point for new clients: the scope is clear, delivery takes anywhere from two weeks to a couple of months, and the results are measurable. We begin by auditing the existing system and reviewing the partner’s documentation, define the API contract, implement the integration, cover it with tests, and hand it over with monitoring in place.

Frequently asked questions

Сколько занимает интеграция с платёжной системой?

Типовая интеграция с агрегатором — 1–3 недели с тестами и обработкой ошибок. Собственный процессинг с отчётностью и сверками — от 3 месяцев.

Вы делаете документацию к API?

Да, в формате OpenAPI/Swagger с примерами запросов и песочницей. Документация обновляется вместе с кодом.

Можно ли доработать интеграцию, сделанную другим подрядчиком?

Да. Начинаем с аудита кода и логов, показываем риски и план, затем дорабатываем. Часто это дешевле, чем переписывать.

Как вы следите, что интеграция не сломалась?

Логируем запросы и ответы, ставим мониторинг и алерты, тесты на контракты. О проблемах узнаём раньше ваших клиентов.

Let’s talk

Need api and integrations? Tell us about the task

Contacts