API Integration Services in India: Complete 2026 Guide

API integration in India costs ₹15,000 to ₹3,00,000 per connection in 2026, depending on what the connection touches. A Razorpay pay button with basic webhooks sits at the bottom of that range. A GST e-invoicing link that has to survive an audit sits near the top. Most Indian SMBs spend ₹50,000 to ₹2,00,000 on their first three or four integrations and two to eight weeks of calendar time. Ongoing monitoring adds ₹5,000 to ₹25,000 a month.

I'm Ashish Sharma, founder of Codingclave. We have worked from Lucknow since 2017 and shipped over 200 projects, a large share of them integrations: payment checkouts, WhatsApp Business API connected to CRMs, GST e-invoicing inside billing software, Shiprocket and Delhivery sync, Tally sync. This guide covers what each integration costs in October 2026, how long it takes, what the providers charge on top, and the mistakes we keep finding in inherited code.

What does API integration cost in India in 2026?

These are the ranges we quote and see other Indian agencies quote. Hourly rates on marketplaces such as IndiaMart and Upwork for Indian integration developers run ₹1,000 to ₹5,000 an hour; the fixed prices below assume mid-range rates and production quality (webhooks, retries, monitoring), not just a working demo.

Integration (APIs we integrate most)	Build cost (₹)	Build time	What the provider charges after launch
Payment gateway: Razorpay, Cashfree, PayU, PhonePe	25,000 to 75,000	1 to 3 weeks	1.95% to 2% platform fee plus 18% GST on the fee
UPI Autopay and recurring mandates	40,000 to 1,20,000	2 to 4 weeks	Gateway fee; no network MDR on mandates
WhatsApp Business API with CRM sync: Meta Cloud API, Wati, Interakt, AiSensy, Gupshup	40,000 to 1,50,000	2 to 5 weeks	Meta ₹0.8631 marketing, ₹0.115 utility per message, plus BSP fee
GST e-invoicing: ClearTax, Cygnet, Masters India, IRIS, NIC IRP direct	80,000 to 2,50,000	3 to 5 weeks	₹1 to ₹3 per invoice to the GSP
Logistics aggregator: Shiprocket	35,000 to 1,00,000	2 to 3 weeks	Shipping rates plus aggregator plan or per-shipment margin
Direct carrier: Delhivery, Blue Dart, DTDC	60,000 to 1,50,000 per carrier	3 to 4 weeks	Negotiated shipping rates
Accounting sync: TallyPrime, Zoho Books and Zoho CRM, Busy	50,000 to 2,00,000	2 to 6 weeks	Zoho API plan limits; Tally licence you already own
Multi-channel inventory: Shopify, Amazon SP-API, Flipkart Seller API, Unicommerce	1,50,000 to 5,00,000	6 to 12 weeks	Marketplace API limits; Unicommerce or Vinculum subscription if used
SMS OTP and login: MSG91, Twilio Verify, Truecaller SDK, DigiLocker	15,000 to 40,000	1 week	₹0.16 to ₹0.25 per SMS plus DLT registration
AI API: OpenAI, Claude, Gemini	40,000 to 2,00,000	2 to 6 weeks	Per-token usage billed in USD
Enterprise middleware: SAP, Salesforce, custom ERP	10,00,000 and up	3 to 9 months	Platform licences

Two things move a quote inside these ranges: how many failure modes the integration must handle (confirming a payment is cheap; reconciling partial refunds against settlements is not), and whether your data is clean. Half our hours on legacy billing systems go into fixing invoice data before the GSP will accept it. The usual build order is payments, then messaging, then logistics or compliance, then accounting sync the first time finance spends a weekend re-keying orders into Tally.

How does payment gateway integration work and what does Razorpay charge?

Razorpay still leads Indian startup checkouts because the documentation is the clearest and the dashboard does reconciliation work your developers would otherwise build. The fee picture changed in 2026, so here is what the published rate cards say as of 5 October 2026.

Gateway	Domestic cards, net banking, wallets	UPI	International cards	Setup / AMC	Source
Razorpay	2%	2% platform fee (Razorpay lists UPI as zero network MDR with its 2% platform fee applying)	Up to 3%	₹0 / ₹0	razorpay.com/pricing
Cashfree	1.95%	1.95%	2.99% Visa and Mastercard, 2.95% Amex	₹0 / ₹0	cashfree.com/payment-gateway-charges
PayU	2%	Varies by business type and volume	3% (also EMI, Amex and Diners)	₹0 / ₹0	payu.in/pricing

