You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to have the ability to filter the result of "/api/session" end point with a single session name.
With this feautures i'm able to know the state of the session.
If the {session} is not available, we should return a 404 error, similar to how it's handled in sessions/{session}/me.
data: {
statusCode: 404,
message: "We didn't find a session with name '{session}'. Please start it first by using POST /sessions/start request",
error: 'Not Found'
}
This ensures consistency in error handling across endpoints and provides clear guidance to users when a session is not found.
It would be useful to have the ability to filter the result of "/api/session" end point with a single session name.
With this feautures i'm able to know the state of the session.
Originally posted by @giovannicarella in #299
GET /api/sessions/{name}
The text was updated successfully, but these errors were encountered: