Available now

PLATFORMSeven products, one workspaceOne account and one API key for all seven.See the lineup
Notify docs · Preview

Notify.

One call notifies a user on every channel they use.

Your backend sends invoice.paid to user_123. Notify puts it in their in-app inbox, pushes it to their phone and browser, emails it if they never saw it, and respects what they turned off and when they sleep. You get the record of what happened to every message, and a reason with a fix when something did not go out.

Notify is free during the preview, with no SLA. It is hosted in the EU (DigitalOcean, Frankfurt, fra1).

Get startedComing from Knock, Courier, OneSignal or Novu?

Browse

What you’ll find here

Getting started

Turn Notify on, create a notification type, send it to a user and read it back from their inbox. About ten minutes, no devices needed.
Read more

Core concepts

Recipients, categories, notification types, channels and routing, notifications and deliveries, preferences, quiet hours, scheduling, tenants.
Read more

Guides

Nineteen walkthroughs: Node and other backends, React and Next.js, web push, iOS and Android, React Native, email, webhooks, testing, erasure and migrating.
Read more

Why didn’t it arrive?

Every reason a delivery can be skipped, held or failed, what it means and how to fix it. The same text the console and the MCP tools show.
Read more

Limits and retention

Preview limits per workspace and per recipient, payload sizes, rate limits with Retry-After, and how long each record is kept.
Read more

API reference

Every endpoint, management and client, generated from the live OpenAPI spec, with a Node tab per operation.
Read more

Channels

Five channels, one call

A notification type decides which channels a message uses and in what order. Each recipient’s preferences decide the rest.

Notify channels and what each needs from you
ChannelWhat you needNotes
In-app inboxNothingAlways on. Unread counts, real-time updates, a React component and a framework-free client.
EmailA verified sender in ProductCraft MailSent through Mail: its templates, suppression list and sender reputation.
Web pushNothingNotify generates the VAPID keys. Chrome, Edge, Firefox, Safari on macOS, and installed web apps on iOS 16.4+.
iOS push (APNs)An APNs key (.p8) from your Apple Developer accountUpload it once: encrypted, never shown again.
Android push (FCM)A Firebase project and a service-account keyUpload it once: encrypted, never shown again.

A push counts as sent when Apple, Google or the browser’s push service accepts it. None of them tells anyone whether it was shown or seen, so Notify never claims “delivered” for push. The inbox knows when an item is read, and Mail reports delivered, bounced and complained for email. SMS and Slack are planned after the preview.

Reference

Base URL and credentials

Two kinds of call, two kinds of credential. Your server uses a workspace API key; browsers and apps use a short-lived recipient token your server mints. No secret ever ships in an app.

base URLs
https://api.notify.productcraft.co/v1/workspaces/{workspace_id}/…   your server, workspace API key
https://api.notify.productcraft.co/v1/client/…                        browsers and apps, recipient token

Before the first call, turn Notify on for the workspace in the console (Workspace › Services); until then the API answers 403 SERVICE_NOT_ENABLED. The limits page lists the preview limits.