Frequently Asked Questions: API Development & Integration
(01)How does API versioning work?
We version via the URL path (e.g. /v1/, /v2/): a new major version only comes with breaking changes, everything else stays backward compatible. How far in advance breaking changes are announced and how long the old version keeps running in parallel is something we agree with you. You get migration guides, and deprecated endpoints are marked with Deprecation and Sunset headers (RFC 9745, RFC 8594).
(02)What support do you offer after launch?
We agree the scope of support, availability and response times in the contract – matched to your operations and to the availability commitments of the cloud services involved. From final delivery we fix bugs free of charge for 30 days; for ongoing operations there is the Build & Support format.
(03)Is there a sandbox environment for testing?
Yes, every API comes with a complete sandbox environment. This includes mock servers for contract testing, Postman collections, and interactive API documentation. Developers can integrate and test risk-free.
(04)How is API security ensured?
Our APIs follow OWASP API Security Top 10 guidelines. This includes: secure authentication (OAuth 2.0, JWT), input validation, rate limiting, audit logging, encrypted communication (TLS 1.3), and regular security audits.
(05)How does API development differ from tool integration and the enterprise API platform?
API development builds a new interface for your own product or data – with design, OpenAPI, authentication and versioning. If you only want to connect tools that already exist, tool integration with Make, n8n or webhooks is enough. If many internal systems and partners should work through one centrally governed interface with a gateway, SSO, rate limits and a developer portal, the enterprise API platform is the right service. We place your project in the first call.