Contact Increase support to have wire drawdown request origination enabled on your account, as this feature requires explicit enablement and is not available by default
Construct a POST request to the wire drawdown requests endpoint with the required fields: account_id (your Increase account that will receive the funds), amount (in cents), beneficiary_account_number, beneficiary_routing_number, beneficiary_name, beneficiary_address_line1, beneficiary_city, beneficiary_state, and a message_to_recipient describing the purpose of the drawdown
Store the returned Wire Drawdown Request object id; poll the object or listen for the wire_drawdown_request.submitted webhook to confirm the Fedwire message was sent to the counterparty bank
Handle the case where the counterparty bank chooses not to fulfill the drawdown — Increase will emit an inbound_wire_drawdown_request.created webhook when a third party requests a drawdown from your account, which is a separate flow requiring you to decide whether to send a wire in response
Reconcile the incoming wire by matching it against the Wire Drawdown Request id once the counterparty fulfills it and funds land as an inbound wire transfer on your account
Use idempotency keys on all POST requests to prevent duplicate drawdown requests in case of network retries
Known gotchas
Wire drawdown requests are a Fedwire mechanism requiring pre-negotiated relationships with the counterparty — sending a drawdown to a party that has not agreed to honor them will simply result in no response and no funds received, with no error returned by Increase
Increase distinguishes Wire Drawdown Requests (you sending a request to pull funds) from Inbound Wire Drawdown Requests (a third party requesting you send them a wire); confusing the two objects leads to incorrect status handling in your reconciliation logic
Wire drawdown requests cannot be cancelled once submitted to Fedwire; over-drafting the counterparty's account or misrouting the request requires out-of-band coordination directly between banks
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