Question10 min read
How Much Does API Integration Cost?
Quick answer
An API integration has two costs: the build, set by how many systems connect, one-way or two-way sync, data mapping, login method, error handling, volume limits and how good the other API's docs are; and the running cost, which is Zapier or Make task fees or hosting for custom code, plus upkeep when a vendor changes its API. At Zapier's published prices checked Nov 11, 2026, 10,000 tasks a month on the Professional plan is $129 a month billed annually.
Reviewed by Alpit Patel, Founder and CEO · Updated November 11, 2026
On this page 9 sections
Key takeaways
- An API integration costs a build and a running bill. Budget for both, plus upkeep when either vendor changes its API.
- The build gets bigger with more systems, two-way sync, messy data mapping, expiring logins, high volume and weak API docs.
- Zapier bills per task and does not count the trigger: at Nov 11, 2026 prices, 10,000 tasks a month is $129 on Professional billed annually, and 100,000 tasks is $489.
- Every extra action adds a task per record: at these tiers, 10,000 records a month through three actions moves Zapier Professional from $129 to $289 a month billed annually.
- Use a native integration when it covers your fields, Zapier or Make for simple flows at modest volume, and custom code for two-way sync, high volume or data where a mistake costs money.
How much does API integration cost?
An API integration costs two things: the work to build it, and the monthly bill to keep it running. The build is driven by how many systems connect, whether data flows one way or both ways, how much the data has to be reshaped between them, how each system handles logins, how much error handling the job needs, how much volume runs through it and how good the other side’s API documentation is. The running cost is either Zapier or Make task fees or hosting for custom code, plus someone’s time when a vendor changes its API.
We quote integration work on its scope after a free call, because a one-way connection to a well documented API and a two-way sync between three systems are different jobs. When the integration is part of a full app or web app build, it sits inside our build range: $7,000 for a focused first version to about $25,000-$30,000 for many features, user roles, payments and integrations, and larger builds are quoted on their scope. Our custom software development page covers how those builds are scoped.
What does it cost to run on Zapier or Make?
The running cost is where most owners get surprised, because it grows with every record and every step. The arithmetic below uses the published pricing.
We assumed each record (a new order, a new contact, a paid invoice) runs through an automation with one trigger and one action. Zapier does not count triggers as tasks, so that is one task per record. Make counts the trigger as one operation per run and then one per module per record, so with an instant trigger it is about two credits per record.
| Records a month | Zapier Professional (annual / monthly billing) | Zapier Team (annual / monthly) | Make (estimate) |
|---|---|---|---|
| 1,000 | $39.00 / $58.50 (1,500-task tier) | $69.00 / $103.50 (smallest tier, 2,000 tasks) | About 2,000 credits, more than the 1,000-credit Free plan, so Core from $9 a month billed annually (10,000 credits) |
| 10,000 | $129.00 / $193.50 | $169.00 / $253.50 | About 20,000 credits: roughly $20 a month (illustrative: $9 for 10,000 plus 10,000 extra credits at the 25% surcharge) |
| 100,000 | $489.00 / $733.50 | $599.00 / $898.50 | About 200,000 credits: roughly $150 a month (illustrative, at the $0.000759 per credit rate in Make’s own Core example) |
Sources: Zapier pricing page; Make’s Make vs n8n comparison page and Help Center articles on operations, subscriptions and plan adjustments. All checked Nov 11, 2026. Zapier prices are per month in USD; annual plans are billed yearly at 33% off monthly. Make’s pricing page shows prices on a slider that we could not read in text, so the Make column is an estimate built from Make’s published examples. Confirm on the slider before you buy.
Three things change the numbers fast:
- More steps. Each extra action is another task per record on Zapier (built-in Filter and Paths steps do not count) and another credit per record on Make. If each record runs through three actions, 10,000 records become 30,000 Zapier tasks, which needs the 50,000-task tier: $289 a month billed annually.
- Going over. Zapier’s pay-per-task overage is 1.25 times the base rate on annual plans and 2.5 times on monthly plans, and usage stops at three times your plan. Make sells extra credits at a 25% surcharge, and scenarios stop when credits run out.
- Polling on Make. Make counts a trigger as one operation per check. A scenario that checks often uses credits on checks as well as on records, which is one more reason to use an instant trigger when the app offers one.
What does custom code cost to run?
For a small integration, the hosting bill can be close to zero. AWS Lambda, one common place to run this kind of code, includes one million requests and 400,000 GB-seconds of compute a month in its free tier. As an illustration, 100,000 runs a month at 512 MB for one second each is 50,000 GB-seconds, inside that free tier. Past the free tier, AWS lists $0.20 per million requests and $0.0000166667 per GB-second, so the same workload would be under $1 a month.
That is not the whole running cost. A custom integration also needs logging, alerts when something fails, often a small database to remember what has already synced, and a developer when an API changes. Those are real costs; they are just not per-record fees. Our do I need a backend answer explains what that server side does.
How do API integrations work?
An API is a set of web addresses (endpoints) that a system opens up so other software can read or change its data in an agreed format. An integration is code, or a Zapier or Make automation, that calls those endpoints on your behalf. Four parts are worth knowing even if you never write code.
- Login. The integration proves who it is with an API key or an OAuth token. OAuth 2.0 is the standard that lets one app get limited access to another on a user’s behalf, and its access tokens can be short-lived, so the integration has to renew them.
- Webhook or polling. With a webhook, the other system sends a message the moment something happens. With polling, your integration asks “anything new?” on a schedule.
- Rate limits. Most APIs cap how many requests you can make in a given time. Go over and you get an HTTP 429 “Too Many Requests” error, sometimes with a Retry-After header saying how long to wait.
- Retries and duplicates. Things fail in transit. Stripe, for example, retries webhook deliveries for up to three days in live mode, says events can arrive out of order, and warns that the same event can arrive more than once. A good integration expects all three.
How is an API integration done?
- Write down what moves. Which records, which direction, and which system wins when both change the same field.
- Read both APIs. Check the login method, the rate limits, webhooks, and whether there is a test account.
- Map the fields. Match IDs, names, currencies, dates and custom fields between the two systems.
- Build it with failure in mind. Retries, duplicate checks, logging and alerts are part of the build, not extras.
- Test with realistic data in a sandbox before it touches live records.
- Name an owner. Someone watches the alerts and updates it when a vendor changes its API.
Is API integration real time?
It is real time when the source system sends webhooks; otherwise it is as fast as the polling interval. Zapier runs webhook-style “Instant” triggers immediately on every plan, and some Make triggers can run “Immediately as data arrives.” Polling delays depend on the plan, as the table below shows. Custom code can poll as often as the other API’s rate limit allows, or receive webhooks directly.
| Method | Typical delay | Source |
|---|---|---|
| Webhook / instant trigger | Immediately, as the event happens | Zapier Help Center |
| Zapier polling, Free plan | Every 15 minutes | Zapier Help Center |
| Zapier polling, Professional | Every 2 minutes | Zapier Help Center |
| Zapier polling, Team and Enterprise | Every 1 minute | Zapier Help Center |
| Make scheduled scenario | Every 15 minutes by default; minimum depends on plan | Make Help Center |
Checked Nov 11, 2026.
Is API integration hard?
A one-way link between two systems with good documentation is usually straightforward; the hard ones are hard because of what happens when things go wrong. These factors push a job from easy to hard, and they push the build price up too:
| Factor | Easier | Harder |
|---|---|---|
| Number of systems | Two | Three or more, each with its own rules |
| Direction | One way, one system owns the data | Two way, both sides edit the same record |
| Data mapping | Same fields and formats on both sides | Different IDs, currencies, time zones, custom fields, line items |
| Login | API key that does not expire | OAuth tokens that expire, per-user consent |
| Change events | The source sends webhooks | You poll and work out what changed |
| Volume | A few hundred records a day | Bulk imports, monthly spikes, tight rate limits |
| Documentation | Clear docs, a sandbox, stable versions | Thin docs, no test account, frequent breaking changes |
| Cost of a mistake | A missed record is a nuisance | A missed record is a wrong invoice or oversold stock |
Our judgment from integration work, not a published standard.
Native integration, Zapier or Make, or custom code?
Start with the cheapest option that covers your fields and your volume, and move up only when it stops covering them.
| Option | Fits when | Watch for |
|---|---|---|
| Native integration (built into one of the apps) | It exists, syncs the fields you need, and is included in your plan | Fixed field mapping, often one way, no room for your own rules |
| Zapier or Make | A simple trigger and action, modest volume, you want it running this week without a developer | Fees that grow with every record and step, polling delay on lower plans, a flow only one person understands |
| Custom code | Two-way sync, high volume, complex rules, or money and stock data where errors are expensive | A build cost up front, and someone has to maintain it when an API changes |
Our decision rule; prices behind it from Zapier and Make pricing, checked Nov 11, 2026.
One quick check is to multiply your expected Zapier or Make bill by 12. At 100,000 tasks a month on Zapier Professional, that is $489 x 12 = $5,868 a year, before any growth. If the yearly figure is climbing toward the cost of a one-time build, a custom integration is worth pricing. We build custom integrations as part of custom software development.
Can AI do API integration?
AI coding tools can draft a lot of it, but someone still has to own it. This section is our view, not a sourced finding. The tools are good at reading API docs, writing the requests, mapping fields and sketching tests, which makes the typing part of a build faster. They do not know your business rules, such as which system wins when two records disagree. They cannot get production keys or approve an OAuth app for you. And they can write code that looks right but drops a page of results, retries in a way that creates duplicates, or swallows an error. The logins, the error handling, the data checks and the upkeep still need a person who answers for them.
What to do next
Write down the two systems, what should move between them, in which direction, and roughly how many records a month. Bring that to a free 30-minute call. We will tell you whether a native integration or Zapier covers it, and if custom code is the better path, you get a fixed-price quote in writing. The code is yours, and you get a recorded video walkthrough and written documentation at handover.
Sources
- Zapier, Pricing (plan tiers, task definition, overage rules, polling times), checked Nov 11, 2026.
- Zapier Help Center, How Zap triggers work (polling intervals by plan, instant triggers), checked Nov 11, 2026.
- Make, Make vs n8n (Free 1,000 credits; Core $9, Pro $16, Teams $29 a month from 10,000 credits), checked Nov 11, 2026.
- Make, Pricing (plan names, Free plan credits, extra-credit rules), checked Nov 11, 2026.
- Make Help Center, Operations (one operation per trigger check, one per module per bundle), checked Nov 11, 2026.
- Make Help Center, Change your subscription (Core 150,000 credits at $113.85 a month, $0.000759 per credit), checked Nov 11, 2026.
- Make Help Center, Adjustments to plans and pricing (25% extra-credit surcharge), checked Nov 11, 2026.
- Make Help Center, Schedule a scenario (15-minute default, plan-based minimum, “Immediately as data arrives”), checked Nov 11, 2026.
- AWS, Lambda pricing (free tier, request and GB-second prices), checked Nov 11, 2026.
- Stripe, Receive Stripe events in your webhook endpoint (retries for up to three days, ordering, duplicates), checked Nov 11, 2026.
- IETF, RFC 6749: The OAuth 2.0 Authorization Framework, checked Nov 11, 2026.
- IETF, RFC 6585, section 4: 429 Too Many Requests, checked Nov 11, 2026.