API integration services

API integrations that keep working when things go wrong

Connecting two systems is easy on a good day. The real work is in the bad days: expired tokens, rate limits, duplicate webhooks and an API that changes without warning. We've built and maintain integrations with Stripe, Moneybird, Instagram, YouTube, X, TikTok, Etsy, Printful, Gmail, OpenAI and more, all running in our own products.

  • OAuth, API keys and webhooks handled securely
  • Retries, idempotency and duplicate detection built in
  • Monitoring that raises the alarm before customers notice

Anatomy of a reliable integration

  1. Authenticate

    OAuth with tokens refreshed before they expire, or API keys kept in encrypted credentials.

    • OAuth 2.0
    • PKCE
    • API keys
  2. Sync

    Background jobs pull and push data on a schedule that fits each API's rate limits.

  3. Receive webhooks

    Signatures verified and events de-duplicated, so an event that arrives twice is processed once.

  4. Recover

    Retries with back-off, row locks against race conditions and a clear error when a person needs to step in.

  5. Monitor

    Error tracking and alerts when success rates drop, so problems surface before customers notice.

The pattern behind every integration we run.
What we can build

What we connect

The integrations we've built most, and can build for your systems.

Payments and billing

Stripe Checkout, Billing, Connect and Tax, with webhooks that keep subscriptions, invoices, refunds and disputes in sync.

Bookkeeping

Stripe invoices, payouts, fees and refunds synced to Moneybird, mapped to the right ledger accounts and tax rates.

Social networks

Publishing, comments and statistics through the official Instagram, YouTube, X and TikTok APIs, including the app reviews.

Marketplaces and suppliers

Listings, orders and tracking with Etsy, and print-on-demand orders routed to Printful, built so other marketplaces can follow the same pattern.

Google services

Sending and inbox sync through the Gmail API, address autocomplete with Google Places, Search Console data and server-side Google Ads conversions.

AI providers and public data

OpenAI, Fal, Replicate and ElevenLabs behind one interface, and address data enriched from Dutch public registries such as the BAG and the Kadaster.

Proof, not promises

Integrations we run in production

Across Postcrest, Twelve Lumens and Salestreak we run integrations with payment providers, bookkeeping, social networks, marketplaces, Google services, Dutch public registries and a long list of AI providers. They sync orders, publish posts, refresh tokens and process webhooks around the clock.

Every one of them has failed at some point. That's exactly why they're built the way they are.

  • Stripe checkouts protected with idempotency keys, webhook events de-duplicated by event ID
  • OAuth tokens refreshed before they expire, under a row lock so two jobs never refresh at once
  • Webhooks from AI providers verified with ED25519 signatures
  • A Stripe to Moneybird sync with a log of every push
  • An alarm in Sentry when the share of completed connections drops

Services we've integrated

  1. Payments and bookkeeping

    • Stripe Billing
    • Stripe Connect
    • Stripe Tax
    • Moneybird
  2. Social networks

    • Instagram
    • YouTube
    • X
    • TikTok
  3. Commerce

    • Etsy
    • Printful
  4. Google

    • Gmail API
    • Places
    • Search Console
    • Ads Data Manager
  5. AI providers

    • OpenAI
    • Google Gemini
    • ElevenLabs
    • Fal
    • Replicate
    • Runway
  6. Data and email

    • BAG
    • Kadaster
    • MillionVerifier
    • Resend
    • PostHog
Integrations running in our own products.
external APIs in production
20+
social network APIs integrated
4
between marketplace order syncs
10 min
between inbox syncs
5 min
Who it's for

Who we connect systems for

SMEs with tools that don't talk

Your webshop, bookkeeping, CRM and email each hold part of the truth. We connect them so data is entered once.

SaaS companies

The integrations your customers ask for, built as a dependable part of your product rather than a fragile add-on.

E-commerce businesses

Orders, stock, invoices and shipping flowing between your shop, marketplaces, suppliers and bookkeeping.

Teams with brittle connections

Scripts or no-code flows that break without anyone noticing. We replace them with integrations that retry, log and alert.

How it works

How we build an integration

We plan for the failure cases first, because that's where integrations cost money.

  1. 1

    Map the data flows

    Which system owns which data, what triggers a sync and what should happen when two systems disagree.

  2. 2

    Check the APIs

    Limits, permissions, webhooks and review processes of every API involved, before we commit to an approach.

  3. 3

    Build the connection

    Authentication, data mapping, background syncing and webhooks, with idempotency from the start.

  4. 4

    Test the failure cases

    Expired tokens, timeouts, duplicate events and partial failures, tested on purpose.

  5. 5

    Monitor in production

    Logs, error tracking and alerts on success rates, so nothing fails silently.

  6. 6

    Keep it current

    APIs get new versions and retire old ones. We keep integrations up to date when providers change.

Tooling we use

Integrations run as background jobs next to your application, with the same logging, monitoring and tests as the rest of the code.

  • REST APIs
  • Webhooks
  • OAuth 2.0
  • Ruby on Rails
  • Solid Queue
  • PostgreSQL
  • Stripe
  • Moneybird
  • Gmail API
  • Sentry
Cost & timeline

What does an API integration cost?

One integration between two well-documented APIs is a small project. These factors make it bigger:

Number of systems
Every extra system adds authentication, data mapping and its own ways to fail.
Direction and volume
Occasional one-way syncs are simpler than real-time two-way syncs at high volume.
Quality of the APIs
Well-documented APIs with webhooks are quick. Thin documentation, strict rate limits or no API at all take more work.
Platform approvals
Some platforms, such as Meta, TikTok and Google, review your app before it can go live.
Data clean-up
Duplicates and inconsistent data in existing systems often need sorting out first.
FAQ

Questions about API integrations

How much does an API integration cost?

It depends on the number of systems, whether data flows one way or both ways, the volume and the quality of the APIs involved. After a free intro call you get a written scope and estimate.

How long does it take to build an API integration?

That depends on the systems and the APIs involved. We plan the work in phases and start platform reviews by Meta, TikTok or Google early, because they add waiting time. The estimate after the intro call includes a timeline.

Can you connect our webshop to our bookkeeping software?

Usually, yes. We built a Stripe to Moneybird sync for our own products, and connect other webshops and accounting packages through their APIs.

What if a system has no API?

We look for alternatives such as scheduled exports and imports, email parsing or a partner programme, and tell you honestly how robust each option is.

Why not just use Zapier or Make?

For simple, low-volume flows they're great. Once an integration is business-critical, high-volume or needs complex logic, a built integration with retries, logging and tests is more reliable, and often cheaper over time.

Who maintains the integration when an API changes?

We can. APIs get new versions and deprecate old endpoints, and we keep integrations up to date. Or we document everything so your own team can take over.

Do you handle platform app reviews?

Yes. Integrations with Meta, Google, X and TikTok often need an approved developer app. We prepare and submit those reviews as part of the project.

Systems that should talk to each other?

Tell us which tools you use and where data gets stuck. You'll get an honest view on what can be connected and how robust it will be.

martin@balk.dev

Typically a reply within one business day.

Useful to mention

  • What you want to build, in a few sentences
  • Who is going to use it
  • Any deadline or launch date
  • Tools and systems it should connect to