All three add 18% GST on the fee itself, which turns a 2% fee into 2.36% of the transaction. Above roughly ₹50 lakh a month every gateway negotiates; we have seen UPI at 0% and cards at 1.6% to 1.8% for merchants who ask. Cashfree's charges page also lists a 0% platform fee for new merchants on their first ₹20 lakh of volume until 31 March 2027, excluding Amex, Diners, corporate cards, EMI and subscriptions. Settlement timings and EMI are compared in our Razorpay vs Stripe vs PayU vs Cashfree breakdown.

The UPI fee change on 15 October 2026

NPCI notified on 15 September 2026, as The Times of India and Business Standard reported that day, that person-to-merchant UPI transactions above ₹2,000 attract a 0.4% MDR from 15 October 2026, capped at ₹300 from ₹75,000 upward. The Supreme Court declined to stay it on 28 September. Transactions of ₹2,000 or less stay at zero, small merchants collecting up to ₹1 lakh a month on a UPI QR stay at zero, railways, telecom, insurance and fuel pay a flat ₹5 above ₹2,000, and UPI Autopay mandates carry no network MDR. For your integration: reconciliation must handle a UPI fee that varies by ticket size, and any 0% UPI deal you negotiated last year will be repriced if your average order is above ₹2,000. Ask your gateway in writing how they pass this through.

What a finished Razorpay integration contains

A pay button is the first 10% of the work. Production means:

1. Order created on your server before checkout opens, so the amount cannot be edited in the browser.
2. Checkout with UPI intent pinned first for consumers; UPI collect kept for B2B or desktop flows.
3. HMAC verification of the X-Razorpay-Signature header on every webhook. Without it anyone with your webhook URL can mark an order paid.
4. Handlers for payment.captured, payment.failed, refund.processed and, for subscriptions, subscription.charged and subscription.halted.
5. Idempotency: a payment ID that is already processed must be a no-op when the webhook arrives again.
6. Partial and full refunds from your admin panel, with the refund ID stored.
7. Daily reconciliation between the settlement report and your order table, including fee, GST and now the UPI MDR line.

For recurring collections, UPI Autopay mandates can be debited without a second authentication up to ₹15,000 per transaction, and up to ₹1,00,000 for insurance premiums, mutual fund SIPs and credit card bills under the RBI e-mandate framework. If you are building fee collection, SaaS billing or EMIs, our UPI Autopay build guide covers mandate types and pre-debit notifications, and the SaaS billing guide covers proration and dunning.

How do you integrate the WhatsApp Business API in India?

The official WhatsApp Business API (not the free Business app) is the only way to send at scale, automate replies or connect WhatsApp to a CRM.

Direct Meta or a BSP

You can connect your own backend to Meta's Cloud API or go through a Business Solution Provider that hosts the connection and gives you an inbox, template manager and wallet. Direct Meta has no platform fee but you build template management, opt-in storage, webhooks and invoicing yourself. Under a lakh of messages a month, a BSP is cheaper than the engineering time.

• Under 10,000 messages a month: Wati, Interakt, AiSensy. Subscription plans from ₹999 to ₹9,999 a month with no-code builders. Our own PayPerWA charges ₹0.20 per message with no subscription and refunds failed messages.
• 10,000 to 5,00,000 a month: Gupshup self-serve at $0.001 (about ₹0.09) per message, or direct Meta if you have engineers.
• Above 5,00,000 a month: Gupshup enterprise, Infobip, Route Mobile with custom SLAs.

The provider bills are modelled at 1,000 to 2 lakh messages in our cheapest WhatsApp API provider comparison, and Gupshup's hidden fees are in the Gupshup pricing teardown.

What Meta charges in India

Meta moved from per-conversation to per-message pricing on 1 July 2025 and, per its developer pricing documentation, moved Indian accounts to rupee billing on 1 January 2026, with legacy dollar-billed accounts required to migrate by 31 December 2026.

Message category	Meta rate (India, INR, before 18% GST)	Notes
Marketing template	₹0.8631 per delivered message	Promotions, re-engagement, abandoned cart
Utility template	₹0.115 per delivered message	Order confirmations, OTP-style alerts; free if sent inside an open customer service window
Authentication template	₹0.115 per delivered message	OTPs; volume tiers reduce the rate at scale
Service (customer-initiated) reply	₹0.115 per message from 1 October 2026	Free until 30 September 2026; Meta's non-template pricing page sets it at the utility rate. Some BSPs pass through a free first 1,000 a month per number, so check yours
Free entry point	Free for 72 hours	Customer arrives from a Click-to-WhatsApp ad or Facebook Page button

