Generate a FedEx Electronic Trade Document (ETD) commercial invoice for an international shipment via the FedEx Ship REST API
domain: developer.fedex.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth 2.0 token from https://apis.fedex.com/oauth/token
POST to /ship/v1/shipments including the 'customsClearanceDetail' object with commodities, currency, customsValue, and 'dutiesPayment' info; set 'shippingDocumentTypes' to include 'COMMERCIAL_INVOICE'
In the request, set 'electronicTradeDocuments' to indicate ETD submission so FedEx electronically files the commercial invoice with customs rather than requiring paper copies
Use the Trade Documents Upload API (/documents/v1/etds/upload) if pre-uploading a custom invoice PDF or company letterhead image for countries requiring a signed document
Check the FedEx country list for ETD eligibility before assuming paperless clearance — unsupported country pairs return an EWO (Electronics with Originals) flag requiring printed copies to accompany the shipment
Known gotchas
Not all origin/destination country pairs accept ETD; the shipment response will include 'EWO' in shippingDocumentDetails if paper originals are still required alongside the electronic submission
Commodity HS codes and accurate declared values are required; incorrect values cause customs holds — do not use placeholder values in production
The Trade Documents Upload endpoint is separate from the Ship endpoint; upload supplementary documents before confirming the shipment so they are linked to the correct tracking number
Give your agent this knowledge — and 15,500+ 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?