What is an API? How APIs work, with business examples
An API (application programming interface) is a defined way for one software system to request data or actions from another: which requests it accepts, in which format, with which permissions, and what it returns. APIs are how your store, accounting, CRM, payment provider and logistics partners talk to each other without anyone copying data by hand. This guide explains what an API is in plain words, how a request and response work, the parts of an API, the main types, business examples, the benefits and limits, security basics and the EU rules that now require some products to offer data access.
The short version
- An API is a contract between systems: what you may ask, how to ask and what you get back.
- Most business APIs are web APIs over HTTPS, exchanging data in JSON.
- API keys and OAuth tokens control who may use an API and what they may do.
- An API is a door, not a connection; integrations are what use the doors to move data reliably.
How an API works
Take an online store that needs to know whether a customer's payment went through. The store's software sends a request to the payment provider's API: an address (the endpoint for payments), a method (read this payment), an identifier (the payment number) and a key or token that proves who is asking. The provider checks the permission, looks up the payment and sends back a response: a status code that says whether the request worked, and data such as the amount, currency and status in a structured format, usually JSON.
The store does not see the provider's database, code or internal systems. It only sees what the API offers. That separation is the point: each side can change its internals freely as long as the agreed interface stays the same. When the provider does need to change the interface, it publishes a new version and gives users time to move.
Many APIs also work the other way round. Instead of the store asking every minute whether the payment is complete, the provider sends a message to the store when the status changes. These push messages are called webhooks, and they are how most systems learn about events quickly without constant polling.
The parts of an API
- Endpoints: the addresses for each kind of data or action, such as orders, customers or invoices.
- Methods: in HTTP APIs, GET reads, POST creates, PUT or PATCH changes and DELETE removes; RFC 9110 defines these semantics.
- Request and response formats: usually JSON, sometimes XML, with defined fields and types.
- Authentication: API keys for software-to-software access, OAuth 2.0 tokens for access on behalf of a user.
- Status codes and errors: standard codes such as 200, 404 or 429, ideally with machine-readable error details as described in RFC 9457.
- Rate limits: how many requests a client may send per minute or day.
- Versioning: how changes are introduced without breaking existing users.
- Documentation: the description that tells others how to use it, often in OpenAPI; see our API documentation guide.
In front of many APIs sits an API gateway: a layer that checks keys and tokens, applies rate limits, logs traffic and routes requests to the right internal service.
Types of APIs
- By audience: public or open APIs anyone can register for, partner APIs for selected companies, and internal APIs used only inside an organisation.
- REST APIs, the most common style for business systems, built on HTTP methods and resource addresses.
- GraphQL APIs, where the client asks for exactly the fields it needs in one query.
- SOAP APIs, an older XML-based style still common in banking, government and large ERP systems.
- Webhooks and event streams, which push events to subscribers instead of waiting for requests.
APIs in everyday business
- An online store sends orders to the warehouse system and receives tracking numbers from the carrier.
- Accounting software fetches bank transactions and matches them to invoices.
- A CRM creates a customer in the ERP when a deal is won, and the ERP sends invoice status back.
- A booking system checks availability, takes payment and sends a confirmation message.
- An AI assistant reads documents or creates tickets through the APIs of the systems it is allowed to use.
Each of these is an API integration: work that uses two or more APIs, maps data between them and handles failures.
Benefits and limits
The benefits are speed and accuracy. Data moves between systems in seconds instead of being retyped, so errors fall and staff time goes to work that needs people. Companies can combine specialised tools instead of forcing everything into one suite. Partners and customers can connect directly, which makes a company easier to work with.
The limits are just as practical. An API only offers what its provider chose to expose, and some systems have weak APIs or none. Rate limits and usage fees constrain how much data can move. Providers change or retire versions, and integrations must keep up. Every API is also an entry point that must be secured. The OWASP API Security Top 10 (2023 edition) lists broken object level authorisation as the first risk, ahead of broken authentication, which shows how often APIs return data to clients that should not see it.
Security basics
- Keep keys and tokens out of websites, apps and code repositories; store them in a secrets vault and rotate them.
- Give each client only the permissions it needs, and check permissions on every object, not only at login.
- Use OAuth 2.0 for user-delegated access and follow RFC 9700 (January 2025), the IETF's best current practice for OAuth 2.0 security, which for example requires public clients to use PKCE.
- Log requests, watch for unusual volumes and keep an inventory of every API and version that is live.
Rules that affect APIs in the EU
- Data Act. Regulation (EU) 2023/2854 applies from 12 September 2025. Under Article 3(1), connected products placed on the market after 12 September 2026 and their related services must make product data accessible to the user by default, easily, securely and in a structured, commonly used and machine-readable format, where relevant and technically feasible directly. For many manufacturers, an API is the practical way to meet that duty.
- Data portability. GDPR Article 20 gives people the right, in defined cases, to receive their personal data in a structured, commonly used and machine-readable format and to transmit it to another controller.
When to build your own API or integration
Ready-made connectors and integration platforms are a good choice for standard links between popular tools. Custom work is worth comparing when:
- The systems you need to connect have no standard connector, or the connector does not handle your fields, volumes or error cases.
- You need your own API so that partners, customers, apps or AI assistants can use your data safely.
- An old system without an API has to be connected through files, a database or a new interface built around it.
- Product data has to be offered to users under the Data Act.
- You want to own the integration code and the monitoring, instead of paying per connection or per task.
Our API integration services design and build these connections, hosted in the EU and owned by you. Before deciding, read what drives API integration cost and how to write good API documentation. Every guide is in the guides library.
Questions people ask
What is an API in simple terms?
An API is an agreed way for one piece of software to ask another for data or an action. Like a counter in a shop, it defines what you can ask for, in which form, and what you get back, without letting you into the stockroom. When your online store checks a payment or your accounting software fetches bank transactions, an API is doing the work.
What does API stand for?
API stands for application programming interface. An interface is the meeting point between two systems; application programming means it is used by software, not by people clicking buttons. Most APIs in business today are web APIs, reached over the internet with the same HTTP protocol that web pages use.
What is an API key?
An API key is a long secret string that a program sends with each request to identify itself to an API. The provider uses it to decide what the program may do and to count usage. An API key is a password for software: it must not appear in websites, apps or shared documents, and it should be possible to rotate it. For access on behalf of a user, OAuth 2.0 tokens are used instead.
What is an API endpoint?
An endpoint is one specific address of an API that offers one kind of data or action, for example the address that returns a list of orders or the one that creates a new customer. An API is usually a set of endpoints, each accepting certain request methods and parameters, and documented together, often in the OpenAPI format.
What is the difference between an API and an integration?
An API is the door a system offers; an integration is the work of connecting two or more systems through their doors. The integration decides which data moves when, how fields map from one system to the other, what happens when one side is down and how errors are reported. One integration often uses several APIs.
Sources
- IETF RFC 9110, HTTP Semantics (read 13 November 2026)
- IETF RFC 9457, Problem Details for HTTP APIs (read 13 November 2026)
- IETF RFC 9700, Best Current Practice for OAuth 2.0 Security (January 2025) (read 13 November 2026)
- OpenAPI Specification, version 3.2.1 (10 September 2026) (read 13 November 2026)
- OWASP API Security Top 10 (2023 edition) (read 13 November 2026)
- Regulation (EU) 2023/2854 (Data Act), Articles 3(1) and 50 (read 13 November 2026)
- Regulation (EU) 2016/679 (GDPR), Article 20 (read 13 November 2026)