How much does API integration cost? Tiers, yearly upkeep and no-code options

How much does an API integration cost?

“API integration” covers everything from a one-hour webhook to a four-month ERP bridge, so no single price exists. Three public guides, one in euros, show the spread.

VITON¹³ sells integration as a fixed-scope package: from $73 for the three outputs its service page lists (an integration map, a secure data flow, failure monitoring), delivered in 5–8 working days. Systems outside that boundary are priced before approval, so read it as the entry point of a quote, not a substitute for the ranges above.

Why do published prices disagree so much?

Scope, perspective and copying. On the CRM row, Netguru says $20,000–$40,000, Digital Heroes $12,000–$35,000 and Axire €4,000–€10,000 for standard fields. A form pushing leads one way and a two-way sync with custom objects are different products with one name.

Merge, which sells a unified integration API, puts one integration at nearly $50,000 and $50,000–$150,000 a year, on stated assumptions: 150 engineer hours to build, 300 a year to maintain, an engineer at $72.10 an hour, and 150 support tickets of two hours at $52.90. That sums to about $48,300: $10,815 to build, $21,630 to maintain, $15,870 for support. It describes a software company keeping customer-facing integrations alive, not a shop connecting its website to its CRM.

Netguru then repeats Merge’s per-year range and its $50,000 per-integration figure beside a $2,000 starting price. Matching numbers on two sites can be one estimate quoted twice.

What makes one integration cost more than another?

The firms agree on drivers more than on totals. These figures describe the sources’ own projects, not yours.

To size your own project, multiply objects by directions by events. Qtim, a Russian software firm, works one shop through: three objects (customer, order, stock), two directions and four events (create, pay, ship, cancel) make 24 exchange scenarios; checking each for a duplicate, an unavailable system and a back-dated change adds 72 exception checks. That is the work behind “testing” in a quote.

What does an integration cost after launch?

Plan three more lines. Upkeep: Digital Heroes and Axire both say 15–20% of the build price a year, because you control neither end and providers retire versions and change limits. Changes: Digital Heroes expects 20–35% of the build price in year one for new fields and filters. Hosting: $50–$600 a month for a queue and database, by Digital Heroes’ estimate.

On a $30,000 build, Digital Heroes’ arithmetic gives $41,000–$54,000 for year one. The API provider may bill usage too, and some gate access behind a paid plan, so read its price page before the quote arrives.

• Who rotates the keys and watches failure alerts after handover?
• What does a change cost per hour? Digital Heroes says to name the rate in the contract and calls $95–$150 fair.
• Which API versions is it built on, and what happens when one is retired?

Should you build custom, use Zapier, Make or n8n, or buy a connector?

Netguru frames it as control against speed: custom code needs a large upfront spend and maintenance; platforms bring pre-built connectors and faster deployment.

When the middle route fits, VITON¹³’s n8n automation starts from $73: one production workflow connecting up to three services, with retries and a runbook. Go custom when the flow must survive audits or spikes.

What is different about a payment gateway integration?

It carries two bills: the build, and the gateway’s fee on every sale. The build runs from €2,000–€5,000 for basic cards (Axire) to $10,000–$25,000 (Netguru). PayPal’s US list shows 3.49% plus a fixed fee for Checkout and 2.99% plus a fixed fee for cards, with 1.50% more on international payments; Netguru cites 2.9% + $0.30 for mainstream gateways. Rates depend on country and volume, so read your own provider’s page.

How you embed checkout changes your PCI scope. The PCI Security Standards Council explained in 2025 that SAQ A’s script-protection criterion applies to merchants who embed the provider’s payment form in an iframe, not to those who redirect customers to the provider or fully outsource payment. Your acquirer or card brand tells you which questionnaire applies. Digital Heroes adds $4,000–$10,000 of architecture to keep card data off your systems; this is not legal advice.

• Webhooks decide an order’s status, so the handler must tolerate a delayed, repeated or reordered event.
• Refunds, partial refunds, failed payments and reconciliation each need their own path.

VITON¹³’s payment system integration, from $73, covers checkout, webhook and refund flows and transaction reconciliation. Gateway fees go to the provider.

How do you write an integration brief that gets comparable quotes?

Vendors price different projects if you describe different ones. Send every vendor the same facts:

1. Both systems by name and edition: Salesforce Professional and Enterprise are different integrations.
2. The direction: one way in, one way out, or both.
3. The objects and roughly how many fields each: “orders and customers, about 25 fields” is enough.
4. Volumes: records to carry across on day one, and per day afterwards.
5. Freshness in plain words: “stock may be an hour old, orders must arrive within five minutes”.
6. The source of truth for each object, and what happens when both sides change it.
7. Whether a sandbox exists, who holds the credentials and any compliance regime.
8. One normal example, one failed example, and the person who accepts the result.

Ask each vendor for hours by connector, the assumptions priced and the rate for later changes. A quote that never mentions retries, a sandbox or monitoring has priced the happy path.

When should you not build an integration yet?

• Volume is low and a documented manual handoff costs less than automation risk.
• Nobody can say which system wins when the two disagree; settle that first.
• The other API has no sandbox or documentation; pay for a short discovery or pilot before production.
• One of the two tools already ships the feature natively.
• No one will own upkeep: alerts, key rotation and version changes need a named person.

A smaller route is valid only if every failure stays visible and a retry never creates a duplicate.

What would an integration cost with VITON¹³?

The integration is selected. Add payments or an n8n workflow if the flow needs them. Totals add the live starting prices in both production modes; hosting and third-party plans are not included.

The integration takes 5–8 working days, payments 5–8 working days and the n8n workflow 5–8 working days, from an approved brief.