Skip to main content
WassliSystems
Request a consultation
WassliSystems
Request a consultation

Integrations

Custom APIs and middleware, for when connectors run out.

When two systems have APIs but no connector, or the connector can’t handle your volume or logic, we build middleware: webhook receivers, queues, transformation and sync with proper error handling.

  • Node.js
  • Python
  • REST
  • GraphQL
  • Webhooks
  • Queues
  • Idempotency keys
  • OAuth 2.0
  • OpenAPI

01 — The problem

Integrations that fail silently.

A connector drops records when one API is slow, retries create duplicates, and nobody notices until a customer complains.

Reliable integration needs things connectors rarely give you: idempotency, ordered processing, back-off on rate limits, dead-letter queues and logs searchable by record.

02 — What we build

What the engagement delivers.

Webhook receivers

Endpoints that verify signatures, acknowledge quickly and queue work for processing.

Queue-based sync

Jobs processed with retries and exponential back-off, with failed jobs parked in a dead-letter queue for replay.

Transformation

Mapping and validation between systems, versioned and tested.

APIs for your systems

REST or GraphQL APIs over your data, documented in OpenAPI, with authentication and rate limiting.

Observability

Structured logs searchable by record ID, alerts on failure rates and a replay tool.

03 — Configuration vs custom

What is set up, and what is written.

Configuration

  • Hosting on your cloud account
  • Secrets management
  • Monitoring and alert channels

Custom development

  • Middleware services and workers
  • API design and documentation
  • Test suites against sandbox APIs
  • Replay and admin tools

04 — Typical effort

What it usually takes.

Ranges from comparable projects. You get a fixed-scope quote after a 30-minute call.

Single integration2–4 weeks
Integration hub across 3–5 systems6–12 weeks
Public API for your platform4–8 weeks

05 — What you own

Yours at handover.

  • Source code in your repository
  • Infrastructure in your cloud account
  • OpenAPI documentation
  • Runbooks

FAQ

Questions about custom API development.

Where is the middleware hosted?

In your cloud account (AWS, Azure, Google Cloud or Cloudflare), so you own it and can move it.

What is idempotency and why does it matter?

It means processing the same event twice has the same effect as once. Webhooks are often delivered more than once, so without it you get duplicates.

How do you handle API rate limits?

Queues control throughput, and requests back off when a system signals it is overloaded.

Can you document an API for partners?

Yes, in OpenAPI with examples, authentication guides and a sandbox.

Related

Often paired with

Next step

Start with a 30-minute call.

Tell us what you run today and where it breaks. You get a fixed-scope quote afterwards. We don’t publish rates, because the honest price depends on scope.

Enquire

Talk to us about Custom API & middleware development.

We have started the message for you. Add what you run today and we will reply within one business day.

So we can call you back the same day. Country code is filled in for you.
We reply within one business day.
Request a consultation