Novu API

Name: Novu API API
Brand: Novu API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsPush NotificationsapiKey102 EndpointsREST

For Agents

Trigger multi-channel notifications (email, SMS, push, in-app, chat), manage subscriber preferences, and orchestrate notification workflows from a single API.

Quickstart

Get started with Novu API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger a multi-channel notification"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Novu API API.

Trigger notifications across email, SMS, push, in-app, and chat channels with a single event call

Define multi-step notification workflows with conditional routing and delay logic

Fan out notifications to subscriber groups via topic-based pub/sub

Track per-subscriber notification preferences and channel opt-in status

GET STARTED

Start building with Novu API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Novu API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Novu API, keeping it validated and agent-ready. Orchestrate multi-channel notifications across email, SMS, push, in-app, and chat from a unified API with 102 endpoints. Define notification workflows with step-based logic, manage subscriber preferences, and route messages through configurable provider integrations. Supports topic-based fan-out, bulk subscriber operations, and per-subscriber channel credential management.

Use Cases

Patterns agents use Novu API API for, with concrete tasks.

★ AI Agent Notification Orchestration

AI agents trigger multi-channel notifications through Jentic by searching for the event trigger operation, loading the schema, and executing with the event name, subscriber ID, and payload. Jentic handles ApiKey injection from the MAXsystem vault. A single POST to /v1/events/trigger delivers the notification across all channels defined in the workflow — email, SMS, push, in-app, and chat — without the agent managing individual provider integrations.

Trigger a notification event named 'order-shipped' for subscriber 'user-123' with payload containing order_id and tracking_url via POST /v1/events/trigger

Subscriber Preference Management

Allow end users to control which notification channels they receive messages on. The API exposes per-subscriber, per-workflow preference endpoints that respect opt-out choices at delivery time. Agents can read and update preferences programmatically, enabling self-service notification settings without building custom preference UIs from scratch.

Retrieve notification preferences for subscriber 'user-456' via GET /v2/subscribers/{subscriberId}/preferences and disable the email channel for the 'marketing-updates' workflow

Topic-Based Fan-Out

Group subscribers into topics and send a single trigger to notify all members simultaneously. Topics support dynamic membership — subscribers can be added or removed at any time. This pattern handles use cases like product update announcements, team notifications, and event alerts without maintaining recipient lists in application code.

Create a topic named 'product-updates' via POST /v2/topics, add 3 subscribers to it, then trigger a broadcast notification to the topic

In-App Notification Feed

Power an in-app notification center by fetching a subscriber's notification feed with read/unread status. The API supports marking individual messages or all messages as read, tracking unseen counts for badge displays, and filtering by notification category. This eliminates the need to build notification storage and retrieval infrastructure.

Fetch the notification feed for subscriber 'user-789' via GET /v1/subscribers/{subscriberId}/notifications/feed and mark all as read via POST /v1/subscribers/{subscriberId}/messages/mark-all

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/v1/events/trigger

Trigger a notification event for one or more subscribers

POST

/v1/events/trigger/broadcast

Broadcast a notification to all subscribers

POST

/v1/events/trigger/bulk

Trigger multiple notification events in a single request

GET

/v2/subscribers/{subscriberId}/preferences

Get subscriber notification preferences

POST

/v2/topics

Create a notification topic for fan-out

GET

/v1/subscribers/{subscriberId}/notifications/feed

Get a subscriber's notification feed

POST

/v2/workflows

Create a notification workflow

GET

/v1/integrations/active

List active notification provider integrations

POST

/v1/events/trigger

Trigger a notification event for one or more subscribers

POST

/v1/events/trigger/broadcast

Broadcast a notification to all subscribers

POST

/v1/events/trigger/bulk

Trigger multiple notification events in a single request

GET

/v2/subscribers/{subscriberId}/preferences

Get subscriber notification preferences

POST

/v2/topics

Create a notification topic for fan-out

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Novu API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive authenticated requests — the raw ApiKey never enters the agent context or logs.

Intent-based discovery

Agents search by intent (e.g., 'trigger a multi-channel notification') and Jentic returns matching Novu operations with input schemas, so the agent can trigger events without navigating 102 endpoints or understanding the workflow system.

Time to first call

Direct Novu integration: 2-3 days for workflow setup, provider configuration, and subscriber management. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

OneSignal API

OneSignal focuses on push notifications and in-app messaging with rich targeting and analytics

Choose OneSignal when the primary channel is mobile push notifications and you need built-in A/B testing and segmentation without managing workflows.

Complementary

Twilio SendGrid Mail API

SendGrid provides dedicated high-volume email delivery that Novu can route through as a provider

Use SendGrid alongside Novu when you need advanced email-specific features like dedicated IPs, email validation, or detailed delivery analytics beyond what Novu's email step provides.

Complementary

Twilio REST API

Twilio provides SMS and voice capabilities that Novu can leverage as delivery providers

Use Twilio alongside Novu when you need direct SMS delivery control, voice calls, or phone number management beyond Novu's SMS workflow step.

Complementary

Pusher API

Pusher provides real-time WebSocket channels for live in-app messaging alongside Novu's notification infrastructure

Use Pusher alongside Novu when you need real-time bidirectional communication (chat, live updates) in addition to one-directional notification delivery.

FAQs

Specific to using Novu API API through Jentic.

Why is there no official OpenAPI spec for Novu API?

Novu does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Novu API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Novu API use?

The Novu API uses API key authentication via the Authorization header with format 'ApiKey <your-secret-key>'. Through Jentic, your Novu API key is stored encrypted in the MAXsystem vault and injected automatically, so agents never handle the raw secret key.

Can I send notifications to multiple channels with a single API call?

Yes. POST to /v1/events/trigger with your event name and subscriber ID. The notification routes through all channels defined in the associated workflow — email, SMS, push, in-app, and chat — based on the subscriber's active integrations and preferences.

What are the rate limits for the Novu API?

Novu enforces rate limits based on your plan tier. The trigger endpoint supports up to 300 events per second on the Business plan. Bulk trigger via POST /v1/events/trigger/bulk accepts up to 100 events per request for higher throughput. The API returns 429 with retry guidance when limits are hit.

How do I trigger a notification through Jentic with the Novu API?

Search for 'trigger a multi-channel notification' in Jentic to find the Novu events trigger endpoint. Load the operation schema, then execute with the event name, subscriberId, and payload object. Install with pip install jentic and use the search-load-execute flow. Jentic injects the ApiKey header automatically.

Does the Novu API support subscriber notification preferences?

Yes. GET /v2/subscribers/{subscriberId}/preferences returns per-workflow channel preferences. PATCH the same endpoint to update preferences. Novu respects these preferences at delivery time — if a subscriber opts out of email for a specific workflow, the notification skips the email step automatically.

Can I use topics for group notifications in Novu?

Yes. Create a topic via POST /v2/topics with a topicKey, then add subscribers via POST /v2/topics/{topicKey}/subscriptions. Trigger a notification to the topic and all subscribed members receive it. Topics support dynamic membership — add or remove subscribers at any time without modifying the trigger logic.