Retrieve a signed proof of delivery (POD) document from FedEx via the API after a shipment is delivered
domain: developer.fedex.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth 2.0 bearer token via the FedEx authentication endpoint using your app's client_id and client_secret
Call the FedEx Track API GET /track/v1/trackingdocuments with the tracking number and documentType set to SIGNATURE_PROOF_OF_DELIVERY
Check the trackingDocuments array in the response for a document object; the encoded document is returned as a base64-encoded PDF or image
Decode the base64 string and store the POD document in your document management system linked to the shipment record
Verify that the deliveredDateTime and signedByName fields in the track response match expected delivery confirmation data
Automate POD retrieval by triggering it when a delivery-confirmed webhook event is received rather than polling; this reduces unnecessary API calls
Known gotchas
POD documents are not immediately available at the moment of delivery confirmation; FedEx requires up to several hours after the delivery scan for the signature image to be accessible via API
Not all FedEx service types capture a physical signature; FedEx Home Delivery and SmartPost/Ground Economy may return a delivery confirmation without a signature image
The SIGNATURE_PROOF_OF_DELIVERY document type requires that the shipment was sent with Signature Required or Adult Signature Required special handling; standard deliveries may only return a delivery confirmation letter
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?