Inspect the Current Workspace Context
Check who the current principal is, which workspace is active, and which installation context is in effect before you run sensitive automation or admin work.
API In this interface
4 steps Steps
2 interfaces Available in
Use this path when
Use the introspection endpoints before running scoped work that depends on the current principal or workspace.
What you'll finish here
- Identify the current principal.
- Confirm the active workspace.
- Prevent admin work in the wrong workspace.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Do the work
- 1. Call `/api/v1/me` first to confirm whether the token resolved to a human or automation principal.
- 2. Read the `workspace` block to confirm the current workspace id, name, and context.
- 3. If the token is automation-backed, check the automation id, provider type, and allowed team ids before you issue write calls.
- 4. Call `/api/v1/workspaces` when you still need to resolve the workspace id for admin endpoints.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.