> ## Documentation Index > Fetch the complete documentation index at: https://docs.praxis-ai.com/llms.txt > Use this file to discover all available pages before exploring further. # A cross-board view of your open cards > Four views over the open cards on every board the caller may see. `open-loops` is what needs you: cards assigned to you, cards waiting on you, and cards you created that are still unassigned (add `delegated=1` to include cards you created and handed on). `blocked` is cards in the Waiting / Blocked list or carrying a waiting-on person, waiting-on text or a blocked reason. `this-week` answers a fixed layout, Overdue, Monday to Sunday, High priority and Blocked, from due dates and follow-up dates (weeks run Monday to Sunday, UTC). `by-label` groups cards by label, most cards first, with the seed label suggestions. Boards are resolved from the caller's access first and cards are then read by board, so a personal board is never shown to anyone else. Each view is capped at 200 cards and `truncated` is true when more exist. A teammate appears as a name, never an id. Every card carries `nudges`, short reminders computed when you ask (blocked three days or more, who it waits on, a follow-up due today or overdue, a high-priority card that has not moved this week, a card in Review / QA with no one assigned). ## OpenAPI ````yaml /mdx/api-reference/runtime/runtime-api.json get /api/boards/views/{name} openapi: 3.0.0 info: title: Pria Runtime API version: 2.0.282 description: >- Pria API Documentation Praxis's developer platform is a core part of our mission to empower organizations to grow better. Our APIs are designed to enable teams of any shape or size to build robust integrations that help them customize and get the most value out of Pria. All Pria APIs are built using REST conventions and designed to have a predictable URL structure.

They use many standard HTTP features, including methods (POST, GET, PUT, DELETE) and error response codes.

All API calls are made under https://hiimpria.ai/api and all responses return standard JSON. In these docs, you'll find lists of all available endpoints for a given API, along with interactive code blocks for building requests. For walkthroughs of basic usage for these APIs, check out the API guides.

