Get your FTD Mercury HQ orders through an API

What you can build on Mercury HQ

• Get incoming wire orders

  Build this

  Reads the orders on the Orders tab of Mercury HQ for a delivery date range, with the sending florist and when each order was received.

  Takes

  Delivery date from, delivery date to (optional)

  Returns

  Order number, sending florist, received at, delivery date, recipient, delivery address, product, price, flagged

• List orders without a delivery confirmation

  Build this

  Reads the orders due on one delivery date and checks each order's Order Journey for a delivery confirmation.

  Takes

  Delivery date

  Returns

  Order number, sending florist, recipient, delivery address, delivery date, confirmed (yes or no)

• Get the Order Summary Report

  Build this

  Reads the Order Summary Report in Mercury HQ's reports for a date range: order volume, sales value and average order value.

  Takes

  Start date, end date

  Returns

  Date range, order count, sales value, average order value

• Confirm a delivery

  Build this

  Opens an order on the Orders tab, selects Confirm Delivery in the actions drop down, fills in the delivery information and a note for the sending florist, and confirms.

  Takes

  Order number, delivered at, received by, note for the sending florist

  Returns

  Order number, confirmed at, status

Automate Mercury HQ with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• New wire orders, inside the two-hour reject window

  Build this

  Starts

  Every 15 minutes

  Step 1

  Get the incoming wire orders for today onward.

  Step 2

  Keep the orders that were not there on the last run.

  Step 3

  Post each one, with sending florist, received at, delivery date and product, to your Slack webhook.

• Orders still undelivered before the 7:00 pm cut-off

  Build this

  Starts

  Every day at 4:30 pm in your shop's time zone

  Step 1

  List today's orders and check each one for a delivery confirmation.

  Step 2

  Keep the orders with no delivery confirmation, and stop if there are none.

  Step 3

  Email you the list with recipient, address and sending florist.

• Weekly order summary for your bookkeeper

  Build this

  Starts

  Every Monday at 8:00 am

  Step 1

  Get the Order Summary Report for the previous Monday to Sunday.

  Step 2

  Compare it with the week before.

  Step 3

  Post order count, sales value and average order value to your accounting webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get incoming wire orders” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "mercuryhq.com/get_incoming_orders",
    "input": {
      "delivery_date_from": "2026-11-13",
      "delivery_date_to": "2026-11-14"
    }
  }'

{
  "status": "completed",
  "data": {
    "orders": [
      {
        "order_number": "M4821-7",
        "sending_florist": "Northwind Flowers",
        "received_at": "2026-11-12T09:42:00-06:00",
        "delivery_date": "2026-11-13",
        "recipient": "Northwind Traders, reception",
        "delivery_address": "118 Maple Ave, Springfield, IL 62704",
        "product": "Birthday mixed bouquet, deluxe",
        "price": 84.99,
        "flagged": false
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

Mercury HQ’s own options

FTD's pages for Mercury HQ describe no developer API for member florists. What they list are built-in connections in the Essentials edition: incoming Teleflora and BloomNet orders, web orders from third-party e-commerce sites, a QuickBooks Online integration and customer data export. Everything else is the Mercury HQ site and its mobile app.

Read on November 12, 2026: Mercury HQ feature comparison, Summer 2026, Mercury HQ on FTDi.com.

Signing in to Mercury HQ

Mercury HQ signs you in at mercuryhq.com with your email and password, and staff get their own user profiles with permissions set by role. With Fous you sign in once through Mercury HQ's own sign-in with your own account: the login is sealed with AES-256 and never shown to your code or AI agents, and an expired session is signed back in.

Worth knowing

Two hours to reject a wire order

Under FTD's Delayed Response Policy a filling florist must reject an order within two business hours of receiving it. Later rejections cost $10, $20, the order's value or twice its value, credited to the sending florist.

Delivery confirmation by 7:00 pm

Every FTD order should be delivery confirmed by 7:00 pm local time on the delivery date. FTD charges $2.25 per order missed, and another $10.00 when no confirmation is sent within 48 hours.

Date changes go through Ask and Answer

To move a delivery date, the florists exchange an Ask and an Answer message, and the delivery date field must also be changed. The Delayed Response Policy still runs while you wait for an answer.

Your edition decides what you see

Mercury HQ comes in Core and Essentials. Both have the Order Summary Report and Network Scorecard; the Sales Summary, Business Snapshot, Aged Analysis and other reports are in Essentials.

More in Distribution: specialty wholesale and B2B marketplaces

• Tradeplace
• Alibaba.com supplier back end
• IndiaMART Seller Panel
• JOOR
• NuORDER
• Trek B2B
• Ingram iPage
• 1688
• Covetrus
• MWI Animal Health
• Patterson Veterinary
• SanMar
• Faire

Other industries: 千牛卖家中心, VA Enrollment Manager, PSE&G My Account, foodpanda Partner Portal, BBVA Net Cash México, Moneris Merchant Direct.