Skip to content
⁨NDDev Dev⁩, home page
Community
Language: English
Display
Theme
Motion

API integration services

NDDev connects your systems to external services through their APIs: email and SMS, messengers, maps, analytics, sign-in with Google or Apple, file storage and language models. For example, we connected the Almaty City Library Service app to the libraries’ external records system; the app has 50,000 users instead of the planned 2,000.

Who it is for

Companies whose data lives in several services and gets pieced together by hand, and product teams that need to plug an external service into their app.

  • Services with a documented API
  • Queues, retries and a call log
  • Webhook signature checks
  • Source code and data flow description

What we connect and how we keep it connected

We write the integration as a separate service in Python and FastAPI, or inside your backend if you already have one. We use a synchronous call where the answer is needed at once. Heavy and slow exchanges go through a queue on Redis or RabbitMQ, and webhooks from external services are verified by signature and processed once.

  • email and SMS: SendGrid, Mailgun, Amazon SES, Resend, Twilio
  • messengers: Telegram, WhatsApp Business, Slack
  • sign-in with Google, Apple, GitHub and Microsoft, SAML and two-factor authentication
  • analytics: GA4, Mixpanel, Amplitude, PostHog
  • maps: Google Maps, Mapbox, 2GIS
  • S3-compatible file storage
  • work tools: Jira, Confluence, Notion, Linear
  • language models and AI pipelines on LangGraph

In the Almaty libraries system we kept to a rule we now consider right for any integration: the sync records an unknown value as a gap, and a staff member fixes it. The reader’s main path keeps working even when the external system is down.

When a service has no API, we find another route: a scheduled export, file exchange or an intermediate service. We name the option and its limits before work starts.

Four stages of an integration

Keys and secrets live in the server’s environment variables, apart from the code.

  1. Data flow

    We map which data moves between systems, in which direction and how often, and who owns each side.

  2. API check

    We read the documentation, try calls on test access and note the service’s limits and weak spots.

  3. Building the exchange

    We write the service with a queue, retries with a growing pause, a circuit breaker for when the other side fails and a log of every request.

  4. Handover

    We launch the exchange in the live environment, set up alerts in Telegram or by email and hand over the code and the data flow description.

Questions about API integration

How will we know the exchange has stopped working?

Every call is logged and failures are retried automatically. Anything still failing after the retries arrives as an alert by email or in Telegram.

The service limits the number of requests. What then?

We design around the limits: requests go through a queue at an allowed pace, and data that rarely changes is cached.

Will you build the integration into our backend?

If your backend is open to changes, we build the integration into it following your team’s rules. If it suits you better to keep it apart, we run a standalone service next to it that talks to your system through an API.

Can a language model be connected to our systems?

Yes. We connect models and AI pipelines on LangGraph to your data and services. When the task goes beyond an integration, our AI practice takes it on.

How much does API integration cost?

You can see the figure we start from in the price block. More services, more data and a two-way exchange make the work larger. We record the exact price and timeline in the specification, and writing it is already included in the project price.

from $890

Free warranty
8 days

Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.

Integrations

Name the services you need to connect

Send links to the API documentation or describe which data should go where. We will reply with an exchange scheme and a price.

We reply within 24 hours

Assistant

Loading the assistant…