> ## Documentation Index > Fetch the complete documentation index at: https://docs.tiro.ooo/llms.txt > Use this file to discover all available pages before exploring further. # Count Wiki Pages > Count all wiki pages visible to the authenticated user in this workspace. Returns a flat object with all, person, org, concept, and decision counts. Counts are independent of list pagination and page-type filters. The optional since parameter limits counts to pages updated on or after the supplied instant. Keyword search (q) is not supported by this endpoint. Requires wiki:read. Returns 402 if wiki is not plan-eligible or not activated. ## OpenAPI ````yaml /openapi.yaml get /v1/external/workspaces/{workspaceGuid}/wiki/pages/counts openapi: 3.1.0 info: title: Tiro API description: AI-powered note-taking and voice file processing API version: 1.0.0 contact: name: Tiro Support email: support@tiro.ooo url: https://tiro.ooo servers: - url: https://api.tiro.ooo description: Production server security: - BearerAuth: [] tags: - name: Workspace description: > List the workspaces an API key can reach. Workspace-scoped endpoints take a `{workspaceGuid}` path segment; get it from `GET /v1/external/workspaces`. - name: Note description: Operations for managing notes and their paragraphs - name: Note Share Link description: Manage share links for notes - name: Note Summary description: Operations for retrieving note summaries - name: Note Document description: Template-based document generation from notes - name: Note Document Template description: Operations for managing note document templates - name: Folder description: Operations for retrieving folders - name: Voice File description: Operations for voice file processing - name: Word Memory description: > Manage word memories to improve voice transcription accuracy. Register important terms like company names, people's names, and product names so Tiro recognizes them precisely during recording. Each term has an `entry` and an optional `subEntry` (an alternate spelling or notation). Personal (User), workspace-shared (Workspace), and organization-shared (Organization) word memories are managed separately, and each scope supports bulk create/update/delete (up to 1000 items per request). - name: Wiki description: | Access workspace wikis — unified knowledge graphs built from notes. Requires a workspace with wiki plan and activation enabled. - name: Organization description: > Endpoints for organization API keys. An organization key is issued by an organization admin, carries fixed scopes chosen at issuance, and can reach the notes in every workspace that belongs to the organization. Built for server-to-server integrations such as CRM sync — receive `note.ended` webhook events, generate documents for notes, and reconcile with the organization notes list. - name: Organization Management description: Operations for the authenticated user's organization. paths: /v1/external/workspaces/{workspaceGuid}/wiki/pages/counts: get: tags: - Wiki summary: Count Wiki Pages description: > Count all wiki pages visible to the authenticated user in this workspace. Returns a flat object with all, person, org, concept, and decision counts. Counts are independent of list pagination and page-type filters. The optional since parameter limits counts to pages updated on or after the supplied instant. Keyword search (q) is not supported by this endpoint. Requires wiki:read. Returns 402 if wiki is not plan-eligible or not activated. operationId: countWikiPages parameters: - name: workspaceGuid in: path description: Workspace GUID example: workspaceGuid required: true schema: type: string - name: since in: query description: ISO 8601 instant. Include only pages updated on or after this time. example: '2026-11-01T00:00:00Z' required: false schema: type: string format: date-time responses: '200': description: Counts of visible wiki pages content: application/json: schema: $ref: '#/components/schemas/WikiPageCounts' '401': description: Unauthorized. Supply a valid API key. content: application/json: schema: $ref: '#/components/schemas/Error' '402': description: >- Wiki plan requirement not met or not activated. Activate wiki on an eligible plan. content: application/json: schema: $ref: '#/components/schemas/WikiPlanRequired' '403': description: Missing wiki:read scope. Use an API key with wiki:read permission. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Workspace not found. Check the workspace GUID and membership. content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: WikiPageCounts: type: object required: - all - person - org - concept - decision properties: all: type: integer format: int64 description: >- Total visible wiki pages, including page types without a dedicated count example: 100 person: type: integer format: int64 description: Visible ENTITY pages with PERSON subtype example: 20 org: type: integer format: int64 description: Visible ENTITY pages with ORGANIZATION subtype example: 10 concept: type: integer format: int64 description: Visible CONCEPT pages example: 60 decision: type: integer format: int64 description: Visible DECISION pages example: 10 Error: type: object required: - error properties: error: type: object required: - code - errorType - message properties: code: type: integer description: > 6-digit error code in `AAABBB` form: first 3 digits match the HTTP status, last 3 digits are a per-status serial (e.g. `404018`). Use only when you need to distinguish specific error cases within the same HTTP status — values may be added or renumbered across releases. For general client branching, prefer `errorType`. example: 404018 errorType: type: string description: > Stable, coarse-grained error category. Recommended default for client-side branching: the value-to-status mapping is part of the API contract and will not change without a breaking-change notice. Typical use: - `unauthorized` → trigger re-authentication - `forbidden` → surface a permission error to the user - `not_found` → treat as missing resource - `too_many_requests` → back off and retry - `internal_error` → retry with exponential backoff enum: - bad_request - unauthorized - forbidden - not_found - not_acceptable - conflict - payload_too_large - unprocessable_entity - too_many_requests - internal_error example: not_found message: type: string description: >- Human-readable error message. Not stable; do not use for branching. example: 'No team found for user #217' detail: description: >- Additional error details. Authorization failures may include a reason and required scopes. oneOf: - type: string nullable: true - type: object additionalProperties: true properties: reason: type: string example: insufficient_scope required: type: array items: type: string example: - folder:read example: null WikiPlanRequired: type: object required: - error_code - message - status_code properties: success: type: boolean description: Always false for error responses example: false error_code: type: string enum: - WIKI_PLAN_REQUIRED - WIKI_NOT_ACTIVATED description: > Machine-readable error code: - `WIKI_PLAN_REQUIRED` — plan does not include wiki - `WIKI_NOT_ACTIVATED` — plan is eligible but admin has not activated wiki example: WIKI_PLAN_REQUIRED message: type: string description: Human-readable error message example: 위키 기능은 Pro 이상 요금제에서 사용할 수 있어요. current_plan: type: string nullable: true description: Current plan name, or null if no subscription example: Lite required_plans: type: array items: type: string nullable: true description: > Upgrade targets for `WIKI_PLAN_REQUIRED`; null for `WIKI_NOT_ACTIVATED`. Team Free Trial is intentionally excluded. example: - pro - max - team - enterprise action_url: type: string format: uri nullable: true description: >- Web link to act on (pricing page for users, null for team members without permission) example: https://tiro.ooo/#pricing status_code: type: integer description: HTTP status code (always 402) example: 402 securitySchemes: BearerAuth: type: http scheme: bearer description: > API key in format `{id}.{secret}`. The notes an endpoint returns depend on the key type. A **user key** reaches the notes that user can see in the app, including notes in their own private folders. A **system key** (workspace or organization, no user identity) reaches only notes that sit in a folder shared with all workspace members. Notes in a private folder, in a folder shared with only some members, or in no folder at all fall outside a system key's read scope, and scopes do not widen that boundary. List and search endpoints drop out-of-scope notes from the response without an error. Single-note reads and their sub-resources return `404`, the same response as a deleted note. See [What notes a system key reads](https://docs.tiro.ooo/en/developers/fundamentals/system-key-note-scope). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.