Select a licensed customs broker that offers a documented API or EDI integration (many large brokers expose REST APIs or SFTP-based document submission portals); obtain integration credentials from the broker's technology team.
Submit shipment documents (commercial invoice, packing list, bill of lading, certificate of origin) to the broker's document intake API or SFTP endpoint in the agreed format (PDF, EDI, or structured JSON/XML).
Pass the shipment metadata alongside documents: importer of record EIN, HTS classification if pre-determined, declared value, country of origin, incoterms, and any PGA-related product data.
Poll the broker's entry status API or subscribe to status webhooks to track entry lifecycle stages: document receipt, classification review, entry filing, CBP release, and final liquidation.
Automate ISF pre-filing by pushing supplier and cargo data to the broker's ISF submission endpoint at least 24 hours before vessel departure; confirm ISF acknowledgment receipt.
Retrieve the broker's duty and fee invoice via API after entry release; reconcile invoiced amounts against your pre-calculated estimates and post the duty expense to your ERP.
Known gotchas
Customs broker APIs are proprietary and not standardised; each broker integration requires separate discovery, credentialing, and field mapping — budget significant engineering time per broker.
Power of attorney (POA) must be executed and on file with the broker before the broker can file entries on your behalf; the API integration does not substitute for the legal POA requirement.
Submitting documents to the broker API does not guarantee timely entry filing; monitor entry status and set SLA alerts for entries not filed within the agreed processing window to avoid cargo delays.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp