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 your Jentic One instance 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.

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

Yes. Because you self-host Jentic One, your own rules decide which Novu operations and credentials the agent may use. Since Novu triggers events from the request body rather than a resource id in the URL path, you scope the agent to just the operations it needs, such as triggering an event with POST /v1/events/trigger and reading a subscriber feed with GET /v1/subscribers/{subscriberId}/notifications/feed. Anything you leave out, like creating workflows via POST /v2/workflows or topics via POST /v2/topics, stays off limits unless you add it.