Notify API
★ Only Publicly Available OpenAPI DocumentCommunicationsPush NotificationsapiKey1 EndpointsREST
For Agents
Send a notification to a recipient over Notify's multi-channel transport with a single POST.
Use for: I want to send a transactional notification to a customer, Trigger a notification from a workflow when an order ships, Send a B2B alert to a partner contact, Issue an account notification to a user
Not supported: Does not handle inbound message reception, contact management, or marketing campaigns — use for outbound transactional notifications only.
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.
Install Jentic One Beta
Connect the Notify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Notify API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Notify API.
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
Patterns agents use Notify API for, with concrete tasks.
★ 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.
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.
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.
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.
Send a confirmation notification to the user that their requested action completed, including a deep link to the result
Key Endpoints
1 endpoints — jentic publishes the only available openapi specification for notify api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/notification/send
Send a notification to a recipient
POST
/notification/send
Send a notification to a recipient
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Notify X-ClientId and X-SecretKey pairs are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw secret key never enters the agent's prompt or context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'send a notification') and Jentic returns the POST /notification/send operation with its input schema attached.
Time to first call
Direct Notify integration: a couple of hours for auth and payload shaping. Through Jentic: minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Notify API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED