Hub Suprsend SuprSend API

Name: SuprSend API
Brand: SuprSend API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsPush NotificationsapiKey26 EndpointsREST

For Agents

Trigger multi-channel notifications, manage subscriber lists, brands, and per-channel notification preferences through SuprSend's central event and workflow API.

Install Jentic One Beta

Connect the SuprSend API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SuprSend API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhub.suprsend.com%2Fsuprsend" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhub.suprsend.com%2Fsuprsend" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SuprSend API.

Trigger a notification workflow for one or many users by sending an event payload to /event or /{workspace_key}/trigger

Broadcast a single notification to a subscriber list via /{workspace_key}/broadcast

Manage subscriber lists and version-controlled draft lists through the /v1/subscriber_list endpoints

GET STARTED

Start building with SuprSend API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SuprSend API for, with concrete tasks.

★ Multi-Channel Transactional Notifications

Replace separate SendGrid, Twilio, and FCM integrations by triggering a single SuprSend event that fans out to email, SMS, and push based on the workflow definition. POST to /event with the user's distinct_id and event properties; SuprSend resolves the right channels per user preference and template.

POST to /event with event_name order_shipped and properties for the order ID; SuprSend dispatches email plus SMS based on workflow config.

Broadcast Campaigns to Subscriber Lists

Send a single message to a curated subscriber list - for product announcements, weekly digests, or service alerts. /{workspace_key}/broadcast accepts the list ID and template, and SuprSend handles per-user channel routing and rate-limit-aware delivery.

Call /{workspace_key}/broadcast with list_id beta_users and template weekly_digest_2026_06 to send the digest.

User Preference Management

Honour per-user notification preferences without building a preference centre from scratch. Update channel-level preferences at /v1/subscriber/{distinct_id}/channel_preference and category-level preferences at /v1/subscriber/{distinct_id}/category/{category_slug}; SuprSend filters subsequent sends accordingly.

POST to /v1/subscriber/user_123/channel_preference setting email=true and sms=false for the user.

AI Agent Notification Sending via Jentic

An AI agent that has just completed a task - for example, processed a refund - calls Jentic to find the SuprSend trigger endpoint and notify the customer across whichever channels they prefer, with no per-channel SDK setup.

Search Jentic for trigger a multi-channel notification, load the SuprSend /event operation, and execute with the user distinct_id and event payload.

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for suprsend api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/event

Trigger a notification workflow with an event payload

POST

/{workspace_key}/trigger

Trigger a workflow by workspace key

POST

/{workspace_key}/broadcast

Broadcast a notification to a subscriber list

POST

/v1/subscriber_list

Create a subscriber list

POST

/v1/subscriber_list/{list_id}/subscriber/add

Add subscribers to a list

POST

/v1/subscriber/{distinct_id}/channel_preference

Update a user's per-channel notification preferences

GET

/v1/template

List notification templates

POST

/event

Trigger a notification workflow with an event payload

POST

/{workspace_key}/trigger

Trigger a workflow by workspace key

POST

/{workspace_key}/broadcast

Broadcast a notification to a subscriber list

POST

/v1/subscriber_list

Create a subscriber list

POST

/v1/subscriber_list/{list_id}/subscriber/add

Add subscribers to a list

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring SuprSend by hand means setting up its Authorization header auth, keeping the hub.suprsend.com host straight across event, trigger, and subscriber endpoints, and handling errors yourself. Through Jentic you install once, import the SuprSend API from the API Directory, store the key once, and your agent calls it.

Permission scoping

SuprSend puts the workspace key in the URL path (/{workspace_key}/trigger), so a rule can pin your agent to one workspace: it can trigger and broadcast for that workspace and nothing else. You choose the operations it may call, so subscriber-list writes are not included unless you add them.

Credential isolation

Your SuprSend API and workspace keys are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'trigger a notification' or 'update subscriber preferences', and Jentic returns the matching SuprSend operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SuprSend API through Jentic.

Why is there no official OpenAPI spec for SuprSend API?

SuprSend does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call SuprSend API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the SuprSend API use?

SuprSend uses an API key plus workspace key model. Through Jentic, both are stored encrypted in the vault and injected at execution time so the raw secret never reaches the agent context.

Can I send a notification across email and SMS in a single SuprSend call?

Yes. POST to /event with the user's distinct_id and event properties; the workflow definition in SuprSend fans the event out to whichever channels are configured (email, SMS, push, Slack) according to the user's preferences.

What are the rate limits for the SuprSend API?

Rate limits are workspace and plan-tier specific and not encoded in the spec. Check workspace settings in the SuprSend dashboard or contact SuprSend support before high-volume bulk broadcasts.

How do I manage subscriber preferences through Jentic?

Search Jentic for update notification preferences, load /v1/subscriber/{distinct_id}/channel_preference, and execute with the distinct_id and a body containing email, sms, or push set to true or false.

Does SuprSend support multi-tenant branded notifications?

Yes. Use POST /v1/brand/{brand_id} to create or update a brand, and GET /v1/brand to list them. Workflows and templates can then reference the brand to deliver white-labelled notifications per tenant.

Hub Suprsend SuprSend API

Connect the SuprSend API to your agent

Capabilities

Start building with SuprSend API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs