SuprSend
SuprSend is a notification infrastructure platform that enables engineering teams to build, manage, and scale multi-channel notifications through a single unified API. It supports delivery across email, SMS, push notifications, in-app inbox, WhatsApp, Slack, and Microsoft Teams without requiring separate integrations for each channel. The platform provides workflow orchestration, template management, user preference management, smart channel routing with vendor fallback, and real-time delivery logs. SuprSend also offers a Management API for programmatic control of workflows and templates, a CLI for asset synchronization, and an MCP server enabling AI agents to interact with notification infrastructure through tool calling.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles SuprSend the way a machine reads it — 72 machine-readable artifacts across 21 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SuprSend scores 54.7/100 (developing), with a separate agent-readiness read of 45/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from SuprSend's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/suprsend/"
title="SuprSend on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/suprsend.svg"
alt="SuprSend Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/suprsend/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/suprsend/"
title="SuprSend on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/suprsend/card.svg"
alt="SuprSend Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile SuprSend
Each block below is one kind of artifact we hold for SuprSend. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SuprSend Management API
The SuprSend Management API provides programmatic control over workspace assets including workflows, templates, and other SuprSend configuration resources. It uses service token...
SuprSend Broadcast API
The Broadcast API from SuprSend — 1 operation(s) for broadcast.
SuprSend Broadcast Run API
The Broadcast Run API from SuprSend — 1 operation(s) for broadcast run.
SuprSend Bulk API
The Bulk API from SuprSend — 3 operation(s) for bulk.
SuprSend Event API
The Event API from SuprSend — 5 operation(s) for event.
SuprSend Message API
The Message API from SuprSend — 1 operation(s) for message.
SuprSend Object API
The Object API from SuprSend — 8 operation(s) for object.
SuprSend Preference Category API
The Preference Category API from SuprSend — 4 operation(s) for preference category.
SuprSend Schema API
The Schema API from SuprSend — 3 operation(s) for schema.
SuprSend Subscriber List API
The Subscriber List API from SuprSend — 11 operation(s) for subscriber list.
SuprSend Template API
The Template API from SuprSend — 12 operation(s) for template.
SuprSend Tenant API
The Tenant API from SuprSend — 7 operation(s) for tenant.
SuprSend Translation API
The Translation API from SuprSend — 5 operation(s) for translation.
SuprSend Trigger API
The Trigger API from SuprSend — 2 operation(s) for trigger.
SuprSend User API
The User API from SuprSend — 9 operation(s) for user.
SuprSend Workflow API
The Workflow API from SuprSend — 4 operation(s) for workflow.
SuprSend Workflow Run API
The Workflow Run API from SuprSend — 1 operation(s) for workflow run.
SuprSend Workspace API
The Workspace API from SuprSend — 1 operation(s) for workspace.
SuprSend Ws Api Key API
The Ws Api Key API from SuprSend — 2 operation(s) for ws api key.
SuprSend Ws Public Key API
The Ws Public Key API from SuprSend — 3 operation(s) for ws public key.
SuprSend Ws Signing Key API
The Ws Signing Key API from SuprSend — 3 operation(s) for ws signing key.
Scroll within the panel for all 21 ·
Postman Collections 20
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
SuprSend Broadcast API
POSTMANSuprSend Broadcast Bulk API
POSTMANSuprSend Broadcast Event API
POSTMANSuprSend Broadcast User API
POSTMANScroll within the panel for all 20 ·
Open Collections 21
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONSuprSend Broadcast API
OPEN COLLECTIONSuprSend Broadcast Broadcast Run API
OPEN COLLECTIONSuprSend Broadcast Bulk API
OPEN COLLECTIONSuprSend Broadcast Event API
OPEN COLLECTIONSuprSend Broadcast Message API
OPEN COLLECTIONSuprSend Broadcast Object API
OPEN COLLECTIONSuprSend Broadcast Preference Category API
OPEN COLLECTIONSuprSend Broadcast Schema API
OPEN COLLECTIONSuprSend Broadcast Subscriber List API
OPEN COLLECTIONSuprSend Broadcast Template API
OPEN COLLECTIONSuprSend Broadcast Tenant API
OPEN COLLECTIONSuprSend Broadcast Translation API
OPEN COLLECTIONSuprSend Broadcast Trigger API
OPEN COLLECTIONSuprSend Broadcast User API
OPEN COLLECTIONSuprSend Broadcast Workflow API
OPEN COLLECTIONSuprSend Broadcast Workflow Run API
OPEN COLLECTIONSuprSend Broadcast Workspace API
OPEN COLLECTIONSuprSend Broadcast Ws Api Key API
OPEN COLLECTIONSuprSend Broadcast Ws Public Key API
OPEN COLLECTIONSuprSend Broadcast Ws Signing Key API
OPEN COLLECTIONScroll within the panel for all 21 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Suprsend Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Suprsend Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Suprsend Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
SuprSend API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
SuprSend API Schemas
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for SuprSend — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/suprsend · machine-readable index on apis.io
This is an independent, third-party profile of SuprSend, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.