Why API Integration Is Essential
The portal has a web interface for manual entry, but for companies sending more than 5-10 delivery notes daily, manual input is unsustainable. API integration enables automatic creation, receipt confirmation, and status synchronization.
System Architecture
- Protocol: HTTPS (TLS 1.2+)
- Format: JSON
- Authentication: Qualified electronic certificate (mutual TLS) + API key
- Documentation: Available on the portal after registration
Key API Endpoints
| Endpoint | Method | Description |
|---|---|---|
| /api/v1/delivery-notes | POST | Create new e-delivery note |
| /api/v1/delivery-notes/{id} | GET | View single delivery note |
| /api/v1/delivery-notes | GET | List delivery notes (with filters) |
| /api/v1/receipt-notes | POST | Create receipt note (confirm receipt) |
| /api/v1/delivery-notes/{id}/status | GET | Delivery note status |
| /api/v1/delivery-notes/{id}/pdf | GET | PDF version for printing |
Integration with Popular ERP Systems
SAP
Use SAP PI/PO or SAP Integration Suite. Map from SD module (Shipping/Delivery document) to API format.
Microsoft Dynamics
Use Power Automate or custom connectors. Map from Sales/Transfer Orders.
Local ERP Systems
Most local ERP solutions (Pantheon, Lidder, Bild, 4D) are developing or have e-delivery note modules.
Common Integration Issues
- Certificate not properly configured — must be on the server, not just workstation
- Wrong date format — API expects ISO 8601 (YYYY-MM-DDTHH:mm:ss)
- Missing required fields — API returns 400 with field list
- Recipient not registered — recipient must exist in the system
- Timeout with large shipments — split 100+ items across multiple notes
Webhook Notifications
The portal supports webhooks for real-time status updates — receipt confirmation, acceptance/rejection, deadline warnings.
Conclusion
API integration is the only sustainable approach for high-volume operations.
Arhivix has a ready-made portal integration — connect your ERP to Arhivix, and it communicates with the portal for you.
