Solutions
Who We Serve
Our Solutions
Who We Serve
Home›Who We Serve›ERP & IT Teams
💻 ERP & IT Teams

We built the DIWASS integration. You get it - applied to your stack.

WS-Security headers. Sequential call enforcement. NTP synchronization. XML message construction. Building this takes months. Evreka has already built it - you get the integration.

DIWASS API: technical requirements
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
✓ Evreka's connector handles all of this. Your team maps data fields - we handle the protocol.
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

How the DIWASS integration layer works

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.
How long does integration take?
1 week
Discovery + scoping
3-4 weeks
Build + sandbox testing
4-5 weeks
Total to go-live
Building from scratch typically takes 3-5 months. Evreka integration starts from a working production foundation, cutting that to weeks.

Spring 2026 is the testing window.

The DIWASS sandbox is live now. Don't build alone - book a technical discovery call and let's scope the right integration approach together.

On this page