> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alforse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Collections

> Work overdue and upcoming receivables, and send reminders through configured channels.

## List collections

`GET /collections` · requires `collection` (view)

<ParamField query="tab" type="string" default="overdue">`overdue` | `soon` | `all`</ParamField>

<ParamField query="page" type="integer" default="1" />

<ParamField query="pageSize" type="integer" default="20">Max 200.</ParamField>

<ParamField query="subjectId" type="string" />

## Preview a reminder

`GET /collections/preview` · requires `collection` (view)

<ParamField query="contractId" type="string" required />

<ParamField query="paymentId" type="string" required />

<ParamField query="channelId" type="string">Defaults to the tenant's default channel.</ParamField>

Renders what a reminder would contain without sending it.

## Send a reminder

`POST /collections/remind` · requires `collection` (edit)

<ParamField body="contractId" type="string" required />

<ParamField body="paymentId" type="string" required />

<ParamField body="channelId" type="string" />

## Send reminders in bulk

`POST /collections/remind-bulk` · requires `collection` (edit)

<ParamField body="channelId" type="string" />

<ParamField body="tab" type="string" default="overdue">`overdue` | `soon` | `all`</ParamField>

<ParamField body="subjectId" type="string" />

Sends a reminder for every payment matching the given tab (and subject, if provided).

## Run due reminders now

`POST /collections/run-due-reminders` · requires `collection` (edit)

No body. Triggers the same reminder sweep that runs on a schedule, on demand — useful after
changing notification channel configuration and wanting to confirm it immediately, rather than
waiting for the next scheduled run.

See [Tenant Administration](/guides/tenant-administration) for configuring notification
channels, and [Collections](/guides/collections) for the product-level walkthrough.
