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

Update per-user channel preferences (email, SMS, push) at /v1/subscriber/{distinct_id}/channel_preference

GET STARTED

Start building with SuprSend API

Explore with Jentic One

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

POST

/v1/subscriber/{distinct_id}/channel_preference

Update a user's per-channel notification preferences

GET

/v1/template

List notification templates

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.

Can I limit what my agent is allowed to do with the SuprSend API?

Yes. Because you self-host Jentic One, your own rules decide which SuprSend operations and credentials the agent can use. SuprSend carries the workspace key in the URL path, such as /{workspace_key}/trigger and /{workspace_key}/broadcast, so a rule can pin the agent to a single workspace and let it only trigger and broadcast there. You choose the exact operations it may call, so subscriber-list writes at /v1/subscriber_list or preference changes at /v1/subscriber/{distinct_id}/channel_preference stay off limits unless you add them.

Hub Suprsend SuprSend API

AI ReadinessNon-Ready (F)37/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticCommunicationsPush NotificationsapiKey26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to send a transactional notification to a single user, Broadcast an announcement to a subscriber list, Add a batch of users to a SuprSend subscriber list, Update a user's email and SMS notification preferences

Not supported: Does not handle CRM, billing, or analytics - use for triggering and managing multi-channel user notifications only.

Jentic publishes the only available OpenAPI specification for SuprSend API, keeping it validated and agent-ready. SuprSend is a multi-channel notification infrastructure for triggering transactional and engagement messages across email, SMS, push, in-app, Slack, and Teams from a single endpoint. The API covers event-based triggers, broadcast workflows, branding, subscriber lists, and per-user notification preferences. Teams use it as a central messaging stack instead of building separate delivery integrations for each channel.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

36%

Example Density

How richly the API is illustrated with examples.

71%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

25%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SuprSend API to your agent

Capabilities

Start building with SuprSend API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hub Suprsend SuprSend API

Jentic AI Readiness Score

SuprSend API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness