Skip to main content

​
Overview

By default, notifications are triggered for the default tenant (represents your organization). Pass tenant_id in workflow or event calls to apply tenant-specific customizations. When tenant_id is passed:
  • Tenant properties replace variables in templates
  • Per-tenant preferences are applied
  • Tenant-specific vendor routing is used if configured
📘 For entirely different business lines with separate user bases, use different workspaces instead of tenants.

​
Workflow Trigger

curl --request POST \
     --url https://hub.suprsend.com/trigger/ \
     --header 'Authorization: Bearer __api_key__' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{
  "workflow": "_workflow_slug_",
  "recipients": [
    {
      "distinct_id": "0gxxx9f14-xxxx-23c5-1902-xxxcb6912ab09",
      "$email": ["user@example.com"]
    }
  ],
  "data": {},
  "tenant_id": "_tenant_id_",
  "$idempotency_key": "_unique_identifier_"
}'

​
Event Trigger

curl --request POST \
     --url https://hub.suprsend.com/event/ \
     --header 'Authorization: Bearer __api_key__' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{
  "distinct_id": "0fxxx8f74-xxxx-41c5-8752-xxxcb6911fb08",
  "event": "new_user_signup",
  "properties": {},
  "tenant_id": "_tenant_id_"
}'