An API is the part of a system nobody sees, yet it decides whether your app, website and partners' software get accurate data on time. We build it so other developers can use it without constantly emailing us.
When a mobile app shows stock levels, when a shipping carrier receives shipment details or when a partner checks an order status on their own, it happens through an API. It's the set of rules by which two programs exchange data, with no person in between.
We do two kinds of work: we build APIs for your system so others can use it, and we connect your system to other services' APIs.
01
REST or GraphQL
REST is still the most common choice, especially when the API is used by partners and external systems. It's easy to understand, every developer knows how to work with it and it caches well.
GraphQL makes sense when the same data is needed by a website, a mobile app and an admin panel, each in a different shape. The client then asks for exactly the fields it needs in one query, instead of five calls and a pile of unused data.
We usually build APIs on API Platform, which provides both REST and GraphQL from the same data model. So the choice doesn't have to be final - the other approach can be added when needed.
02
Documentation, versioning and security
Every REST API comes with OpenAPI documentation, with examples developers can try directly in the browser. A GraphQL API is described by its own schema, which tools read automatically. When the API changes, the old version keeps working for an agreed transition period, so nothing breaks for partners overnight.
We secure access with API keys or OAuth 2.0 tokens, every API user has only the permissions it needs, and requests are rate-limited so one badly written client can't bring down the whole system. Every call is logged, so when something doesn't work, it's quick to see where it got stuck.
03
Integrating third-party APIs
We connect websites and applications to payment providers, shipping carriers, ERPs, CRMs and accounting software. Most of the work isn't the call itself, but what happens when the other side doesn't respond.
That's why messages go through a queue and are retried at intervals, instead of an order getting lost because a carrier's service was down for five minutes. If they still fail after several attempts, the responsible person is notified, and the same order is never recorded twice. When several logistics systems need to be connected, see also logistics system integration. An API is usually part of a larger application, and how we run those projects from start to finish is on our web application development page.
FAQ
Questions about API development
A set of rules by which two programs exchange data. For example, your store asks a shipping carrier how much delivery costs, and it answers - without anyone typing anything.
For partners and external systems, usually REST. For your own frontend and mobile app, often GraphQL. With API Platform you can have both.
Usually yes. It depends on what the system is built with and how it stores data, so we review it first.
With access tokens, per-user permissions, rate limiting and logging of every call.