Confirm you are creating an outgoing manifest to another in-state licensee, since this uses a different endpoint family than incoming shipments from outside the tracked system.
Retrieve valid transfer types and confirm the receiving facility's license number.
Gather the package labels to include on the manifest.
Submit shipper/recipient license numbers, transfer type, transporter and vehicle information, and package labels to the outgoing transfer template endpoint.
Add delivery-level detail (destination sequence, transporter assignment) to the created template before the shipment departs.
Retrieve the manifest document from the transfer manifest endpoint once the template is finalized.
Known gotchas
Endpoints named for external/incoming shipments are for receiving product from outside Metrc's tracked system, not for creating your own outgoing manifest — easy to confuse by name.
Building a full manifest is a multi-step process (template, then deliveries, then transporters and packages), not a single API call.
Walking a transfer's deliveries and packages typically requires one call per object; throttle requests on large transfers to avoid rate limiting.
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?