Pulse API#

Novaza Pulse exposes a REST API for subscribers, lists, templates, campaigns, and transactional email. The API is served by the Pulse product directly at https://pulse.novaza.ai and is not proxied through the Novaza Platform Gateway.

Access and Authentication#

Because the Pulse API is served by the product directly, it has its own authentication handshake that is separate from the Platform Gateway at api.novaza.ai. Clients must obtain a Pulse access token before calling Pulse API endpoints.

  • Base URL: https://pulse.novaza.ai
  • Authentication: OAuth2 Authorization Code flow against Novaza SSO (id.novaza.ai), or a Pulse-issued API token generated in the Pulse admin panel for server-to-server integrations
  • Token header: Authorization: Bearer <access_token>
  • Requires separate auth: a JWT issued for api.novaza.ai cannot be reused here.

See API Authentication for the OAuth2 flow and token exchange details.

What You Can Do#

The Pulse API supports the same actions that are available in the Pulse user interface, including:

  • Managing subscribers, lists, and segments
  • Creating, updating, and launching campaigns
  • Managing templates
  • Sending transactional messages
  • Reading campaign analytics (opens, clicks, bounces, unsubscribes)

API Reference#

For the complete endpoint list, request/response schemas, and parameter documentation, see the Pulse product’s own API reference available from within the Pulse application:

Pulse → Settings → API

The in-product reference is always in sync with the version of Pulse deployed to your workspace.

Backward Desk API Webhooks Forward

© 2026 Novaza. All rights reserved.