> ## Documentation Index > Fetch the complete documentation index at: https://developers.parkes.ai/llms.txt > Use this file to discover all available pages before exploring further. # List incoming document links > Required scopes (OAuth and personal tokens): knowledge:read. Resource permissions also apply. ## OpenAPI ````yaml /openapi.json get /rest/v1/knowledge/documents/{id}/backlinks openapi: 3.0.3 info: title: Parkes REST API version: 1.0.0 description: > Work with your organization’s resources and browse and install marketplace content. Publisher management is documented in the Marketplace API. ## Authentication and organization access Send an OAuth access token or personal token as `Authorization: Bearer `. Each credential belongs to exactly one organization. Authorize additional organizations separately; resource routes do not take an organization selection header or path parameter. Required scopes and current member permissions both apply. Use `GET /rest/v1/me` to inspect the authenticated identity. ## Pagination Collections return `data` and `page.next_cursor`. A null cursor means the traversal is complete. Pass the cursor with the same filters to retrieve the next page. Most collections default to 50 records and allow up to 200; Knowledge search has its own limit. Activity tail cursors represent a continuing feed rather than a completed traversal. ## Mutations and concurrency Send JSON for operations with a request body. Unknown fields are rejected; omitted update fields stay unchanged and null is accepted only where declared nullable. Every POST requires an `Idempotency-Key` of at most 128 bytes. Reuse the same key and body when retrying the same logical mutation. Other mutations accept an optional key. Conditional mutations require `If-Match` with the resource's latest ETag. For nested automation triggers and Marketplace items, use the parent automation or release ETag returned by the read operation. Knowledge content writes additionally require `expected_version` from the document's version field. A 202 response confirms admission, not completion; follow the returned operation or run. ## Errors and limits Handled API errors use `application/problem+json`. Inspect `code` for the error category, `detail` for context, and `request_id` when reporting a failure. Validation errors may include an `errors` object keyed by field. Each operation lists its expected errors. Unexpected server or infrastructure errors may have a different body; clients must tolerate other HTTP error responses. The request body limit is 2 MiB unless an operation specifies otherwise. The limit applies even to a body sent with a read request. Request budgets are shared per member and organization; a 429 response includes `Retry-After` in seconds. A temporarily unavailable API contract can also return 503 on any operation. servers: - url: https://api.parkes.ai security: - bearer: [] tags: - name: Identity description: >- Inspect the user, organization, and scopes associated with your bearer credential. Use this endpoint to confirm which account and organization your integration is acting on. - name: Organizations description: >- Read metadata for the organization bound to your credential. The collection contains that organization only. To work with another organization, authorize it separately and use its credential. - name: Skills description: >- Create reusable prompts, manage their content, and share them with other members of your organization. Fork an accessible skill to make your own copy, or restore a fork from its source. Run a skill with optional input to start an asynchronous execution. Follow the returned run to inspect its status and logs. - name: Knowledge description: >- Browse namespaces and documents, search their content, and explore document history and links. Collection endpoints return metadata; fetch a document or version to read its content. Content updates require both the document ETag and its content version. Personal tokens can write only to the user’s own namespace. - name: Personal tokens description: >- Create and revoke credentials for unattended integrations, and inspect existing token metadata. Each token is bound to one organization and has its own scopes and expiry. Issuance requires recent first-party CLI OAuth authentication. The secret is returned only when the token is created; it cannot be recovered by replaying the request. - name: Integrations description: >- Discover available integration providers and inspect their tools, triggers, and input schemas. Enable providers for your organization before creating connections. Provider availability and management actions remain subject to your account permissions. - name: Connections description: >- Connect external accounts, inspect their tools, and manage sharing and sync configuration. Creating or reconnecting an account returns a connection session with an authorization URL. Follow the session to check connection progress. Disconnection and sync changes return asynchronous operations that can be polled for completion. - name: Automations description: >- Create workflows with prompts and scheduled or integration-based triggers. Manage their definitions, sharing, and enabled state, or start a manual run. Trigger mutations use the parent automation’s ETag. Changes that require asynchronous activation return an operation; run endpoints expose execution status and logs. - name: Operations description: >- Track background work accepted by mutation endpoints. Poll the returned operation until it reaches a terminal state. Only `successful` confirms completion. Inspect `error_code` when an operation fails. A `needs_attention` outcome requires investigation before repeating the mutation. - name: Runs description: >- Inspect an execution started through the API and retrieve its conversation logs. Access follows the underlying skill conversation or automation permissions. Logs are paginated and may change while a run is active. Poll the run to determine when execution finishes. - name: Members description: >- List organization members and inspect their roles and access status. Administrators with the required scope can change roles, suspend members, or reactivate them. Member IDs identify organization memberships; the separate `user_id` identifies the user account. Conditional changes require the member’s current ETag. - name: Invitations description: >- Invite people to your organization, inspect pending invitations, resend delivery, or revoke an invitation. Creation and resending return an invitation together with a delivery operation. Follow that operation to confirm delivery processing. Resending and revoking require the invitation’s current ETag. - name: Models description: >- Discover the models available to your account and inspect their reasoning settings and context and output limits. Use a returned model ID when configuring an automation that accepts a model selection. - name: Activity description: >- Browse recorded activity and filter events by time, actor, type, status, or origin. Fetch an event separately to inspect its payload. Tail follows newly published deliveries using a resumable cursor. Deduplicate deliveries by `delivery_id`. Archive endpoints expose older activity and allow authorized users to request hydration. - name: Marketplace description: >- Browse published listings, categories, publishers, releases, and release items. Install content into your organization, preview updates or removal, and manage installations. Publisher authoring and publishing are documented separately in the Marketplace API. - name: Library description: >- Browse your accessible files and folders, inspect file metadata, and retrieve content or temporary download URLs. Small Markdown and plain-text files can be returned inline. Create expiring share links when sharing is permitted. Deleting an item requires its current ETag. - name: Agent runs description: >- Start an agent execution with the supported AG-UI input and follow its server-sent event stream. Admission returns the run and an `events_path`; use `Last-Event-ID` to resume event delivery. Closing the stream does not cancel execution. Personal tokens start unattended runs and cannot resolve interactive approvals or questions. - name: Community description: >- Browse community spaces, discussions, comments, and replies. Participation actions include joining spaces, commenting, and reacting, subject to the organization’s plan and current permissions. Writes return asynchronous operations. Reaction changes require the discussion’s current ETag. Paginated discussions may repeat pinned posts, so deduplicate by ID. - name: Notifications description: >- Register or remove an iOS APNs device token for agent-run notifications. These endpoints require the iOS-only `notifications:write` scope and are unavailable to CLI credentials and personal tokens. A device token belongs to the user who most recently registered it. paths: /rest/v1/knowledge/documents/{id}/backlinks: get: tags: - Knowledge summary: List incoming document links description: >- Required scopes (OAuth and personal tokens): knowledge:read. Resource permissions also apply. operationId: backlinksDocuments parameters: - name: id in: path required: true schema: type: string description: Identifier of the requested resource. - name: cursor in: query schema: type: string description: >- Opaque cursor from page.next_cursor. Keep the original filters unchanged when requesting the next page. - name: limit in: query schema: type: integer minimum: 1 maximum: 200 default: 50 description: Maximum number of results to return in this page. responses: '200': description: Request completed successfully. content: application/json: schema: $ref: '#/components/schemas/BacklinksDocumentsResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '413': $ref: '#/components/responses/ContentTooLarge' '429': $ref: '#/components/responses/TooManyRequests' security: - oauth: - knowledge:read - bearer: [] components: schemas: BacklinksDocumentsResponse: type: object properties: data: type: array items: $ref: '#/components/schemas/Document' page: type: object properties: next_cursor: type: string nullable: true required: - next_cursor required: - data - page Document: type: object properties: id: type: string namespace_id: type: string path: type: string title: type: string kind: type: string status: type: string visibility: type: string updated_at: type: string content: type: string nullable: true version: type: string required: - id - namespace_id - path - title - kind - status - visibility - updated_at Problem: type: object properties: type: type: string title: type: string status: type: integer code: type: string detail: type: string request_id: type: string description: Request identifier to include when reporting an API failure. errors: type: object additionalProperties: type: array items: type: string required: - type - title - status - code - detail description: >- A handled API failure. The HTTP status and status field agree; code identifies the failure category. responses: BadRequest: description: Invalid request parameters, body, or idempotency key. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' Unauthorized: description: Missing, expired, revoked, or invalid bearer credential. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' example: type: about:blank title: Unauthenticated status: 401 code: unauthenticated detail: A valid bearer credential is required request_id: 0b7238c5-a883-4ed0-8613-31f531e50f40 headers: WWW-Authenticate: description: Bearer authentication challenge. schema: type: string example: Bearer Forbidden: description: Insufficient scope or resource permissions. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' NotFound: description: Resource not found or not visible to this credential. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' ContentTooLarge: description: Request body exceeds the operation limit. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' TooManyRequests: description: Rate limit exceeded; wait Retry-After seconds. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' headers: Retry-After: description: Delay in seconds before retrying. schema: type: integer example: 60 securitySchemes: bearer: type: http scheme: bearer oauth: type: oauth2 flows: authorizationCode: authorizationUrl: /oauth/authorize tokenUrl: /oauth/token refreshUrl: /oauth/token scopes: organizations:read: Organizations read integrations:read: Integrations read integrations:write: Integrations write connections:read: Connections read connections:write: Connections write skills:read: Skills read skills:write: Skills write skills:execute: Skills execute automations:read: Automations read automations:write: Automations write automations:execute: Automations execute knowledge:read: Knowledge read knowledge:write: Knowledge write marketplace:read: Marketplace read marketplace:write: Marketplace write marketplace:publish: Marketplace publish users:read: Users read users:manage: Users manage activity:read: Activity read activity:write: Activity write models:read: Models read library:read: Read Library files and folders library:write: Delete Library files and create share links agent:execute: >- Execute and observe agent conversations; browser OAuth may resolve interactions community:read: Read Community spaces and discussions community:write: Join spaces, comment, and react notifications:write: >- Register this device for push notifications about the user's agent runs; granted only to the first-party iOS app ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.