Get current workspace identity
GET /v1/me
Returns the workspace identity associated with the bearer key. Useful as a connectivity smoke-test. No specific scope is required - any valid key may call this endpoint.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”Authenticated workspace identity.
Workspace identity returned by GET /v1/me.
object
Internal user id.
Workspace email address.
Display name (maps to FullName on the user record).
Account creation timestamp (UTC).
Metadata about the API key used in this request.
object
12-character key identifier.
Scopes granted to this key.
Which shared pool this request acted on, and which ids the key may switch to with X-Workspace-Id. Without this an integration has no way to discover that a team scope exists.
object
Workspace this request resolved to. Null means personal scope.
The caller’s role in the active workspace. A Viewer cannot write.
Name of the header that selects a workspace (“X-Workspace-Id”).
Every workspace this key may address.
object
Example
{ "id": 42, "email": "jane@example.com", "name": "Acme Inc.", "createdAt": "2024-01-15T09:00:00Z", "apiKey": { "keyId": "abc123def456", "scopes": [ "contacts:read", "telegram:send" ] }}Missing or invalid bearer token.
Standard error envelope for all v1 error responses.
object
Machine-readable error code.
Human-readable explanation of the error.
Optional structured context (field-level validation errors, etc.).
Example
{ "error": "unauthorized", "message": "Invalid bearer principal"}The requested resource does not exist or is not owned by the caller.
Standard error envelope for all v1 error responses.
object
Machine-readable error code.
Human-readable explanation of the error.
Optional structured context (field-level validation errors, etc.).
Example
{ "error": "not_found", "message": "contact not found"}