Retrieve 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.
Retrieve a single filing by ID. The response includes the current status, completion result (registration number for formations, EIN for EIN filings), any bundled child filings (related_filings), partner-action cases attached to the filing (cases), generated documents, and recorded fees.
Authorizations
Enter your API key in the format: sk_test_xxxxx or sk_live_xxxxx
Path Parameters
Filing ID
Response
Filing details
Unique identifier for the resource
"123e4567-e89b-12d3-a456-426614174000"
Object type
filing "filing"
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.
{
"external_id": "user_123_in_my_system",
"customer_tier": "premium",
"signup_source": "mobile_app"
}Filing type
formation, ein, registered_agent, ra_change, amendment, scorp_election Current status
queued, ready_to_file, processing, filed, completed, rejected, canceled, failed Entity type (for formations)
llc, corporation Jurisdiction (ISO 3166-2)
"US-NC"
Business name for the filing
"Acme Holdings LLC"
Linked business ID
Filing result — populated on completion. Contents vary by filing type. Formation: { registration_number, formation_date }. EIN: { ein_number, entity_name }.
Parent filing ID (for bundled EIN/RA)
Related filings (EIN, registered agent)
Documents associated with this filing
Fee components keyed by type (base, dynamic, late, credit_card, ach). 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.

