Nosotros construimos la integración con DIWASS. Usted la obtiene, aplicada a su stack.
Cabeceras WS-Security. Aplicación de llamadas secuenciales. Sincronización NTP. Construcción de mensajes XML. Construir esto lleva meses. Evreka ya lo ha construido: usted obtiene la integración.
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
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.
Cómo funciona la capa de integración con DIWASS
The Evreka DIWASS layer sits between your existing system and the DIWASS API. Your data in, compliance out.
La primavera de 2026 es la ventana de pruebas.
El entorno de pruebas (sandbox) de DIWASS ya está activo. No construya solo: reserve una llamada técnica de descubrimiento y dimensionemos juntos el enfoque de integración adecuado.