Asendia Shipping Integration Workflow
A custom Asendia integration can isolate carrier-specific mapping and request handling behind a shared shipment workflow. The API and authentication shown depend on the selected Asendia product, region and account; they should not be treated as a universal connector.
A project workflow may map the approved product and service, validate parcel requirements and prepare sender, receiver and parcel structures before calling the account's supported interface.
For applicable cross-border shipments, customs fields can be mapped before data is serialized into the selected API contract. The SOAP payload below is illustrative and account-specific. The response is then validated and parsed to extract labels and tracking information.
Implementation flow:
Authenticate → map product/service → build parcels and addresses → process customs → build SOAP request → submit → parse response → process labels and tracking.