Solutions
Who We Serve
Nos solutions
À qui nous nous adressons
Accueil›Pour qui nous travaillons›Équipes ERP & IT
💻 Équipes ERP & IT

Nous avons construit l'intégration DIWASS. Vous l'obtenez - appliquée à votre stack.

En-têtes WS-Security. Application séquentielle des appels. Synchronisation NTP. Construction de messages XML. Construire cela prend des mois. Evreka l'a déjà construit - vous obtenez l'intégration.

API DIWASS : exigences techniques
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
✓ Le connecteur d'Evreka gère tout cela. Votre équipe mappe les champs de données - nous gérons le protocole.
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

Comment fonctionne la couche d'intégration DIWASS

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.
Combien de temps prend l'intégration ?
1 week
Découverte + cadrage
3-4 weeks
Build + tests sandbox
4-5 weeks
Total avant mise en production
Building from scratch typically takes 3-5 months. Evreka integration starts from a working production foundation, cutting that to weeks.

Le printemps 2026 est la fenêtre de test.

Le bac à sable DIWASS est désormais en ligne. Ne construisez pas seul - réservez un appel technique et définissons ensemble la bonne approche d'intégration.

On this page