Skip to content

Tag Routes

Route inbound email by tag to custom processing handlers.

Every domain receives operational email that usually goes unread: abuse reports from other mail servers, postmaster delivery failure notices, security vulnerability disclosures, billing alerts from SaaS providers, and compliance notifications. Most teams either ignore these addresses entirely or forward them to a shared inbox where they disappear. But this email contains valuable signals: an abuse report might indicate a compromised account, a postmaster notice might explain why a customer's password reset never arrived, and a spike in security disclosures might mean a vulnerability was published.

Tag routes let you process this email programmatically. When you forward operational email to Bounce House, the tag in the address (the part after the +) determines what happens: store it for querying via the API, extract structured content like OTP codes or links, push the payload to a webhook in real time, or apply conditional rules that alert you on keyword matches or frequency spikes. You can also BCC your outgoing transactional email to a tagged address to build a complete record of what you sent and correlate it with bounce and delivery events.

Handlers

HandlerBehavior
storeStore the message and make it queryable via the messages API
extractExtract structured content (OTPs, links, specific fields)
webhookPush the message payload to an external URL on arrival
rulesApply conditional rules (keyword matching, sender filtering, frequency alerting)

Handlers can be combined — a single tag route can store, extract, and push to a webhook.

Create a tag route

curl -X POST https://api.bouncehouse.cloud/api/accounts/me/tag-routes \
  -H "Authorization: Bearer bh_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "tag": "security",
    "handler": "webhook",
    "config": {
      "url": "https://your-app.com/webhooks/security-reports",
      "extract_links": true
    }
  }'

Returns {id, tag, handler, config, created_at}.

List tag routes

curl https://api.bouncehouse.cloud/api/accounts/me/tag-routes \
  -H "Authorization: Bearer bh_your_key"

Update a tag route

curl -X PUT https://api.bouncehouse.cloud/api/accounts/me/tag-routes/{route_id} \
  -H "Authorization: Bearer bh_your_key" \
  -H "Content-Type: application/json" \
  -d '{"handler": "store", "config": {"retention_days": 90}}'

Delete a tag route

curl -X DELETE https://api.bouncehouse.cloud/api/accounts/me/tag-routes/{route_id} \
  -H "Authorization: Bearer bh_your_key"

Examples

Monitor abuse reports:

abuse@example.com → example-com_abuse_{hmac}@{account-name}.{shard}-bo.ing-bo.ing

Built-in handler. Stores reports, extracts sender info, alerts on frequency spikes.

Collect security disclosures:

security@example.com → example-com_security_{hmac}@{account-name}.{shard}-bo.ing-bo.ing

Tag route with webhook handler pushes to your security team's Slack integration.

Track outgoing transactional email via BCC:

BCC: {id}+txn@shard-bo.ing-bo.ing

Tag route with store + extract captures what was sent, extracts OTPs and links, and correlates with bounce/delivery events.

Was this page helpful?