For a D2C brand sending 5,000 utility messages and 2,000 marketing messages a month, Meta's bill is about ₹2,300 before GST, plus about ₹345 if support answers 3,000 customer chats now that service replies are billed. The BSP plan or per-message fee is extra.

The parts of a WhatsApp integration

1. Templates, approved by Meta in 24 to 72 hours, for every proactive message.
2. Send API wired to your events: order placed, shipped, delivered, payment due.
3. Incoming webhook for customer messages and status updates (sent, delivered, read, failed), written to your CRM.
4. Opt-in storage with timestamp and source, which the DPDP Rules will require you to show.
5. A chatbot layer only if volume justifies it, with a hard hand-off to a human.

The four CRM integration levels are in our WhatsApp CRM integration guide; verification and the green tick are in the WhatsApp Business API guide for India.

Is GST e-invoicing API integration mandatory and how does it work?

E-invoicing is mandatory for any business whose aggregate annual turnover crossed ₹5 crore in any financial year from 2017-18 onward, for B2B, B2G and export invoices, and the obligation is permanent once triggered (Tally Solutions' e-invoicing guide has the threshold history). The rules that trip up integrations:

• Businesses above ₹10 crore must report invoices, credit notes and debit notes to the Invoice Registration Portal within 30 days of the document date; the IRP rejects anything older. This has applied since 1 April 2025.
• Two-factor authentication on the e-invoice and e-way bill portals has been mandatory for all taxpayers since 1 April 2025 (GSTN advisory, reported by The Economic Times), so service accounts need a proper OTP flow.
• B2C e-invoicing is not mandatory; the dynamic QR code applies only to very large retailers.
• Penalties: ₹10,000 or the tax due, whichever is higher, under Section 122 of the CGST Act, and up to ₹25,000 under Section 125, plus the commercial penalty that your buyer cannot claim input tax credit on an invalid invoice.

The integration flow

1. Your billing software finalises an invoice and your backend validates the JSON against the NIC schema (GSTIN format, HSN or SAC codes, place of supply, tax splits).
2. You call the GSP API (ClearTax, Cygnet, Masters India, IRIS) or NIC's IRP directly and receive the IRN and signed QR code.
3. The invoice PDF prints both; the e-way bill is generated from the same payload when goods move.
4. IRN, acknowledgement number and date are stored against the invoice for the audit window.

What breaks in practice

The NIC schema is unforgiving: one wrong HSN code fails the whole submission. Credit notes must also go through the IRP, and an IRN can only be cancelled within 24 hours; after that you issue a credit note. IRP downtime happens, so the integration needs a queue that retries without creating duplicate IRNs. We deliver a production e-invoicing integration in three to five weeks for ₹80,000 to ₹2,50,000 depending on how clean the billing data is; our own billing and invoice software ships with this flow built in. GSTR reports and ITC are covered in our GST-compliant software guide.

Which logistics API should a D2C brand integrate?

A tracking sync that falls behind by a day turns into "where is my order" tickets on WhatsApp, so this integration decides how your support queue looks.

Shiprocket for the first 1,000 orders a day

Shiprocket's carrier page lists 42 courier partners, including Delhivery, Xpressbees, Ecom Express, Blue Dart, Ekart, DTDC, Amazon Shipping, Shadowfax and India Post, behind one API, with coverage of 19,000-plus pin codes. A production Shiprocket integration includes order push from your store, rate and serviceability check at checkout, AWB assignment and label PDF, tracking webhooks written back to your order table, return and RTO handling, and COD remittance reconciliation. Build cost is ₹35,000 to ₹1,00,000.

Direct carriers above that

Past roughly 1,000 orders a day, direct contracts with Delhivery or Blue Dart usually pay back within six to twelve months because the aggregator's per-shipment margin disappears. Each carrier has its own API, label format, manifest process and NDR (non-delivery report) workflow, so budget ₹60,000 to ₹1,50,000 per carrier and keep Shiprocket as the fallback for pin codes your contracted carrier does not serve.

How do you sync Tally, Zoho Books and your ERP?

Orders live in Shopify or a custom CRM, payments in Razorpay, and the accountant re-keys all of it into Tally at month end. This is the integration most businesses leave for last.

• TallyPrime has no cloud REST API. Integration uses Tally's XML interface over HTTP (Tally listens on a local port, usually 9000) or ODBC, so a small connector service must run where Tally runs. We push sales vouchers, receipts and ledger masters in and pull outstanding and stock summaries out. Expect ₹50,000 to ₹1,50,000 for two-way sync, and plan for the data path and company name changing when the accountant upgrades.
• Zoho Books and Zoho CRM have REST APIs with OAuth 2.0 and documented per-plan rate limits. A Zoho sync is faster to build (₹40,000 to ₹1,00,000) but must be designed around the daily call quota on lower plans.
• Custom ERPs (SAP, Oracle, Microsoft Dynamics, in-house systems) need a middleware layer that owns mapping, retries and audit logs: the ₹10 lakh and up projects in the cost table, measured in months.

If you are choosing an ERP with integration in mind, our best ERP software in India guide rates the Indian options by API quality, and the custom software and CRM/ERP service page explains how we scope middleware.

How do inventory and marketplace sync APIs work?

If you sell on Shopify, Amazon, Flipkart, Myntra and your own site, stock must update everywhere within minutes of a sale or one channel oversells. Unicommerce (deep Flipkart, Amazon India and Myntra connectors) and Vinculum (D2C with owned warehousing) are the off-the-shelf options. If your operations are genuinely unusual (made-to-order, bundles, multi-warehouse rules), a bespoke sync layer on the Amazon SP-API, Flipkart Seller API and Shopify Admin API costs ₹1,50,000 to ₹5,00,000 across four or five channels and avoids per-order platform fees. Most Indian brands outgrow off-the-shelf sync around ₹5 crore in annual revenue. ONDC adds its own buyer and seller app layer, covered in our ONDC integration guide.

What do SMS OTP and login APIs cost, and what did TRAI change?

SMS OTPs still dominate Indian login flows. MSG91 (OTP, SMS, voice and email in one account; its India price page lists ₹0.25 per SMS at 5,000 messages down to ₹0.16 at about 10 lakh, and ₹0.13 on negotiated volume, checked 5 October 2026) is the usual pick, Twilio Verify the international fallback, Gupshup the bundle with WhatsApp, and the Truecaller SDK the one-tap sign-up for fintech and e-commerce apps. For KYC, UIDAI's offline Aadhaar XML has been discontinued and DigiLocker document fetch with user consent is the replacement providers now point to.

Integration is a week of work, ₹15,000 to ₹40,000, if DLT is handled. Two TRAI rules decide whether your OTPs are delivered at all:

1. DLT registration with a PE-TM chain. Your entity, every sender header and every template must be registered on an operator DLT platform; since 1 December 2024 traffic without a valid principal entity to telemarketer chain is rejected.
2. Header suffixes since May 2025. Under the TCCCPR 2025 amendment, telcos added a type suffix to every header (MediaNama covered the rollout on 20 May 2025): -P promotional, -S service, -T transactional, -G government. OTPs must go out on a -T header or they get blocked or bucketed as promotional.

A serious integrator handles DLT registration as part of the build; skip it and delivery collapses in a way that looks like a code bug.

Should you add AI APIs to your integration stack?

A growing share of our integration work since 2025 includes an LLM API (OpenAI, Claude, Gemini) answering WhatsApp order queries from your database, extracting line items from supplier invoice PDFs, or classifying support tickets. Treat it like any other integration: retries, logging, a hard hand-off to a human when confidence is low, and a usage cap because billing is per token in USD. Builds run ₹40,000 to ₹2,00,000; the OpenAI integration page lists the patterns we have shipped. Do not start here: an AI bot on a CRM that does not yet receive WhatsApp webhooks has nothing to work with.

What goes wrong in API integrations?

These are the recurring faults in code we inherit.

1. No webhook signature verification. Anyone with the URL can fake a paid order.
2. No idempotency. A duplicate webhook creates a duplicate shipment or double-credits a wallet.
3. No retry with backoff. One blip during a GSP call leaves an invoice without an IRN until the buyer's ITC is rejected.
4. Secrets in source code. Keys committed to GitHub are harvested by scanner bots within hours.
5. No dead-letter queue. Failed messages vanish instead of landing where a human can replay them.
6. Synchronous calls in the hot path. A slow gateway or BSP call freezes checkout for 30 seconds.
7. No rate-limit handling. Marketplace and Zoho APIs throttle at scale and the sync silently stops.
8. Timezone drift. Settlements in IST, orders in UTC, reconciliation breaks every night at 5:30.
9. Consent not logged. Under the DPDP Rules you will need to show when and how a customer opted in to WhatsApp or shared KYC documents.

What does an API integration agency charge per hour vs fixed price?

Engagement model	Typical Indian rate (Oct 2026)	Best for	Watch out for
Hourly freelancer	₹800 to ₹2,500 an hour	One simple integration, clear spec	Availability in month four when the webhook breaks
Hourly agency developer	₹1,500 to ₹5,000 an hour	Ongoing work inside your existing team	Hours grow when the spec is loose
Fixed-price project	₹15,000 to ₹5,00,000 per scope	Defined integrations with acceptance tests	Scope must include monitoring and retries, not just the happy path
Monthly retainer	₹5,000 to ₹25,000 a month per stack	Keeping 3 to 10 integrations current through provider changes	Make sure provider API deprecations are explicitly covered

Fixed price with named acceptance criteria is what we recommend for anything touching payments or compliance. Hourly suits exploration and small changes. A retainer earns its cost the first time Meta, NPCI or the GST portal changes a rule, which in 2026 has been roughly once a quarter.

An in-house developer works if you already have a senior backend engineer with time to learn each provider's quirks; it fails when integrations are a side quest for someone hired to build features. A specialist agency makes sense when someone must own the whole chain. Before you sign with any agency, including us, ask five questions:

1. Show me the webhook handler from your last project and where it verifies the signature.
2. What happens when the provider is down for 20 minutes?
3. Who registers the DLT and Meta templates, and who owns those accounts afterwards?
4. What is in the monitoring dashboard on day one, and who gets paged?
5. What does the retainer cover when Meta or NPCI changes pricing or a schema?

What we see in projects

A few patterns from our own work.

• The first integration a client asks for is almost always payments, but the one that changes their week is usually WhatsApp order updates, because support tickets drop the day it goes live.
• Inherited GST integrations fail most often on credit notes, not invoices. The original developer tested the sale and never the return.
• Tally sync is the project with the widest gap between the client's estimate ("it's just an export") and reality, because Tally's XML interface has to run next to the Tally installation and the accountant's machine is not a server.
• Clients who negotiated 0% UPI in 2025 are now asking what the 15 October 2026 MDR change does to their blended rate. For an average order under ₹2,000 the answer is nothing; above it, roughly 0.4% on those orders, and the reconciliation code needs the extra fee column.

We are a team of 5 to 20 depending on the quarter, rated 4.9 on Google from 76 reviews and Top Rated on Upwork, and we have been doing this from Lucknow since 2017. Our reviews and case studies are public if you want to check.

How we run an integration project

A free 45-minute discovery call (book it here) covers your stack, volumes and compliance thresholds, then a one-to-three-day audit reads the provider docs against your code and lists the failure modes. You get a fixed-price proposal with acceptance tests, with retries, signature checks and monitoring in scope by default, built in weekly increments over two to eight weeks and handed over with dashboards, alert rules, runbooks and account ownership. For a quote, use get a free quote, or book a call if you would rather talk first.

What is changing for API integrations in late 2026?

• UPI MDR of 0.4% above ₹2,000 from 15 October 2026 (NPCI circular of 15 September 2026); NPCI's 30% market share cap on any single UPI app is deferred to 31 December 2026.
• DPDP Rules 2025, notified on 13 November 2025, phase in over 18 months: consent manager registration from 13 November 2026 and the core consent, security and breach obligations from 13 May 2027. Opt-in logs and retention rules belong in your integration design now.
• Account Aggregator is infrastructure now: Sahamati's live dashboard lists 1,076 FIUs and 176 FIPs as of October 2026, and RBI recognised Sahamati as the sector's self-regulatory organisation on 5 June 2026. Lending and wealth products should plan on AA consent flows rather than statement uploads.
• WhatsApp Pay is a real checkout rail: Business Today reported 167 million UPI transactions in July 2026 (published 17 August 2026), after NPCI removed the onboarding cap on 31 December 2024.
• Meta billing: service replies stopped being free on 1 October 2026, and legacy dollar-billed WhatsApp accounts must migrate to rupee billing by 31 December 2026 or Meta stops delivering their messages from 1 January 2027.
• E-invoicing thresholds are stable at ₹5 crore and ₹10 crore for now; the threshold has dropped four times since 2020, so watch for the next cut.

If any of these touch your business, reach out and I will tell you which ones apply, or get a free quote and we will scope the work honestly, including the parts you can skip.