Contents
At a glance
- Category
- Automation mechanics
- Stands for
- Application programming interface
- Hard rule
- No API means no reliable automation - scraping breaks on any UI change
- Check before quoting
- Existence, coverage, plan tier, auth method, rate limits, webhook support
- Hidden cost drivers
- Small page sizes, no modified-since filter, no webhooks
- Ongoing risk
- Versions deprecate and response shapes change - follow the changelog
What an API is
An API - application programming interface - is the contract a piece of software publishes for other software: here are the requests I accept, here is the data you must send, here is what I return. Your CRM has one, your accounting package has one, your phone system has one. Every automation you build is a sequence of API calls, whether you write them or a connector writes them for you.
The practical consequence is stark: if a system has no API, it cannot be automated reliably. Screen scraping and browser automation exist as workarounds and they break whenever the vendor changes a button. Before promising anyone an integration, check the API exists, and check it supports the specific operations you need rather than just existing.
What to check before you commit
Six questions, in order. Does an API exist, and is it publicly documented? Does it cover the operations you need - reading a record is common, creating one less so, and updating a specific field on an existing record less so again. Is it available on the customer's plan, since many vendors gate API access behind a higher tier? How does it authenticate - an API key or OAuth, and the difference is hours of setup work.
What are the rate limits? And does it support webhooks, or will you have to poll? Answering those six before quoting an integration is the difference between a project that lands on time and one that discovers in week three that the plan does not include API access.
The shapes you will meet
Most business APIs are REST over HTTP returning JSON, which every automation platform handles natively. GraphQL appears in newer products and lets you request exactly the fields you want in one call. Older or enterprise systems may offer SOAP, which is XML-based and heavier but still workable. A few expose only a file drop or a database connection, which is automation of a sort but with none of the immediacy.
Whatever the shape, the same operational realities apply: authentication expires, limits get hit, responses change format without warning, and the same request sometimes arrives twice. Those are covered under OAuth, rate limits, error handling and idempotency.
Cost and the hidden expenses
Many APIs are included in a subscription; some charge per call or require a developer plan. The costs that surprise people are indirect: an API that only returns twenty records per request turns a sync of ten thousand into five hundred calls; an API with no modified-since filter forces you to fetch everything every time; an API without webhooks forces polling, and every poll consumes your platform's billing unit.
Read the documentation's pagination and filtering sections before estimating any integration. They determine the work far more than the number of endpoints does.
What you should know
APIs change. Vendors deprecate versions, add required fields and alter response shapes, usually with notice you will not read. Subscribe to the changelog for anything your business depends on, pin an API version where the vendor supports it, and log raw responses so that when something breaks you can see immediately whether the shape changed.
And check the terms of use, particularly for anything customer-facing. Some APIs restrict how you may store the data, how long you may cache it, or whether you may pass it to a third party - which includes sending it to an AI provider, so it interacts directly with your data processing obligations.
API FAQ
What is an API in plain English?
The list of requests a piece of software will accept from other software, and what it gives back. It is how your CRM, your accounting package and your phone system can be told to do things by an automation rather than by a person clicking.
Can I automate a system with no API?
Only unreliably. Browser automation and screen scraping can click through a interface, but they break whenever the vendor moves a button, and many terms of service prohibit them. Treat a missing API as a strong argument for changing the tool rather than working around it.
What should I check before promising an integration?
Whether the API exists and is documented, whether it covers the specific operations you need rather than just reading, whether it is included on the customer's current plan, how it authenticates, what the rate limits are, and whether webhooks are available.
Why is my integration slower than expected?
Usually pagination. An API that returns twenty records per call turns a ten-thousand-record sync into five hundred sequential requests, each subject to rate limiting. The page size and filtering options in the documentation predict integration effort better than the endpoint count does.
Do APIs cost money?
Sometimes directly, but more often through plan tiers - a lot of vendors gate API access behind a higher subscription. The indirect costs matter more: no webhooks means polling, and every poll consumes your automation platform's billing unit whether or not it finds anything.
What happens when an API changes?
Your automation breaks, usually silently and usually at an inconvenient time. Subscribe to the vendor's changelog, pin an API version where that is supported, and log raw responses so you can immediately see whether the payload shape changed or your own mapping did.
Primary source
Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what api means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
