Specialist service · API integration services

API development & integrations

Common integrations include TallyPrime, Zoho, SAP Business One, GST e-invoicing and e-way bill systems through GSPs, Razorpay, Cashfree and PayU, Shiprocket and Delhivery, and the WhatsApp Business Platform.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

When orders are retyped from Shopify into Tally, or lab results are copied into billing by hand, the problem is not your staff but a missing connection. Red Balloon's API integration services link the systems Indian businesses run on: accounting, ERP, CRM, payment gateways, logistics platforms, government portals and messaging. We design integrations that reconcile, retry and alert, so a failed sync is caught the same day instead of at month-end. For partners who need to connect to you, we build documented, versioned APIs and webhooks. Integrations run on infrastructure you own, with credentials stored securely and access logged. Many projects start with one painful handoff and grow from there.

What drives the cost of an integration project

The number of systems matters, but the quality of their APIs matters more. A modern payment gateway with clear documentation, a sandbox and signed webhooks is quick to connect. An accounting package on a local machine, an ERP with a partial API, or a vendor who only exchanges files takes longer, because the connector has to handle what the system does not. Volume and timing add cost too: real-time sync with reconciliation is more work than a nightly batch.

Vendor cooperation is the hidden driver. Waiting weeks for sandbox credentials or an answer about rate limits can stretch a project far more than the code does. Our API integration services start with a mapping phase that surfaces all of this, so the quote reflects your actual systems rather than a generic estimate.

Custom code or an integration platform

Not every connection needs custom engineering. Tools such as Zapier, Make and n8n are good for low-volume, non-critical flows, such as posting a new lead into a Slack channel or adding a form entry to a sheet. They are quick to set up and easy for non-engineers to change. Workato and similar enterprise platforms extend this to larger, governed workflows.

Custom code earns its place when money, stock or regulated data moves through the integration, when volumes are high, or when you need idempotency, careful retries and daily reconciliation. Many businesses end up with both, and that is fine if each is documented. We recommend per flow, and we tell you when a platform subscription will do the job more cheaply than a build.

Who looks after an integration once it is live

Integrations do not stay finished. Partners change fields, retire API versions, rotate certificates and adjust rate limits, often with short notice. Each integration therefore needs a named owner in your operations team who receives its alerts, plus an engineering contact who can act on them. We set both up before go-live and test the alert path by causing a controlled failure.

Credentials are rotated on a schedule from a secrets manager, partner changelogs are tracked, and contract tests run nightly to catch breaking changes early. All code, keys and documentation sit in your accounts. If you would rather not run this yourself, our monthly support covers monitoring, partner updates and small changes as part of a care plan.

How integrations feed automation and reporting

Once systems are connected, the data moving between them becomes useful in other ways. Our AI & Automation practice uses the same flows to send WhatsApp updates when an order ships, flag overdue payments to the right salesperson, or draft a daily summary for managers. The integration layer is the foundation; the automations are what people notice day to day.

Reporting improves too. Orders, payments and invoices that reconcile automatically can feed a dashboard the finance team trusts. For our Performance Marketing team, CRM and sales data flowing back to Google Ads and Meta as offline conversions means campaigns are judged on revenue rather than form fills.

Where this works

Real-world situations we're built for

Illustrative · not a client
D2C apparel

Delhi apparel brand re-keys Shopify orders into Tally and Shiprocket; GST invoices go out late

What we'd do
Integration layer syncing Shopify, Shiprocket, Razorpay and Tally with retries and a daily reconciliation report
What moves
Goal: manual entry hours down, payment-order mismatches down, measured as payment-order mismatches before and after, over a fixed period
Hospitals

Gurugram hospital's lab system and billing don't talk; reports and bills mismatch

What we'd do
Integration between lab system and billing using HL7 FHIR or vendor APIs, with an audit trail
What moves
Billing leakage down, report turnaround time down
How a project runs

3 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Mapping

1–2 weeks

Systems, available APIs, auth methods, rate limits, data contracts

You get: Integration map and field mappings

We need: Sandbox admin access and vendor contacts

Build

3–8 weeks

Connectors, retries, idempotency, logging, OpenAPI docs, Postman collection runs against each sandbox in CI

You get: Integrations on staging

We need: Test data and sandbox credentials

Monitor and hand over

1–2 weeks

Alerts, dashboards, reconciliation jobs, runbook

You get: Live integrations and documentation

We need: An ops owner for alerts

A typical engagement

From first call to result

Illustrative · not a client

Noida electronics distributor using Zoho CRM, Tally Prime, Razorpay, WhatsApp via a BSP and warehouse sheets in Excel

