Repository navigation
docs(platform): socket sessions move to /api/v1 and take a personal access token - #341
Merged
Merged
Conversation
Contributor
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/sdk@0.8.54-pr.341.64849bbPrefer not to change any import paths? Install using npm alias so your code still imports npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.54-pr.341.64849bb"Or add it to your {
"dependencies": {
"@base44/sdk": "npm:@base44-preview/sdk@0.8.54-pr.341.64849bb"
}
}
Preview published to npm registry — try new features instantly! |
Contributor
🚀 Package Preview Available! (
|
…ccess token
Your backend opens a session at POST /api/v1/socket-sessions with a personal
access token or a workspace key (apps:watch), and manages its apps at
/{session_id}/apps/{app_id}. No code change: the client only reads the
session body.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ozsay
force-pushed
the
ozs/platform-socket-sessions-pat
branch
from
October 19, 2026 14:41
58f6d1f to
482eaf7
Compare
ozsay
marked this pull request as ready for review
October 19, 2026 14:42
amitbardos
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Platform SDK README described the white-label socket-session API at its old path and as workspace-key only. base44-dev/apper#31673 moves it and adds personal access tokens:
POST /api/service/socket-sessions→POST /api/v1/socket-sessionsPUT/DELETE …/{session_id}/rooms/{app_id}→…/{session_id}/apps/{app_id}apps:watch, both asAuthorization: Bearer. The workspace needs the Builder plan or higher.No code change: the client only reads the session body (
session_token,socket_url,socket_path), which is unchanged.asyncapi.jsonpicks up the new wording through the hourly sync.Merge order
Merge after base44-dev/apper#31673 is deployed, since until then the new path doesn't exist.
🤖 Generated with Claude Code