THE LUMEN CHANGELOG
Always shipping. Just like you.
New capabilities, thoughtful improvements, and the details that make building better.
v2.4
New
A unified connection endpoint now supports every Lumen provider. Create authorization sessions, inspect connection status, and disconnect accounts through one consistent resource.
What’s included
Connection responses now include provider, status, and external_user_id. The previous endpoints remain available during the migration window, so you can roll out the new API incrementally.
v2.3
New
You can now inspect and replay webhook deliveries directly from your workspace. Each delivery shows its payload, response status, and attempt history.
Debug with confidence
Replay preserves the original event ID and signs a new delivery. Make sure handlers deduplicate by event ID before replaying production events. Access is available on Pro and Team.
v2.2
Improved
The rebuilt SDK delivers end-to-end types, smaller bundles, and clearer error messages. Cursor pagination helpers let you process large datasets without managing cursors by hand.
Upgrade notes
Install the latest SDK and replace legacy client initialization with the workspace API key. Existing REST endpoints are unchanged, and the SDK continues to support server-side JavaScript runtimes.
v2.1.1
Fixed
We fixed a race condition that could interrupt token refresh when multiple requests used the same connection at once. Active requests now share a single refresh operation.
No action required
This fix is deployed across all regions. Existing connections remain active and no API changes are required. Failed refresh attempts now include a more specific error code in request logs.
v2.1
New
Team workspaces now include Admin, Developer, and Viewer roles. Scoped API keys help separate read-only monitoring from services that create or remove connections.
Safer by default
New keys can be restricted at creation. Existing keys retain their current permissions until you rotate them. Review workspace access before inviting additional team members.
v2.0.1
Improved
Rate-limit responses now consistently include Retry-After and remaining-capacity headers. Request logs also show the limit that was reached.
Better retry behavior
Clients can use the retry interval instead of guessing a delay. We recommend exponential backoff with jitter when multiple workers share a workspace key.