Send-by-tag (hiding PII from public pages)

Some integrations — a booking confirmation page, a returns portal — need to trigger a message without exposing the recipient's phone number or email in the page's own HTML or client-side JavaScript.

The pattern

1. Create a named recipient once: POST /v1/recipients with { tag, channel, recipient }.
2. From your backend, trigger a send by tag instead of by raw address:

curl -X POST https://api.wezend.com/v1/messages/send-by-tag \
  -H "X-API-Key: $WEZEND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "recipient_tag": "booking-42891",
    "subject": "Your booking is confirmed",
    "message": "See you Thursday at 14:00."
  }'

Only the tag ever needs to reach the browser or a third-party page builder — the platform resolves it to the real recipient server-side.

Attachments (email only)

Pass attachment: { filename, content (base64), contentType } to attach inline, or media_url pointing at a file you've already uploaded via Media. Attachments aren't supported on SMS/WhatsApp — include a link in the message text instead.

This endpoint requires an API key (not a dashboard JWT) — it's designed for server-to-server calls.