Weeks 1–2Integration mapList systems, data owners, events and volumes; choose webhooks, polling or files per systemIntegration map and data contracts
Weeks 2–7API layer buildNode.js service with OpenAPI spec, Razorpay webhooks verified via X-Razorpay-Signature, Tally sync, Zoho CRM updates, idempotency keysIntegrations running on staging
Weeks 6–8Monitoring and reconciliationDead-letter queue, alerts, daily payment-versus-invoice reconciliation reportOps dashboard
Weeks 8–10Go-liveTwo-week parallel run, then manual steps switched off; most common gap found: refunds and partial captures missing from the field mappingLive integrations and runbook
Where it starts1,200 invoices/month, payments matched by hand, 5% of orders shipped before payment was confirmed
Where it endsOrders, payments and invoices flowing without re-keying. Weekly watch: failed sync count, reconciliation mismatches, time from payment to dispatch.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Integration success rateSuccessful calls or events ÷ total attempts, per integrationSet from baseline, then aim for near 100% after retriesLogs in Grafana, Datadog or CloudWatchDaily
Dead-letter backlogEvents that failed all retries and await actionNothing older than 24 hoursAmazon SQS, RabbitMQ or BullMQ dashboardDaily
Reconciliation mismatchesRecords differing between systems ÷ records comparedSet from baseline, then aim close to zeroReconciliation report in Looker Studio or MetabaseDaily
End-to-end latencyTime from source event to update in the target system, p95Set per integration, e.g. under 5 minutes for paymentsOpenTelemetry tracing or structured logsWeekly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Failed API callRetries with backoff and dead-letteringQueue workers (BullMQ, Amazon SQS) with exponential backoffRemoves: Data lost to temporary outages or rate limits
When: Every morningDaily reconciliationScheduled job comparing Razorpay settlements, orders and Tally invoices, posting gaps to SlackRemoves: Mismatches found only at month-end close
When: Every pull request and nightlyContract tests on partner APIsPact or schema checks against OpenAPI specs in CIRemoves: Silent breaks when a partner changes a field
Rules we work to

Standards and regulations

OpenAPI Initiative (Linux Foundation)OpenAPI Specification 3.1

Machine-readable API contracts partners can generate clients and tests from

OWASPOWASP API Security Top 10 (2023)

Covers broken object-level authorisation, authentication and resource-consumption risks to test every API against

GSTN and CBICGST e-invoicing through the Invoice Registration Portal

For businesses in scope, invoice integrations must obtain an IRN and signed QR code from the IRP

What's changing

Platform and policy updates that affect this work

We track: GSTN e-invoice advisories, Meta for Developers changelog (WhatsApp Business Platform).

GSTNTaxpayers with aggregate turnover of ₹10 crore or more must report e-invoices to the IRP within 30 days of issue

Invoice integrations need prompt IRP submission and alerts on failures

Meta (WhatsApp Business Platform)Pricing moved from per-conversation to per-message for template messages

Recalculate notification costs and trim unnecessary template sends

Before you hire anyone

Questions to ask any agency, including us

What happens when a partner API is down for hours?

Why ask

Outages are normal; losing data is not acceptable

A good answer

Queues, retries with backoff, dead-letter handling and an alert to a named owner

Where will integration credentials be stored, and who can see them?

Why ask

Leaked API keys can move money or expose data

A good answer

A secrets manager, least-privilege keys, a rotation schedule and no keys in code

What documentation will our team receive for each integration?

Why ask

Undocumented integrations become impossible to change safely

A good answer

OpenAPI specs, field mappings, sequence diagrams and a runbook for common failures

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

How do you design APIs and webhooks that partners can rely on?

We document every API in OpenAPI, version it in the URL, require idempotency keys on payment and order calls, and sign outgoing webhooks with HMAC so receivers can verify them.

  • REST suits most partner APIs; GraphQL suits your own front ends that need flexible queries.
  • Webhooks retry with exponential backoff and expose a delivery log, as Razorpay and Stripe do.
  • Breaking changes go into a new version with a published deprecation window.
  • We store every inbound webhook body before processing it, so a failed order can be replayed instead of re-entered by hand.
How do you catch integrations that fail silently?

Every integration writes to a queue with retries and a dead-letter queue, and a daily reconciliation job compares record counts and totals between systems, alerting the team when they don't match.

  • Amazon SQS or BullMQ queues absorb third-party downtime without losing orders, and circuit breakers stop calling a failing API so your app stays responsive.
  • Dashboards track success rate, latency and backlog per integration. A frequent silent failure is an integration that stops without an error, such as an expired token or a webhook that quietly stops arriving.
What will you need from our software vendors before integration starts?

Current API documentation, sandbox or test credentials, details of authentication and rate limits, and a technical contact who can answer questions within a few days. For older systems, we also ask whether an export, a database view or file exchange is supported. Delays here are the most common reason integrations slip, so we request everything in the first week of mapping.

  • Documentation and sandbox access
  • Auth and rate-limit details
  • A responsive technical contact
Should integrations run in real time or in scheduled batches?

Use real time where a delay costs money or confuses customers, such as payment confirmation, stock levels on a busy store or order status messages. Use scheduled batches where timing matters less, such as syncing invoices to accounting overnight or updating reports. API integration services in India often mix both, choosing per data flow, because batches are simpler and cheaper to run.

  • Real time for payments and stock
  • Batches for accounting and reports
  • Choose per data flow
Back to the service

Web app development →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.