Manually trigger the dunning ladder

POST 
/billing/dunning/run

Flips issued+past-due invoices to overdue and emits DunningEvents at the 3/7/14/21-day thresholds. Ordinarily runs as a nightly cron; this endpoint is provided for testing and one-off catch-up. Requires the invoice:issue permission.

Request

Responses

200

Summary of overdue and dunned counts.

201

Resource created. Body follows the shared { data, meta } envelope; data is the newly-created resource.

400

The request payload failed validation. error.details lists the offending fields with human-readable messages and the class-validator constraint that fired. Fix the payload and retry — this is not a transient failure.

401

Missing or invalid access token.

403

Caller lacks the required permission.

429

Rate limit exceeded. Global default is 120 requests/minute per IP; auth-flow, OTP, self-registration, WebAuthn, IRA lookup, and public-lead endpoints carry tighter per-endpoint limits. Retry after the delay indicated by the Retry-After header.

Response Headers

Retry-After

Seconds to wait before retrying.

500

Unhandled server error. The response carries a meta.requestId correlator you can hand to platform operations to trace the failure through structured logs and the hash-chained audit trail. Retry with the same Idempotency-Key header if the endpoint accepts idempotency.