# Create notification

`POST /accounts/{accountID}/invoices/{invoiceID}/notifications`

API version: `v2026.10.00`. Send `X-Moov-Version: v2026.10.00` to get the behavior described here.

> AI agents: search and read all Moov docs with the docs MCP server at https://docs.moov.io/mcp (no API key). Setup: https://docs.moov.io/guides/developer-tools/mcp-ai/docs-mcp/index.md

Create a notification for an invoice, which resends the invoice email to the customer. The required
`channels` body lists the channels to notify on; today only `email` is supported. Returns a 409
if the invoice is not in `unpaid` or `overdue` status, or if the merchant or customer account has no
email set.

The request is all-or-nothing: if any requested channel is rate limited, nothing is sent. Each channel
can be sent at most once every 24 hours, and not within 24 hours of the invoice being sent. A 429
response lists the limited channels with `availableOn` and lists the `availableChannels` that can be
sent in a new request.

To access this endpoint using an [access token](https://docs.moov.io/api/authentication/access-tokens/)
you'll need to specify the `/accounts/{accountID}/invoices.write` scope.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `X-Moov-Version` | header | string |  | Set this header to v2026.10.00 to use the API described in this specification. When omitted, the server defaults to v2024.01.00, the earliest supported version, which may not match the behavior documented here. An unrecognized well-formed version uses the latest supported version that is not newer than the requested version, when one exists. For example, `v2026.08.00` uses `v2026.07.00`. A malformed value, such as `2022`, returns a `404` response. Values: `v2026.10.00`. |
| `accountID` | path | string | Yes |  |
| `invoiceID` | path | string | Yes |  |

## Request body

Content type: `application/json`

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `channels` | array of string | Yes | The channels to send the notification on. Required, must contain at least one channel. Values: `email`. |

## Response 204

The request completed successfully, but there is no content to return.

## Errors

| Status | Meaning |
| --- | --- |
| 400 | The server could not understand the request due to invalid syntax. |
| 401 | The request contained missing or expired authentication. |
| 403 | The user is not authorized to make the request. |
| 404 | The requested resource was not found. |
| 409 | The request conflicted with the current state of the target resource. |
| 422 | The request was well-formed, but the contents failed validation. Check the request for missing or invalid fields. |
| 429 | The request was refused because at least one requested channel is rate limited. No notification was sent. |
| 500 | The request failed due to an unexpected error. |
| 504 | The request failed because a downstream service failed to respond. |

## Examples

### cURL

```bash
curl -X POST "https://api.moov.io/accounts/{accountID}/invoices/{invoiceID}/notifications" \
  -H "Authorization: Bearer {token}" \
  -H "X-Moov-Version: v2026.10.00" \
  -d '{
  "channels": [
    "email"
  ]
}'
```

### Typescript (SDK)

```typescript
import { Moov } from "@moovio/sdk";

const moov = new Moov({
  security: {
    username: "",
    password: "",
  },
});

async function run() {
  const result = await moov.invoices.createInvoiceNotification({
    accountID: "<id>",
    invoiceID: "<id>",
    createInvoiceNotification: {
      channels: [
        "email",
      ],
    },
  });

  console.log(result);
}

run();
```

Full reference with SDK examples in every language: https://docs.moov.io/api/v2026.10.00/money-movement/invoices/create-notification/