Workspaces
Select Workspace
Changed onRecord which workspace this user is acting in.
Their selection is stored on their row, so every later request resolves it from the credential instead of from a header the caller has to remember to send on each hop. Any member may select a workspace they belong to; this grants nothing, it only records which of their existing workspaces new resources should land in.
Membership is still re-checked on every request that uses it, so a stored selection cannot outlive the access it was based on.
post/v1/workspaces/{workspace_id}/select
Request
- Base URLhttps://api.getbluejay.ai
- URLhttps://api.getbluejay.ai/v1/workspaces/{workspace_id}/select
- AuthHTTPBearer (a scheme the document does not define)
Path parameters
workspace_idstring required
Headers
X-Organization-Idstring
X-API-Keystring required
API key required to authenticate requests.
Response
Successful Response
Changes
- info
added the new optional
headerrequest parameterX-Organization-Id
- info
- info
endpoint added
- info