←  All terms
A
APIs & Integrations

API

An API is a defined interface through which software systems exchange data and functionality in a controlled way.

An API is a defined interface through which software systems exchange data and functionality in a controlled way. Strong implementations use explicit data contracts, secure authentication, error handling, and observable operations. The concept is closely related to REST API and Webhook.

Read more

REST API

Webhook

JSON

FAQ

API

When is a webhook a better fit than regularly polling an API?
A webhook fits when a system should react to events such as a new order, because the notification arrives immediately instead of at the next polling interval. Polling remains sensible when the sender offers no webhooks. Webhooks need signature verification and retry logic to avoid lost events.
What are typical mistakes in API integrations?
Typical mistakes are missing error handling for timeouts, ignored rate limits, and unannounced changes on the provider side. Missing monitoring often goes unnoticed until data is already absent. An integration needs retry logic, alerting, and a clearly defined data contract.
How is an API protected against unauthorized access?
The foundation is authentication and authorization, for example via API keys or OAuth, plus encrypted transport over HTTPS. Rate limiting and validation of incoming data add further protection. Secrets such as keys never belong in frontend code and should stay on a server.
When does it make sense to build a custom API?
A custom API makes sense when several clients, such as a website, an app, and partner systems, need the same data. For a single website, the interfaces of existing systems are often sufficient. Every custom API creates ongoing effort for versioning, documentation, security, and operations.
How does an API differ from a REST API?
API is the umbrella term for any defined interface between pieces of software, while REST is an architectural style for web APIs built on HTTP and resources. Other approaches such as GraphQL or RPC exist as well. Choosing between them depends on data shape, number of clients, and caching requirements.