Skip to content
ENNO
← Back to services
⟷

Service

API & Integration Development

I connect systems that were never designed to talk to each other. REST APIs, webhooks, data pipelines and third-party integrations that fail gracefully.

What I deliver

I design and build APIs that connect your systems, whether that's syncing data between a CRM and an ERP, exposing internal services to partners, or building a public API for your product. Every integration comes with proper error handling, retry logic, and observability so you know what's happening in production.

Technologies

Most of my integration work is in C#/.NET with ASP.NET Core, but I'm comfortable working with REST, GraphQL, webhooks, message queues (Azure Service Bus, RabbitMQ), and file-based integrations (SFTP, CSV, XML). I've built integrations against Dynamics 365, Visma, Tripletex, Stripe, and dozens of custom systems.

What to expect

Clear API contracts (OpenAPI/Swagger), proper authentication (OAuth2, API keys, mTLS), structured logging, and documentation that your team can actually use. I test integrations against real sandboxes, not mocks.

How I approach it

Most integration work is not hard because the protocols are difficult. It's hard because the two systems disagree about what a customer is, one of them returns a 200 for a failure, and the vendor's documentation was last accurate two years ago. I start by finding out what the other end actually does rather than what it claims to, then build against that.

Where a third party is unreliable, the integration is built to survive it going down rather than to assume it won't. Typical work: connecting a CRM to an accounting system so invoicing stops being manual, pulling several vendor feeds into one normalised shape, or replacing a fragile nightly script with something that can be watched and rerun safely.

Case studies

Systems I have integrated with