canonical: https://jentic.com/apis/notify.eu/notify # Notify API Jentic publishes the only available OpenAPI specification for Notify API, keeping it validated and agent-ready. Notify is a European messaging and notification platform that lets B2B and B2C applications send messages to recipients across multiple transport channels behind a single send endpoint. The API exposes a single send-notification operation that takes a payload describing recipient, channel, and content, and routes the notification accordingly. It supports the operational task of issuing transactional notifications without integrating each underlying channel separately. ## For AI agents Send a notification to a recipient over Notify's multi-channel transport with a single POST. ## Scope Does not handle inbound message reception, contact management, or marketing campaigns - use for outbound transactional notifications only. ## Capabilities - Send a transactional notification to a recipient through Notify's transport layer - Specify the channel and payload structure required for the recipient - Authenticate via paired client id and secret key headers for tenant isolation - Trigger notifications from server-side workflows using a single HTTP call - Route notifications without integrating each underlying carrier directly ## Use cases ### Transactional Customer Notifications An e-commerce backend sends order confirmations, shipping updates, and password resets through Notify's single send endpoint, letting Notify route to the correct channel for each recipient. The application calls POST `/notification/send` with payload and channel data and receives an acknowledgement, removing the need to integrate individual channel providers. Example prompt: Send an order-shipped notification to a customer with the order id and tracking link via POST `/notification/send` ### Internal B2B Alerts An operations platform issues alerts to partner contacts when an SLA threshold is crossed. The Notify send endpoint accepts the recipient and content payload and dispatches the alert, so the platform team does not maintain separate carrier integrations for each partner's preferred channel. Example prompt: Send an SLA breach alert to a partner contact with the affected ticket id and breach time ### European Data-Resident Messaging An EU-headquartered application that needs notifications routed through European infrastructure uses Notify because the platform operates in the EU. The single send endpoint and tenant-scoped credentials keep the integration simple while satisfying data-residency expectations for in-region delivery. Example prompt: Send an account-recovery notification to a German customer using EU-based delivery infrastructure ### AI Agent Outbound Notifications An AI agent that handles user requests issues confirmations and updates back to the user through Notify rather than directly integrating a channel SDK. Through Jentic, the agent searches for the send-notification operation, loads the schema, and calls the endpoint as one of its tools whenever it needs to message the user. Example prompt: Send a confirmation notification to the user that their requested action completed, including a deep link to the result ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/notification/send` | Send a notification to a recipient | ## Key resources - **Notifications** — Send a notification to a recipient via the Notify transport layer ## Why Jentic - **Setup:** Wiring Notify by hand means sending both its X-ClientId and X-SecretKey headers on every request to api.notify.eu and managing that pair yourself. Through Jentic you install once, import the Notify API from the API Directory, store both values once, and your agent calls it. - **Permission scoping:** Notify exposes a single send operation that takes the notification in the request body rather than a resource id in the URL path, so scope the agent to that one operation, sending a notification, and nothing else. You choose that set, so no other capability is included unless you add it. - **Credential handling:** Your Notify X-ClientId and X-SecretKey are stored once, encrypted, by your own Jentic One instance and injected at execution time as both headers. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a transactional notification', and Jentic returns the POST `/notification/send` operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio API** — Twilio offers a deeper multi-channel messaging stack but is US-headquartered. - **SendGrid Mail API** — Pair SendGrid for high-volume email with Notify for cross-channel notifications. - **Novu API** — Novu is an open-source notification orchestration layer covering similar multi-channel use cases. ## FAQ ### Why is there no official OpenAPI spec for Notify API? Notify does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Notify API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Notify API use? Notify uses paired API key headers: X-ClientId and X-SecretKey. Both must be provided on each request. Through Jentic, both values are held in the vault and injected at execution time so they never enter the agent's context. ### Can I send a notification with a single API call? Yes. The API exposes one endpoint, POST `/notification/send`, which accepts the recipient and content payload and dispatches the notification through Notify's transport layer. ### What are the rate limits for the Notify API? The OpenAPI spec does not declare explicit rate limits. Notify applies tenant-level limits in production; consult the Notify dashboard for current values and back off on 429 responses. ### How do I send a notification through Jentic? Search Jentic for 'send a notification'. Jentic returns the POST `/notification/send` operation with the input schema, so the agent submits the recipient and payload directly without browsing the Notify docs. ### Is Notify a good fit for EU data-residency requirements? Notify is operated in the EU, which makes it a relevant option for applications that prefer EU-resident notification infrastructure. Confirm specific data-handling commitments with Notify before relying on this for regulated traffic. ### Can I limit what my agent is allowed to do with the Notify API? Yes. The Notify API exposes a single operation, POST `/notification/send`, and because Jentic One is self-hosted you set the rules for which operations your agent may call. You scope the agent to that one send-notification operation and nothing else, so it cannot reach any capability you have not added. Your X-ClientId and X-SecretKey stay under your control and are supplied only when that permitted call runs.