# Approve filings in bulk

> POST /filings/bulk/approve

Source: https://docs.trykintsugi.com/reference/2026-07-21/approve-filings-in-bulk

POST /filings/bulk/approve

Approve filings in bulk

Approve several filings in one organization. Requires an ADMIN or OWNER credential; send an `Organization-Id`, `Connection-Id` or `Entity-Id` selector to say which organization they belong to. Returns 200 with a per-filing `successful`/`failed` breakdown even when some filings cannot be approved (unknown id, not an approvable status, or a disabled jurisdiction). Approving BACK_FILING rows with published terms requires `backFilingTermsId`. Returns 403 PLAN_UPGRADE_REQUIRED when the organization is on a free plan, and 403 FORBIDDEN when the organization's plan does not include managed filings.

Category: Filings

Request body:
filingIds (string[], required) - Ids of the filings to approve. Duplicates are ignored.
backFilingTermsId (string) - Id of the back-filing terms version accepted for any BACK_FILING.
backFilingTermsAcceptedAt (string) - When the customer accepted the back-filing terms (advisory).
requestId (string) - Client-minted id for this confirm attempt, stored on the audit row.

Response fields:
successful (string[], required) - Filing ids acted on, or accepted for a worker when queued.
failed (BulkFilingFailure[], required) - Requested filings that were not acted on, each with a reason.
  id (string, required) - Id of the filing that was not acted on.
  reason (string, required) - Why this filing was not acted on.
queued (boolean) - Whether the batch was enqueued for a worker rather than applied inline.
jobId (string) - Reserved for a pollable job handle; null until a job surface exists.

Response statuses: 200, 400, 401, 403, 404, 409, 422

---

Index of every page: https://docs.trykintsugi.com/llms.txt