Platform integrations
Productized connections we build once and maintain for every vendor that needs them.
- Versioned interface contract per integration
- Shared roadmap and deprecation policy
- Documented in the public catalog
Integration partner for software vendors
Reliable API integrations for automotive software vendors
De Herstellers builds, hosts and maintains API integrations between automotive software platforms. We work exclusively with software vendors — never with their end customers.
We scope, build, host and maintain integrations; submit the intake and we'll reply within two working days.
What we do
Four services, one scope: the connection between your platform and the systems your customers already run. Everything below is delivered, hosted and maintained by us.
One-off integrations
Bespoke connections for a single vendor, built to the same engineering standard as the productized ones.
- Scoped against your own API and a named counterpart
- Field-level mapping signed off before build
- Owned by us end to end, not handed back as a repo
Hosting
We run what we build: queues, retries, credentials rotation and monitoring on our infrastructure.
- Isolated environments per vendor
- Structured logs with correlation IDs
- Alerting on throughput, latency and error budgets
Maintenance
Upstream APIs change. We track them, adapt the integration and tell you before it breaks.
- Contract tests running against both sides
- Breaking-change notices with a migration window
- Named engineer per integration
How an integration gets built
Every engagement runs the same sequence. No phase starts before the previous one has a written output.
- 011 week
Scoping call
We map the systems on both ends, the data that has to move and the failure modes you already know about.
Output: Scope note with entities, direction and open questions
- 021–2 weeks
Interface design
A written contract before any code: field mapping, error semantics, retry policy and the exact shape of every payload.
Output: Signed interface specification
- 032–6 weeks
Build & sandbox
We build the integration against sandbox credentials, with automated tests covering the mapping and the failure paths.
Output: Working integration on our staging environment
- 041–2 weeks
Acceptance
You test against real-world scenarios. We fix, you re-test, and we agree the go-live criteria in writing.
Output: Acceptance sign-off and go-live date
- 051 day
Go-live
Production credentials, a controlled cut-over and a monitored first week with a named engineer on hand.
Output: Integration live, monitoring dashboards handed over
- 06Ongoing
Operate & maintain
We host it, monitor it and adapt it when either vendor changes their API. Versioned, with a changelog per integration.
Output: Monthly reliability report
From the catalog
Productized integrations, documented like an API reference — supported systems, data flow, authentication and version history.
LivePlatform
DMS Workshop Sync
Bidirectional synchronisation of workshop orders, job lines and status between a dealer management system and a vendor planning platform.
- Systems
- 2
- Version
- 2.3.0
BetaPlatform
Parts Catalog Lookup
Real-time part number, price and availability lookup between a supplier parts catalog and a vendor workshop or webshop platform.
- Systems
- 2
- Version
- 0.9.2
PlannedOne-off
Vehicle Data Enrichment
Enriches licence plate or VIN input with technical vehicle attributes from national registries and manufacturer data sources.
- Systems
- 2
- Version
- 0.1.0
Where we stop
Our customer is always the software vendor. Being explicit about the boundary is what keeps the relationship workable.
- We do not sell to, support or invoice your end customers.
- We do not resell middleware licences or lock you into a platform fee.
- We do not hand over an unmaintained repository and call it delivered.
- We do not take on integrations we cannot host and monitor ourselves.
Have two systems that need to talk?
Send the intake and we come back with a scoping proposal within two working days.