---
{
  "id": "platform.delivery.overview",
  "topic": "delivery",
  "title": "Outbound Delivery overview",
  "locale": "en",
  "version": "2026-08-09.1",
  "summary": "Delivery is outbound-only and asynchronously queues an event plus JSON payload for an owner-registered active endpoint.",
  "content": "Delivery is outbound-only: it sends an event name plus JSON payload to an endpoint that the owner registered in Office > Outgoing Deliveries. `arinova.delivery.list_endpoints` returns only safe metadata for explicitly granted endpoints—ID, name, kind, and status—and intentionally omits target URLs and secrets. `arinova.delivery.send` requires a `write` grant and enqueues work on the durable delivery queue. Existing endpoints were pre-granted only to active external Agents during migration; platform Agents received zero grants, and new endpoints are not shared until the owner grants access in Office. An empty list can therefore mean “no grants,” not “no endpoints.” An endpoint must already exist and be `active`. Creating, verifying, enabling, rotating, disabling, or deleting endpoints is a human Office operation; the Agent has no action for it.\n\nA successful send returns `deliveryId` and `status=queued`. That means Arinova accepted the job, not that the receiver got it. The durable worker determines the final status, and the owner can inspect per-delivery history in Office. Enqueue success charges the owner's configured Arinova credit. A rate-limit rejection creates no delivery and no charge. Always prefer the current action result and persisted history over a static explanation.\n\nDirection is the key routing boundary: Webhook is external-to-Arinova inbound traffic; Delivery is Arinova-to-external outbound traffic; Trigger reacts to platform resource events; Email receives mail and can only reply. A Workflow `notify` step writes to the owner's internal Notification Center and is never Delivery. A request about receiving a delivery, receiving a webhook, or an external event coming in does not belong to Delivery. Office Agents may receive an endpoint as collaboration context, including a terminal endpoint for explaining history, but sending still requires an active endpoint and a write grant.\n",
  "aliases": [
    "outbound delivery",
    "delivery endpoint",
    "send to our system",
    "external endpoint",
    "push result outside",
    "對外傳送",
    "外部端點",
    "送到我們的系統"
  ],
  "tags": [
    "delivery",
    "overview",
    "outbound"
  ],
  "relatedActions": [
    "arinova.delivery.list_endpoints",
    "arinova.delivery.send"
  ],
  "relatedActionPrefixes": [],
  "url": "https://docs.arinova.ai/en/kb/delivery/overview/"
}
---

Delivery is outbound-only: it sends an event name plus JSON payload to an endpoint that the owner registered in Office > Outgoing Deliveries. `arinova.delivery.list_endpoints` returns only safe metadata for explicitly granted endpoints—ID, name, kind, and status—and intentionally omits target URLs and secrets. `arinova.delivery.send` requires a `write` grant and enqueues work on the durable delivery queue. Existing endpoints were pre-granted only to active external Agents during migration; platform Agents received zero grants, and new endpoints are not shared until the owner grants access in Office. An empty list can therefore mean “no grants,” not “no endpoints.” An endpoint must already exist and be `active`. Creating, verifying, enabling, rotating, disabling, or deleting endpoints is a human Office operation; the Agent has no action for it.

A successful send returns `deliveryId` and `status=queued`. That means Arinova accepted the job, not that the receiver got it. The durable worker determines the final status, and the owner can inspect per-delivery history in Office. Enqueue success charges the owner's configured Arinova credit. A rate-limit rejection creates no delivery and no charge. Always prefer the current action result and persisted history over a static explanation.

Direction is the key routing boundary: Webhook is external-to-Arinova inbound traffic; Delivery is Arinova-to-external outbound traffic; Trigger reacts to platform resource events; Email receives mail and can only reply. A Workflow `notify` step writes to the owner's internal Notification Center and is never Delivery. A request about receiving a delivery, receiving a webhook, or an external event coming in does not belong to Delivery. Office Agents may receive an endpoint as collaboration context, including a terminal endpoint for explaining history, but sending still requires an active endpoint and a write grant.