Notifications API · notifications

Send an issued quote to the customer on channel

POST /notifications/quotes

Send an issued quote (orderId) to the customer on channel: by email, rendered through the quote's email template as it stands — the organization's active one, else the chosen style's starter, else Classic — whose id and version (or starter) and layout the notification records as template, with its lines, totals and the date it holds its prices until and replies to the accounts email; by sms, a short text with its number, total and validity — each linking the quote's customer page, where the customer views, accepts or declines it (opening it marks the message opened).

to is the address or number (international form) chosen. The message is built from the quote as issued, never a draft; an email's first open and click are recorded unless tracking is off. Appends notifications.requested, then notifications.sent (with the provider's message id) or notifications.failed (with its reason); while the organization is read-only it is recorded and held, failed with the reason. 400 RecipientInvalid when to does not fit the channel; 409 QuoteNotSendable for an order that is not an issued quote (issue it first: POST /orders/{orderId}/quote on fulfillment); 409 QuotesDisabled when quoteMode is draft-orders; 409 SenderNotConfigured until the sender is saved; for a text, 404 SmsSenderNotFound and 409 SmsNotSendable as for a test; 409 RecipientSuppressed for a suppressed address; 422 TemplateInvalid when the email's template cannot render this quote (nothing is recorded: fix or switch the template); 503 ComposeSourceUnavailable when the quote or the customer cannot be read. Keyed on notificationId, the caller-minted ntf_ id: a retry answers the notification as recorded and never sends a second message.

Access

Requires notifications:write.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

Retries

Keyed on notificationId, the caller-minted ntf_ id: a retry answers the notification as recorded and never sends a second message.

A retry with the same key answers 200, with what the first call recorded.

Why every write carries a key: Idempotency and retries.

Facts appended

  • notifications.requested
  • notifications.sent
  • notifications.failed

What a fact is: Facts and the journal.

AI agent tool

Agents call this as notifications_send_quote (Notifications: Send quote), in the notifications toolset.

Connecting an agent: AI agents.

Example

curl
curl -X POST 'https://notifications.getmanifold.io/notifications/quotes' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "notificationId": "ntf_01a15a4f-2b6d-7e8f-a1b2-c3d4e5f6a7b8",
  "orderId": "ord_01a15a3c-7e21-7c4d-9b0e-5f6a7b8c9d0e",
  "channel": "email",
  "to": "buyer@ridgeline-outdoor.example"
}'
JavaScript (fetch)
const response = await fetch("https://notifications.getmanifold.io/notifications/quotes", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "notificationId": "ntf_01a15a4f-2b6d-7e8f-a1b2-c3d4e5f6a7b8",
    "orderId": "ord_01a15a3c-7e21-7c4d-9b0e-5f6a7b8c9d0e",
    "channel": "email",
    "to": "buyer@ridgeline-outdoor.example"
  }),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();
Request body · application/json
{
  "notificationId": "ntf_01a15a4f-2b6d-7e8f-a1b2-c3d4e5f6a7b8",
  "orderId": "ord_01a15a3c-7e21-7c4d-9b0e-5f6a7b8c9d0e",
  "channel": "email",
  "to": "buyer@ridgeline-outdoor.example"
}
Response · 200 · application/json
{
  "id": "ntf_01a15a4f-2b6d-7e8f-a1b2-c3d4e5f6a7b8",
  "kind": "quote",
  "channel": "email",
  "status": "sent",
  "to": [
    "buyer@ridgeline-outdoor.example"
  ],
  "cc": [],
  "from": "\"Ridgeline Outdoor\" <accounts@ridgeline-outdoor.example>",
  "replyTo": "accounts@ridgeline-outdoor.example",
  "subject": "Quote SO-19203 from Ridgeline Outdoor",
  "source": {
    "kind": "quote",
    "id": "ord_01a15a3c-7e21-7c4d-9b0e-5f6a7b8c9d0e"
  },
  "requestedBy": {
    "_tag": "user",
    "id": "usr_01a15709-7582-7646-b491-261a138f0650"
  },
  "requestedAt": "2026-10-20T05:40:11.000Z",
  "sentAt": "2026-10-20T05:40:12.000Z",
  "providerMessageId": "0108019a2b3c4d5e-01a1587e-cd9b-7f2a-9b3c-4d5e6f7a8b9c-000000",
  "steps": [
    {
      "status": "requested",
      "at": "2026-10-20T05:40:11.000Z"
    },
    {
      "status": "sent",
      "at": "2026-10-20T05:40:12.000Z"
    }
  ],
  "template": {
    "starterId": "quote-classic"
  },
  "tracked": true
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: notifications-manager.openapi.json. Base URL https://notifications.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

400

RefusalWhat it meansWhat to do
RecipientInvalid channel, to, reason to does not fit the channel.Fix the request. Sending it again unchanged gets the same answer.

401

RefusalWhat it meansWhat to do
Unauthorized reason The token is missing, expired or not one Manifold issued.Get a fresh token and send the call again.
TokenAlreadyUsed tokenId A single-use app token was already spent.Mint a new token for this call.

402

RefusalWhat it meansWhat to do
SubscriptionRequired status The organization's subscription has lapsed, so writes are refused.An owner settles billing. Reads still work meanwhile.

403

RefusalWhat it meansWhat to do
TenantRequired userId The token names no organization.Choose the organization, then get a new token.
ScopeRequired required The token's roles do not grant the scope this call needs.Ask an owner or admin for a role that grants it.

404

RefusalWhat it meansWhat to do
SmsSenderNotFound reason No such record in this organization.Check the id in the path or the body.

409

RefusalWhat it meansWhat to do
RecipientSuppressed to, suppressionId, reason The request was refused. reason says why.Nothing changed. Read the record, then decide.
QuoteNotSendable orderId, reason The request was refused. reason says why.Nothing changed. Read the record, then decide.
QuotesDisabled orderId The request was refused, and nothing changed.Nothing changed. Read the record, then decide.
SenderNotConfigured reason The organization has no sender set up for mail.Set up a sending domain first.
SmsNotSendable to, country, reason The request was refused. reason says why.Nothing changed. Read the record, then decide.
MirroredFromSource source This area is fed by your source system until the organization goes live.Make the change in the source system, or go live first.

422

RefusalWhat it meansWhat to do
TemplateInvalid stage, reason, line, column The email's template cannot render this quote (nothing is recorded: fix or switch the template).Fix the request. Sending it again unchanged gets the same answer.

503

RefusalWhat it meansWhat to do
ComposeSourceUnavailable reason The quote or the customer cannot be read.Send the same request again, with the same key.
RequestLogUnavailable tokenId, reason The service could not record the request, so it did nothing.Send the same request again, with the same key.

How refusals work everywhere: Errors.