Webhooks

X3D does not send webhooks. There is no field on an order for a callback URL, no page for registering an endpoint, no signing secret issued to API customers, and no code anywhere that posts an event to a customer's server. If you need to know when an order moves, you ask — poll GET /api/print/orders/{code}.

The webhook endpoints in X3D are inbound#

Three paths in this codebase have webhook in their name or their job. All three receive traffic; none send it, and none are addressable by an API customer.

Poll instead#

Poll the code you got back at submission. The response carries status, a human-readable statusLabel, paid, the price, and a tracking object that stays null until the order ships.

CODE=X3D-K7M2QP

while :; do
  BODY=$(curl -sS -H "Authorization: Bearer $X3D_API_KEY" \
    "https://x3dstudios.com/api/print/orders/$CODE")

  STATUS=$(echo "$BODY" | jq -r .status)
  echo "$(date -u +%H:%M) $STATUS"

  case "$STATUS" in
    SHIPPED|DELIVERED|CANCELLED|REJECTED)
      echo "$BODY" | jq -r '.tracking // "no tracking"'
      break
      ;;
  esac

  sleep 300
done

How often to poll#

• Every 5 minutes is a sensible default. Prints run for hours and most transitions are made by a person, so faster polling learns nothing sooner.
• Poll only orders that are still open. Once you see SHIPPED, CANCELLED or REJECTED, stop — nothing further will change that matters to you.
• The status endpoint has no rate limit in the application, so there is nothing to back off from and nothing to catch you either. Be considerate.
• Poll per order. There is no list endpoint on the REST API, so a hundred open orders is a hundred requests — space them out rather than firing them together. The MCP server's list_my_orders tool takes the same key and returns your 20 most recent orders in one call; see /docs/api/mcp.

What arrives without asking#

Email, and nothing else. When an API order is paid, a confirmation goes to every address in the order's email field (the account address unless the request named others, up to five) with the code, a one-line summary, the total charged and the shipping address. After that the same addresses get an email when the order is printed, when it ships (with tracking) and when it is delivered. Printed goes out on its own when the last farm print job for the order completes, and delivered when the daily carrier check sees the parcel arrive; the rest go out when an operator moves the order on. Each address gets its own message, so the people on an order do not see each other's addresses. Accepted and printing send nothing, a correction backwards sends nothing, and nothing is pushed to your systems.