A session that a course page (Canvas) opened for an administrator — or that a Digital Twin's sign-in provider opened for one of its people — starts with user rights in that twin only: until the person confirms it's them with a code (POST /api/user/launch-scope/challenge, then /api/auth/mfa-resend and /api/auth/mfa-verify), every route outside that twin's day-to-day work answers 403 with code LAUNCH_SCOPE_STEP_UP and the twin's id. servers: - url: https://hiimpria.ai description: Pria API Server security: [] tags: - name: Authentication description: User authentication, registration, and password management (/api/auth) - name: OAuth description: OAuth authentication providers - Google, GitHub, SSO (/api/auth/oauth) - name: User description: User profile management and account operations (/api/user) - name: User Institutions description: User institution memberships and switching (/api/user/institution) - name: User Tools description: Available tools for authenticated users (/api/user/tools) - name: Institutions description: Institution settings and configuration (/api/user/institution) - name: Conversation description: AI conversation and Q&A endpoints (/api/ai) - name: Realtime description: Real-time voice AI and WebRTC sessions (/api/ai/rt) - name: Assistant description: AI assistant configuration and management (/api/user/assistant) - name: History description: Conversation history and favorites (/api/user/history) - name: RAG description: >- Document upload, embedding, and retrieval-augmented generation (/api/user/files, /api/user/rag) - name: Setting description: Instance variables and settings management (/api/user/setting) - name: Branding description: Digital twin branding and customization (/api/agent/branding) - name: Agent description: Agent engagement and session management (/api/agent) - name: SDK Launch description: >- SDK launch token signing and verification for secure iframe embedding (/api/auth/sdk-sign, /api/auth/sdk-verify) - name: Testing description: Health checks, diagnostics, and test endpoints (/api/test) - name: Admin Accounts description: Account management for account managers (/api/admin/account) - name: Admin Institutions description: Institution management for admins (/api/admin/institution) - name: Admin Users description: User management for admins (/api/admin/user) - name: Admin Entitlements description: >- User-institution relationships and permissions (/api/admin/userInstitution) - name: Admin Sessions description: Session management for admins (/api/admin/session) - name: Admin Histories description: Conversation history management and analytics (/api/admin/history) - name: Admin Assistants description: AI assistant management for admins (/api/admin/assistant) - name: Admin Questions description: Institution question and prompt management (/api/admin/question) - name: Admin Tools description: Tool configuration management (/api/admin/tool) - name: Admin AI Models description: AI model configuration (/api/admin/aimodel) - name: Admin MCP Servers description: Model Context Protocol server management (/api/admin/mcpserver) - name: Admin Feedbacks description: User feedback management (/api/admin/feedback) - name: Admin Uploads description: Upload management (/api/admin/upload) - name: Admin Charts description: Analytics and visualization chart management (/api/admin/chart) - name: Audio Notes description: Capture and ingest spoken notes into the personal vault - name: Memory description: User-facing memory parameters (personal + shared instance memory). - name: My Data description: >- GDPR controls — personal-scope counts, async ZIP-by-email export, and scoped soft-delete. Every endpoint pins `user = req.user._id` AND `institution: null`; institution-scoped data is governed by the institution's own retention policy and never reached from here. - name: Questions description: >- User-facing read of the onboarding question bank used by the "create a digital twin" wizard. - name: Transcription description: >- One-shot speech-to-text for in-place dictation. Audio blob in, transcript out — no Upload / History / RAG embeddings are persisted. Use `/audio-notes` for anything durable. paths: /api/boards/views/{name}: get: tags: - Boards summary: A cross-board view of your open cards description: > Four views over the open cards on every board the caller may see. `open-loops` is what needs you: cards assigned to you, cards waiting on you, and cards you created that are still unassigned (add `delegated=1` to include cards you created and handed on). `blocked` is cards in the Waiting / Blocked list or carrying a waiting-on person, waiting-on text or a blocked reason. `this-week` answers a fixed layout, Overdue, Monday to Sunday, High priority and Blocked, from due dates and follow-up dates (weeks run Monday to Sunday, UTC). `by-label` groups cards by label, most cards first, with the seed label suggestions. Boards are resolved from the caller's access first and cards are then read by board, so a personal board is never shown to anyone else. Each view is capped at 200 cards and `truncated` is true when more exist. A teammate appears as a name, never an id. Every card carries `nudges`, short reminders computed when you ask (blocked three days or more, who it waits on, a follow-up due today or overdue, a high-priority card that has not moved this week, a card in Review / QA with no one assigned). parameters: - in: path name: name required: true schema: type: string enum: - open-loops - blocked - this-week - by-label - in: query name: scope required: false description: >- all (default), personal, or the id of an institution whose shared workspace the caller may open schema: type: string - in: query name: delegated required: false description: >- open-loops only; 1 also includes cards you created and assigned to someone else schema: type: string responses: '200': description: > open-loops and blocked answer `tasks`; this-week and by-label answer `groups` (each with `key`, `label` and `tasks`; by-label groups also carry `count`, and by-label adds `suggestedLabels`). A card row has `_id`, `title`, `priority`, `dueDate`, `columnId`, `labels`, `board` (`_id`, `name`), `scope`, `blocked`, `nudges`, and for a blocked card `waitingOn`, `reason`, `since`, `followUpAt`, `lastFollowUpAt` and `suggestedFollowUpAt` (three days after the last follow-up, or after it was blocked). content: application/json: schema: type: object properties: success: type: boolean truncated: type: boolean tasks: type: array items: $ref: '#/components/schemas/BoardsViewCard' groups: type: array items: type: object properties: key: type: string label: type: string count: type: integer tasks: type: array items: $ref: '#/components/schemas/BoardsViewCard' suggestedLabels: type: array items: type: string '400': description: Unknown view, or scope is not all, personal or an institution id '401': description: Unauthorized '403': description: No Projects access, or not on that institution's shared workspace security: - apiKeyAuth: [] components: schemas: BoardsViewCard: type: object properties: _id: type: string title: type: string priority: type: string enum: - low - medium - high dueDate: type: string format: date-time nullable: true columnId: type: string labels: type: array items: type: string scope: type: string enum: - personal - shared board: type: object properties: _id: type: string name: type: string blocked: type: boolean waitingOn: type: string reason: type: string since: type: string format: date-time nullable: true followUpAt: type: string format: date-time nullable: true lastFollowUpAt: type: string format: date-time nullable: true suggestedFollowUpAt: type: string format: date-time nullable: true nudges: type: array items: type: object properties: kind: type: string enum: - blocked_days - waiting_on - followup_due - high_unmoved - no_reviewer text: type: string securitySchemes: apiKeyAuth: type: apiKey in: header name: x-access-token description: JWT token passed in x-access-token header ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.