What is PortalData Export
Based on the event added to a package/shipment, PortalData can be configured to trigger an export.
In the background, all events are filtered and if one matches an Export Profile then the attached Gateway is triggered with the wanted data.
The criteria for a match can be anything found on a shipment. E.g InstallationId, Event Types, or even Shipment specific data
An export can be triggered when an event is added, or at an interval.
Interval is normally used if one needs to summarize information based on the period of the interval. Max 24 hours
- On-premises / Ticket / Shipment Server
Example: Print or Transmit
- Consignor Portal
Events added using the Shipment Viewer
Signature and image can also be exported
ReturnData events like delivered
Files from the customer
Only clear text
If more than 160 characters, it will be handled as an extra SMS
Both FTP and SFTP are supported
Support POST request against a single endpoint
PortalData Export Overview
Only nShift employees can currently create and edit profiles.
How to get started
Submit a request to customer service.
Examples of information the ticket should include:
- Which type of Gateway(s)
- Which event(s) should we trigger an export on
- Example of the template we should create using Email/SMS/File
- Documentation of the API if you want to use the HTTP gateway
An example of a POST request, including headers and the payload