Skip to main content
Stay up to date with new features, improvements, and bug fixes to the Palm Platform.

​
Week of July 6, 2026

API — Test mode is here: every API key and Console view now resolves to test or live, with all data partitioned by mode so test activity never touches production. Registered Agent — Registered Agent is now its own resource with its own status lifecycle, and new registered-agent webhook events track it from creation through every change. Formations & Filings — A formation now exposes a related-items view: each part of the bundle reports its own status, plus an overall completion rollup.

​
Week of June 29, 2026

Registry — Business registry detail lookups now return a grouped identifier object that surfaces additional well-known identifiers Palm already holds for a business — the Legal Entity Identifier (identifier.lei), the SEC EDGAR identifier (CIK), the Canadian Business Number, and the state taxpayer number — so you can cross-reference a business against external registries like GLEIF and SEC EDGAR directly from our response. Only identifiers that are present for a given business are included, keeping the payload lean. Formations & Filings — The EIN application now captures the IRS’s conditional Form SS-4 questions as structured fields, covering the category-specific principal-activity follow-ups and employee-count details, so a complete application can be submitted in a single request; you can also dry-run validate an EIN application before submitting it. Fee estimates and the filing.completed event now include a total fee alongside the line-item breakdown. Webhooks — You can now replay past webhook events for a chosen time range, self-serve from the Console and via the API, giving you a standard way to recover deliveries after an outage on your side. Endpoints that are automatically disabled after sustained delivery failures now also send an email alert so you know to step in.

​
Week of June 22, 2026

Registry — Registry search can now start from a person, not just a business. Pass a person’s name and you get back every business they’re connected to — as an officer, director, manager, member, or registered agent — which makes due-diligence and KYB workflows much easier. You can also filter registry search by Palm ID to jump straight to a business you’ve already seen. Formations & Filings — Breaking: filing documents are now referenced by a document ID rather than a URL. Update any integration that reads document URLs from filing responses.

​
Week of June 15, 2026

Formations & Filings — The formation requirements endpoint now returns fully self-contained schemas. Unresolved $refs are gone, so you can parse requirements directly without dereferencing external pointers.

​
Week of June 8, 2026

Formations & Filings — The Formations & Filings API is live. You can form LLCs and Corporations programmatically end to end: apply for an EIN, check name availability, pull state-aware filing requirements, get fee estimates before you file, and track each filing through its full status lifecycle — with webhooks firing on every status change. Registered Agent — The Registered Agent API launched alongside it. Retrieve an agent’s status, name, and address, and request an RA change or termination through the API. Lifecycle webhooks — registered_agent.activated, .changed, .termination_requested, and .terminated — keep your systems in sync as things change. Webhooks — A new document.created event fires the moment a document becomes available on a business, so you can react without polling. We also fixed filing.completed so it always includes the fee field, which could previously come back null. Verify — Identity verification scoring got more accurate, cutting down false positives on legitimate individuals.

​
Week of May 25, 2026

Formations & Filings — Filings that need extra information now drive an information-request flow, giving you a structured way to collect and submit the missing fields. Verify — Improved EIN matching during business verification. Webhooks — Webhook signature headers are now matched case-insensitively, which fixes signature verification for HTTP clients that normalize header casing. Business — You can now delete a business through the API, so you can clean up records you no longer need to track on your own.

​
Week of May 18, 2026

Verify — When several businesses look alike, verification now disambiguates between them and resolves to the best match more reliably. Formations & Filings — Filings can now report exception statuses, giving you a clearer signal when one needs attention.

​
Week of April 13, 2026

Single Sign-On for Palm Console Users can now access the Palm Console with their Google account, removing password friction. Public Developer Documentation Palm’s API and product capabilities can be evaluated directly, without gating or access requests. Monitor Next Actions On top of registry change events, Monitor now surfaces the specific next compliance action a business needs to take. Usage-Based Pricing Palm now meters API usage across verification, registry search and detail, and monitoring subscriptions.

​
Week of January 19, 2026

Registry API Updates
  • New endpoint: GET /v1/business/registry/{jurisdiction}/{registration_number} - Retrieve business details directly by registration number
  • Registry search endpoint path updated to /v1/business/registry/search (the previous path /v1/business/registry-search is deprecated but still supported)
Webhook Events Standardized webhook event types for clearer, more consistent notifications:
  • user.created - New user added
  • user.removed - User deleted
  • user.verification.completed - User identity verification finished
  • business.created - New business added
  • business.removed - Business deleted
  • business.verification.completed - Business verification finished
  • business.registration.updated - Secretary of State registration changed
  • business.filing.due - Upcoming filing deadline
  • business.filing.overdue - Missed filing deadline
  • session.completed - Onboarding session finished

​
Breaking Changes

We take backward compatibility seriously. Any breaking changes will be:
  1. Announced at least 3 months in advance
  2. Documented with migration guides
  3. Supported in a new API version
  4. Available for testing before production rollout

​
Report Issues

Found a bug or have a feature request?