Direct Mail API & Automation Platform

Midwest Label Supply offers a direct mail API built for product, growth, and RevOps teams who want to trigger physical mail the same way they trigger email. POST a JSON payload, and within one business day a CASS-verified, IMb-tracked piece is in the mail stream — with delivery webhooks coming back to your stack. We print postcards, letters, and a category most API-first competitors don't touch: custom sticker sheets and explainer cards in envelopes.

This page is for teams evaluating a direct mail service with API integration. If you're comparing us against Lob, PostGrid, Postalytics, or PFL — keep reading.

What a Direct Mail API Actually Does

A direct mail API is the developer-facing layer over a physical print operation. Your software calls a REST endpoint with a recipient address, a template ID, and any variable data, and the provider handles everything downstream: rendering, CASS address verification, print, finishing, sorting, IMb application, USPS handoff, and webhook event emission. The end state is the same as sending a transactional email — except the recipient gets a physical piece they can hold, save, and respond to. That tactile interaction is why direct mail keeps showing higher recall and response rates than oversaturated digital channels.

Direct Mail API Comparison: How We Stack Up

The US market for API-driven direct mail has a few well-known providers. Each has a sweet spot:

• Lob — The largest aggregator. Strong API, huge customer base, but they don't own the press, which can show up as longer turnaround on non-standard products.
• PostGrid — No-code address verification and zero-code workflows. Good for marketers who don't want engineering involvement.
• Postalytics — Best for marketing automation handoffs between email and direct mail. Tight HubSpot and Marketo plays.
• PFL — Pioneer of "Tactile Marketing Automation" for enterprise ABM. Premium pricing, premium account management.
• Midwest Label Supply — We own the print operation. Lower per-piece cost at volume, deeper custom product range (sticker sheets, kit assembly, dimensional packages), no monthly minimum. Best fit when you want one accountable partner for both software and production.

REST API Architecture

Our API follows REST conventions with JSON request and response bodies. Authentication uses API keys with separate test and live environments. Every endpoint supports idempotency keys, so you can safely retry on network failures without duplicate sends. The base implementation for a single piece looks like this:

// POST /v1/mailings
const mailing = await mlsClient.mailings.create({
  to: {
    name: "Jordan Recipient",
    address_line1: "123 Main Street",
    address_city: "Milwaukee",
    address_state: "WI",
    address_zip: "53202"
  },
  from: {
    name: "Acme Inc.",
    address_line1: "456 Market Street",
    address_city: "Chicago",
    address_state: "IL",
    address_zip: "60601"
  },
  template_id: "tpl_welcome_kit_v3",
  variables: {
    first_name: "Jordan",
    referral_code: "JORDAN-7821",
    qr_url: "https://acme.com/welcome/cust_123456"
  },
  metadata: {
    campaign_id: "spring_promotion_2026",
    customer_id: "cust_123456"
  }
}, { idempotency_key: "cust_123456:welcome:v3" });
							

Same request via cURL:

curl https://api.midwestlabelsupply.com/v1/mailings \
  -H "Authorization: Bearer $MLS_API_KEY" \
  -H "Idempotency-Key: cust_123456:welcome:v3" \
  -H "Content-Type: application/json" \
  -d '{
    "to": { "name": "Jordan Recipient", "address_line1": "123 Main Street", "address_city": "Milwaukee", "address_state": "WI", "address_zip": "53202" },
    "from": { "name": "Acme Inc.", "address_line1": "456 Market Street", "address_city": "Chicago", "address_state": "IL", "address_zip": "60601" },
    "template_id": "tpl_welcome_kit_v3",
    "variables": { "first_name": "Jordan", "referral_code": "JORDAN-7821" }
  }'
							

Webhook Event Reference

Every mail piece emits a stream of events to your registered webhook endpoint. Webhooks are signed (HMAC-SHA256) and retried with exponential backoff for 24 hours on non-2xx responses. The full event sequence:

• mailing.created — Request accepted, ID issued, address validated.
• mailing.rendered — Template merged with variable data, PDF generated and stored.
• mailing.in_production — Piece is on press or in finishing.
• mailing.mailed — Piece has been inducted into the USPS mail stream.
• mailing.in_transit — First IMb scan recorded.
• mailing.in_local_area — Piece has reached the recipient's destination facility.
• mailing.processed_for_delivery — Out for delivery on the carrier route.
• mailing.delivered — Final delivery scan confirmed.
• mailing.returned — Piece returned to sender (bad address, refused, vacant).
• mailing.scanned — Optional: QR code on the piece was scanned by recipient. Includes device, geo, timestamp.

Each event payload includes the mailing ID, USPS IMb, the timestamp, the USPS facility (when known), and your original metadata blob — so you can correlate every event back to the customer record that triggered the send.

USPS Informed Visibility & Real-Time Tracking

We participate in USPS Informed Visibility (IV), which streams IMb scan events from every processing facility in the country. IV is "near real time" — most scans appear within 1–4 hours of the physical event. That's typically fast enough to trigger same-day digital follow-ups when a piece is marked processed for delivery. For deeper detail on tracking architecture, see our direct mail tracking page.

Two layers of tracking are available and are usually combined:

1. USPS IMb tracking — Tells you where the physical piece is in the mail stream. Coverage on over 99% of pieces.
2. QR code response tracking — Tells you who actually engaged. Variable QR codes printed at piece level link recipient scans back to your CRM via a redirect-and-log endpoint we host (or yours).

Address Verification, Personalization & A/B Testing

Every request runs through CASS-certified address validation before going to production. Invalid addresses fail fast with a structured error code — you never get charged for a piece that wouldn't have delivered. Personalization goes beyond name fields: image swaps, offer codes, dynamic copy blocks, and full design variations are first-class fields in the template definition. A/B testing primitives are built in — split a single campaign across two or more template variants and we'll return performance metrics correlated to delivery and QR-scan events.

Integration With Your Existing Stack

You can wire our direct mail API into your stack three ways:

• Native REST API — For engineering teams building transactional or product-driven mail (welcome kits, renewal reminders, dunning).
• Zapier & Make — For business teams who want to wire direct mail into existing workflows without code. Connects to 1,600+ apps.
• Direct platform integrations — Salesforce, HubSpot, Marketo, Customer.io, Braze, Iterable, Outreach, and SalesLoft each get a native action that drops mail into your existing journey.

Use Cases We See Most

The patterns that drive the highest ROI on our API:

Welcome Kits & Onboarding

Trigger a printed welcome packet with a custom sticker sheet on account activation. Subscription, fintech, and DTC brands see 25–30% retention improvements when physical onboarding is added to digital. The API call lives in your existing post-signup workflow.

Re-engagement & Win-back

Send a physical postcard to customers who've gone quiet — especially those who've unsubscribed from email. A/B test offer strength against a holdout group and let the API report back the ROI.

B2B ABM & Sales Trigger Mail

RevOps teams use the API to trigger printed packages off Salesforce stage changes, 6sense / Bombora intent signals, or executive engagement scoring. Pair with Outreach or SalesLoft to land a printed piece the same week as a personalized sequence.

E-commerce Thank-You & Loyalty

Wire a thank-you postcard with a sticker sheet to your Shopify or BigCommerce order webhook. Loyalty tier milestones can trigger different SKUs of physical reward through the same endpoint.

White-Label Direct Mail for Agencies

Agencies and martech platforms resell the API under their own brand with neutral packaging and a per-client partner dashboard. We handle production; you keep the customer relationship.

Pricing & Minimums

Per-piece pricing with no monthly minimum. Pilot programs from 1,000 pieces. Volume tiers kick in at 10K, 50K, and 250K pieces per month. Postage is passed through at USPS rates — we apply for every Marketing Mail and bulk discount you qualify for so the all-in cost is competitive with any aggregator at scale.

How to Get Started

Email or call to provision a sandbox API key. From key issuance to first piece printed is typically 3–5 business days, including template setup. If you're switching from Lob, PostGrid, Postalytics, or PFL, send us your existing template — we'll match it and run a parallel test send before you cut over.

Related Direct Mail & API Pages