What Influences Integration Costs?
The most important cost factor is the API quality of the target system. Well-documented REST APIs with a sandbox environment are inexpensive to integrate. Poorly documented or proprietary APIs significantly increase the effort.
Other factors: data mapping (how different are the data structures?), error handling (what happens during outages?), and security(OAuth, API keys, certificates?).
REST API vs. GraphQL vs. Webhooks
REST APIs are the standard for most integrations. Easy to understand, well-documented, broad support. Ideal for CRUD operations and classic system integration.
GraphQL is suited for complex data queries and mobile apps. More flexible than REST, but higher development effort. Recommended when clients need different data subsets.
Webhooks for real-time events: the target system automatically notifies you of changes. Often combined with REST for bidirectional communication.
Legacy Systems Without API
Not every system has a modern API. For legacy systems, there are still integration options:
- Direct database: DB access (with caution!)
- File exchange: CSV, XML, EDI via shared folder or SFTP
- RPA/Screen scraping: UI automation as a last resort
- Middleware: Custom API layer in front of the legacy system


