Proof of Delivery (POD)

submit proof of delivery details to transportone once the shipment reaches the customer and unloading is complete this helps ensure accurate closure of loads and supports downstream reconciliation such as shortages, damages, and billing completion what is pod? proof of delivery (pod) refers to the confirmation that a shipment was successfully delivered it includes box level information like damages or shortages, total unloaded weight, and optionally, attached pod documents your erp pushes this data to transportone after delivery and unloading are complete at the customer location data flow direction this is a push api your erp sends pod status and supporting details to transportone after the vehicle has been unloaded erp → tms method post prerequisites before using this api, ensure you have a valid access token (generated via the oauth client credentials flow) the x coreos access key and tenantid for constructing the base url a valid indent id and lr number for the delivered shipment base urls and endpoint base urls environment base url sandbox https //{tenantid} sandbox getos1 com production https //{tenantid} logistax io endpoint http post /api/v1/indents/action/actionuploadsupplierpod authentication & headers all requests to transportone must include the following headers required headers http ```http authorization bearer \<access token> x coreos access \<your access key> x coreos tid \<your tenant id> x coreos request id \<uuid> content type application/json following the headers with their description header required description authorization yes bearer token from auth api x coreos access yes access key provided during onboarding x coreos tid yes your assigned tenant id x coreos request id yes unique uuid for request idempotency content type yes must be application/json note note fields marked with an asterisk ( ) must be included in the request https //docs1 getos1 com/authenticate with transportone request payload "dataids" { "indent" "mtpblx", "lr" "3641 mtpblx" }, "data" { "groupbox" { "boxdamaged" 0, "boxshort" 10, "unloadedweight" 100 }, "poddocuments" \[], "ispodlost" false } } field reference true 0,0,178 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type sample success response { "success" true, "message" "pod recorded successfully" } what’s next? once pod is submitted, the load lifecycle is considered complete in tms this data can now be used for final billing validation and transporter payment processing