Solutions
Who We Serve
Unsere Lösungen
Für wen wir arbeiten
Home›Für wen wir arbeiten›ERP- & IT-Teams
💻 ERP- & IT-Teams

Wir haben die DIWASS-Integration gebaut. Sie bekommen sie - angewendet auf Ihren Stack.

WS-Security-Header. Durchsetzung sequenzieller Aufrufe. NTP-Synchronisation. XML-Nachrichtenaufbau. Das selbst zu bauen dauert Monate. Evreka hat es bereits gebaut - Sie bekommen die Integration.

DIWASS-API: technische Anforderungen
Protocol: SOAP (not REST)
Auth: WS-Security Username Token
Calls: Sequential only (no parallel)
Time: NTP sync required
Password: Digest (nonce+timestamp+key)
Sync: Poll-based, ≤12h interval
Format: XML message exchange
✓ Der Konnektor von Evreka übernimmt all das. Ihr Team mappt Datenfelder - wir übernehmen das Protokoll.
What we provide

Pre-built. Production-tested. Yours to use.

⚡

Pre-built connector

WS-Security auth, SOAP XML handling, sequential call management, NTP sync - all implemented and tested against the DIWASS sandbox.

🗺️

Data mapping layer

Your ERP fields mapped to DIWASS XML schema. We document every field, every transformation, every edge case.

↩️

Sync architecture

getEvents → resolve changes → getDetails implemented as a poll-based sync. DIWASS IDs stored and managed in your system.

✅

Real-time validation

Eural code validated against processor permit on every call. Error messages surface at your system level, not at border control.

🔄

Status management

Full lifecycle: Announced → Moving → Received → Completed - all status transitions handled and returned to your records.

📞

Technical support

Post-launch monitoring, error diagnosis, and updates when DIWASS API evolves. We stay on it so you don't have to.

Integration overview

So funktioniert die DIWASS-Integrationsschicht

The Evreka DIWASS layer sits between your existing system and the DIWASS API. Your data in, compliance out.

Your System
ERP / TMS / WMS
→ REST API →
Evreka Layer
Auth · Payload build · Queue · Retry
↔ SOAP / WS-Security ↔
DIWASS API
EU Government Platform
Authentication
WS-Security password digest + EU Login token management. Handled by Evreka layer.
Sequential calls
DIWASS enforces strict call ordering. Queue management built in with automatic retry.
Schema validation
Every message validated against DIWASS XSD schemas before transmission. Rejections caught locally.
Status sync
Bidirectional: outbound submissions and inbound status updates both flow to your system.
Wie lange dauert die Integration?
1 week
Discovery + Scoping
3-4 weeks
Build + Sandbox-Tests
4-5 weeks
Gesamt bis Go-Live
Building from scratch typically takes 3-5 months. Evreka integration starts from a working production foundation, cutting that to weeks.

Frühjahr 2026 ist das Testfenster.

Die DIWASS-Sandbox ist jetzt live. Bauen Sie nicht allein - buchen Sie ein technisches Erstgespräch, und lassen Sie uns gemeinsam den richtigen Integrationsansatz festlegen.

On this page