Cancel a filing
⚠️ Early access — This endpoint is in preview and may change in backwards-incompatible ways before it is marked stable. Avoid depending on it in production, and reach out before building on it.
Cancel a filing before processing begins.
When it succeeds. The filing must still be in a pre-processing status (queued or ready_to_file). It moves to the terminal canceled status, a filing.canceled webhook fires, and the response returns the filing with canceled_at and status_reason set.
When it fails. Once the filing has entered processing (or finished), cancellation returns a 409 filing_not_cancellable problem whose current_status member carries the filing status the decision was made against. There is no dry-run check — call cancel and read the response. A rejected attempt on an in-progress filing is still surfaced to the operations team working it, so they know you asked before anything is finalized with the state.
Related filings. Each filing is evaluated on its own status. Cancelling a formation that is still pre-processing also cancels its pre-processing related filings (an EIN cannot exist without the entity); each cancelled filing sends its own filing.canceled webhook. The reverse never applies: a related EIN filing can be cancelled independently — including after its formation has completed — without touching the formation.
Fees. Cancellation has no billing side effects. Palm fees are only charged on completion, and government fees ride on the filing that incurred them.
Authorizations
Enter your API key in the format: sk_test_xxxxx or sk_live_xxxxx
Path Parameters
Filing ID
"4b2d9e17-8c35-4a6b-9f02-1e7d5a3c8b96"
Response
Filing canceled
Unique identifier for the resource
"123e4567-e89b-12d3-a456-426614174000"
Object type
filing "filing"
Whether this resource was created with test or live credentials. Test and live data are fully isolated — a test resource never appears in live results and vice versa.
test, live "live"
ISO 8601 timestamp of when the resource was created
"2025-10-24T10:30:00Z"
ISO 8601 timestamp of when the resource was last updated
"2025-10-24T15:45:00Z"
Store up to 50 custom key-value pairs for application-specific data. Useful for storing references to external systems, feature flags, or other custom attributes.
Filing type
formation, ein, amendment, scorp_election Current status
queued, ready_to_file, processing, filed, completed, rejected, canceled, failed Entity type (for formations)
llc, professional_llc, corporation, professional_corporation Jurisdiction (ISO 3166-2)
"US-NC"
Business name for the filing
"Acme Holdings LLC"
Expedited processing tier requested for this filing, or null for standard processing. Only set on formations submitted with an expedited_tier.
"same_day"
Linked business ID
Filing result — populated on completion, null until then. Shape depends on the filing type: formation → { registration_number, formation_date }; EIN → { ein_number, entity_name }. Other filing types have no result.
- Option 1
- Option 2
Parent filing ID (for bundled EIN/RA)
Bundle of obligations tracked under this formation, each with its own object type and status: filings (state registration, EIN) and the registered agent (id is the business, resolvable at GET /business/:id/registered-agent).
- Option 1
- Option 2
Documents associated with this filing
Fee components keyed by type (base, dynamic, late, credit_card, ach), plus a convenience total grand total (assumes credit-card payment). Only present components are included. When items is set, it lists each evaluated rule for itemized rendering — the component-keyed values are the sums across those items.
Reason the filing was canceled (partner request, parent off-boarded, duplicate, etc.). Only present when status is canceled.
Role that initiated the cancellation. One of: partner, palm. Only present when status is canceled.
Timestamp the filing was canceled
Cases attached to this filing. One entry per partner-visible case, in chronological order. Each case carries a typed request payload describing what Palm needs and, once submitted, a typed response. Partners respond via POST /v1/case/:case_id/response. An entry with status=needs_response is an outstanding ask — its presence is the signal that the filing needs partner action.

