notification.resend

Send a message that was already sent, again — repeating the SNAPSHOT that was recorded, never re-rendering today’s template, so the customer receives the sentence they are asking about. The delivery happens just after this command commits (it rides the outbox, so it retries and leaves a trail); a NEW record is written and linked back to the original, because the trail has to be able to say the customer received it twice. Refused for a record whose body was never persisted — an authentication code is not repeatable by design.

• Scope: order.write
• System: no
• Reachable from: POST /v1/commands/notification.resend (tenant credential) · MCP tool notification.resend · SDK client.call('notification.resend', …)
• Events: notification.resend_requested

Input (JSON Schema)

{
  "properties": {
    "notification_id": {
      "minLength": 1,
      "type": "string"
    }
  },
  "required": [
    "notification_id"
  ],
  "type": "object"
}

Result (200)

{
  "additionalProperties": false,
  "properties": {
    "channel_key": {
      "type": "string"
    },
    "notification_id": {
      "type": "string"
    },
    "requested": {
      "type": "boolean"
    },
    "type_key": {
      "type": "string"
    }
  },
  "required": [
    "notification_id",
    "type_key",
    "channel_key",
    "requested"
  ],
  "type": "object"
}

Errors

validation_failed (400) · unauthorized (401) · forbidden (403) · conflict (409) · internal (500)