Topics

Understand grouped notification recipients and the current WorldVisa API surface.

A topic represents a group of subscribers, such as the people following an enquiry or the members of a team. It gives that audience a stable key, while subscribers keep their own profiles and notification preferences.

Topics and subscribers

A subscriber identifies one recipient. A topic identifies a group. A notification still needs a recipient-specific workflow run so that delivery credentials, preferences, and personalized content can be evaluated for each person.

The current WorldVisa API does not expose topic creation or subscription-management endpoints. Do not build an integration against /v2/topics or assume that a Topics page is available. Topic-related types exist in the workflow engine, but they are not a complete public topic-management feature in this deployment.

Send to a group today

Resolve the audience in your backend and pass the subscribers in the trigger request. Use stable subscriber IDs, and include profile fields when you want to create or update a recipient at trigger time.

curl -X POST "${WV_API_URL}/v1/events/trigger" \
  -H "Authorization: ApiKey ${WV_API_KEY}" \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "enquiry-updated",
    "to": [
      { "subscriberId": "staff-123" },
      { "subscriberId": "staff-456" }
    ],
    "payload": { "enquiryId": "enquiry-1001" }
  }'

Only include people who should receive the update. If the person who made the change should not be notified, leave their subscriber ID out of this audience.

Keep audience and delivery separate

Your application decides who belongs in the group. The workflow decides which channels to use and how to format the message. Subscriber preferences still apply unless the workflow is marked critical.

Subscribers

Create and maintain recipient profiles.

Trigger a workflow

Send notifications through the WorldVisa API.