This commit is contained in:
a2a-platform
2026-06-27 01:02:21 +00:00
commit 197f1bd317
61 changed files with 48605 additions and 0 deletions

View File

@@ -0,0 +1,25 @@
---
name: ai-agent-default-routes
description: Handle 1 OpenAPI operation(s) under /ai_agent_default for the ai agent default route group.
---
# ai agent default API Routes
Handle 1 OpenAPI operation(s) under /ai_agent_default for the ai agent default route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_ai_agent_default
- Operation ID: `get_ai_agent_default`
- Route: `GET /ai_agent_default`
- Mode: READ
- Summary: Get AI agent default configuration
- Parameters:
- `mode` in `query` required
- `language` in `query`
- `model` in `query`

65
skills/ai-agents/SKILL.md Normal file
View File

@@ -0,0 +1,65 @@
---
name: ai-agents-routes
description: Handle 5 OpenAPI operation(s) under /ai_agents for the ai agents route group.
---
# ai agents API Routes
Handle 5 OpenAPI operation(s) under /ai_agents for the ai agents route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_ai_agents
- Operation ID: `get_ai_agents`
- Route: `GET /ai_agents`
- Mode: READ
- Summary: List AI agents
- Parameters:
- `mode` in `query`
- `fields` in `query`
- `agent_state` in `query`
- `include_box_default` in `query`
- `marker` in `query`
- `limit` in `query`
### post_ai_agents
- Operation ID: `post_ai_agents`
- Route: `POST /ai_agents`
- Mode: WRITE
- Summary: Create AI agent
- Body: JSON request body accepted.
### put_ai_agents_id
- Operation ID: `put_ai_agents_id`
- Route: `PUT /ai_agents/{agent_id}`
- Mode: WRITE
- Summary: Update AI agent
- Parameters:
- `agent_id` in `path` required
- Body: JSON request body accepted.
### get_ai_agents_id
- Operation ID: `get_ai_agents_id`
- Route: `GET /ai_agents/{agent_id}`
- Mode: READ
- Summary: Get AI agent by agent ID
- Parameters:
- `agent_id` in `path` required
- `fields` in `query`
### delete_ai_agents_id
- Operation ID: `delete_ai_agents_id`
- Route: `DELETE /ai_agents/{agent_id}`
- Mode: WRITE
- Summary: Delete AI agent
- Parameters:
- `agent_id` in `path` required

46
skills/ai/SKILL.md Normal file
View File

@@ -0,0 +1,46 @@
---
name: ai-routes
description: Handle 4 OpenAPI operation(s) under /ai for the ai route group.
---
# ai API Routes
Handle 4 OpenAPI operation(s) under /ai for the ai route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_ai_ask
- Operation ID: `post_ai_ask`
- Route: `POST /ai/ask`
- Mode: WRITE
- Summary: Ask question
- Body: JSON request body accepted.
### post_ai_text_gen
- Operation ID: `post_ai_text_gen`
- Route: `POST /ai/text_gen`
- Mode: WRITE
- Summary: Generate text
- Body: JSON request body accepted.
### post_ai_extract
- Operation ID: `post_ai_extract`
- Route: `POST /ai/extract`
- Mode: WRITE
- Summary: Extract metadata (freeform)
- Body: JSON request body accepted.
### post_ai_extract_structured
- Operation ID: `post_ai_extract_structured`
- Route: `POST /ai/extract_structured`
- Mode: WRITE
- Summary: Extract metadata (structured)
- Body: JSON request body accepted.

27
skills/authorize/SKILL.md Normal file
View File

@@ -0,0 +1,27 @@
---
name: authorize-routes
description: Handle 1 OpenAPI operation(s) under /authorize for the authorize route group.
---
# authorize API Routes
Handle 1 OpenAPI operation(s) under /authorize for the authorize route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_authorize
- Operation ID: `get_authorize`
- Route: `GET /authorize`
- Mode: READ
- Summary: Authorize user
- Parameters:
- `response_type` in `query` required
- `client_id` in `query` required
- `redirect_uri` in `query`
- `state` in `query`
- `scope` in `query`

View File

@@ -0,0 +1,50 @@
---
name: collaboration-whitelist-entries-routes
description: Handle 4 OpenAPI operation(s) under /collaboration_whitelist_entries for the collaboration whitelist entries route group.
---
# collaboration whitelist entries API Routes
Handle 4 OpenAPI operation(s) under /collaboration_whitelist_entries for the collaboration whitelist entries route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_collaboration_whitelist_entries
- Operation ID: `get_collaboration_whitelist_entries`
- Route: `GET /collaboration_whitelist_entries`
- Mode: READ
- Summary: List allowed collaboration domains
- Parameters:
- `marker` in `query`
- `limit` in `query`
### post_collaboration_whitelist_entries
- Operation ID: `post_collaboration_whitelist_entries`
- Route: `POST /collaboration_whitelist_entries`
- Mode: WRITE
- Summary: Add domain to list of allowed collaboration domains
- Body: JSON request body accepted.
### get_collaboration_whitelist_entries_id
- Operation ID: `get_collaboration_whitelist_entries_id`
- Route: `GET /collaboration_whitelist_entries/{collaboration_whitelist_entry_id}`
- Mode: READ
- Summary: Get allowed collaboration domain
- Parameters:
- `collaboration_whitelist_entry_id` in `path` required
### delete_collaboration_whitelist_entries_id
- Operation ID: `delete_collaboration_whitelist_entries_id`
- Route: `DELETE /collaboration_whitelist_entries/{collaboration_whitelist_entry_id}`
- Mode: WRITE
- Summary: Remove domain from list of allowed collaboration domains
- Parameters:
- `collaboration_whitelist_entry_id` in `path` required

View File

@@ -0,0 +1,50 @@
---
name: collaboration-whitelist-exempt-targets-routes
description: Handle 4 OpenAPI operation(s) under /collaboration_whitelist_exempt_targets for the collaboration whitelist exempt targets route group.
---
# collaboration whitelist exempt targets API Routes
Handle 4 OpenAPI operation(s) under /collaboration_whitelist_exempt_targets for the collaboration whitelist exempt targets route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_collaboration_whitelist_exempt_targets
- Operation ID: `get_collaboration_whitelist_exempt_targets`
- Route: `GET /collaboration_whitelist_exempt_targets`
- Mode: READ
- Summary: List users exempt from collaboration domain restrictions
- Parameters:
- `marker` in `query`
- `limit` in `query`
### post_collaboration_whitelist_exempt_targets
- Operation ID: `post_collaboration_whitelist_exempt_targets`
- Route: `POST /collaboration_whitelist_exempt_targets`
- Mode: WRITE
- Summary: Create user exemption from collaboration domain restrictions
- Body: JSON request body accepted.
### get_collaboration_whitelist_exempt_targets_id
- Operation ID: `get_collaboration_whitelist_exempt_targets_id`
- Route: `GET /collaboration_whitelist_exempt_targets/{collaboration_whitelist_exempt_target_id}`
- Mode: READ
- Summary: Get user exempt from collaboration domain restrictions
- Parameters:
- `collaboration_whitelist_exempt_target_id` in `path` required
### delete_collaboration_whitelist_exempt_targets_id
- Operation ID: `delete_collaboration_whitelist_exempt_targets_id`
- Route: `DELETE /collaboration_whitelist_exempt_targets/{collaboration_whitelist_exempt_target_id}`
- Mode: WRITE
- Summary: Remove user from list of users exempt from domain restrictions
- Parameters:
- `collaboration_whitelist_exempt_target_id` in `path` required

View File

@@ -0,0 +1,66 @@
---
name: collaborations-routes
description: Handle 5 OpenAPI operation(s) under /collaborations for the collaborations route group.
---
# collaborations API Routes
Handle 5 OpenAPI operation(s) under /collaborations for the collaborations route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_collaborations_id
- Operation ID: `get_collaborations_id`
- Route: `GET /collaborations/{collaboration_id}`
- Mode: READ
- Summary: Get collaboration
- Parameters:
- `collaboration_id` in `path` required
- `fields` in `query`
### put_collaborations_id
- Operation ID: `put_collaborations_id`
- Route: `PUT /collaborations/{collaboration_id}`
- Mode: WRITE
- Summary: Update collaboration
- Parameters:
- `collaboration_id` in `path` required
- Body: JSON request body accepted.
### delete_collaborations_id
- Operation ID: `delete_collaborations_id`
- Route: `DELETE /collaborations/{collaboration_id}`
- Mode: WRITE
- Summary: Remove collaboration
- Parameters:
- `collaboration_id` in `path` required
### get_collaborations
- Operation ID: `get_collaborations`
- Route: `GET /collaborations`
- Mode: READ
- Summary: List pending collaborations
- Parameters:
- `status` in `query` required
- `fields` in `query`
- `offset` in `query`
- `limit` in `query`
### post_collaborations
- Operation ID: `post_collaborations`
- Route: `POST /collaborations`
- Mode: WRITE
- Summary: Create collaboration
- Parameters:
- `fields` in `query`
- `notify` in `query`
- Body: JSON request body accepted.

View File

@@ -0,0 +1,46 @@
---
name: collections-routes
description: Handle 3 OpenAPI operation(s) under /collections for the collections route group.
---
# collections API Routes
Handle 3 OpenAPI operation(s) under /collections for the collections route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_collections
- Operation ID: `get_collections`
- Route: `GET /collections`
- Mode: READ
- Summary: List all collections
- Parameters:
- `fields` in `query`
- `offset` in `query`
- `limit` in `query`
### get_collections_id_items
- Operation ID: `get_collections_id_items`
- Route: `GET /collections/{collection_id}/items`
- Mode: READ
- Summary: List collection items
- Parameters:
- `collection_id` in `path` required
- `fields` in `query`
- `offset` in `query`
- `limit` in `query`
### get_collections_id
- Operation ID: `get_collections_id`
- Route: `GET /collections/{collection_id}`
- Mode: READ
- Summary: Get collection by ID
- Parameters:
- `collection_id` in `path` required

54
skills/comments/SKILL.md Normal file
View File

@@ -0,0 +1,54 @@
---
name: comments-routes
description: Handle 4 OpenAPI operation(s) under /comments for the comments route group.
---
# comments API Routes
Handle 4 OpenAPI operation(s) under /comments for the comments route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_comments_id
- Operation ID: `get_comments_id`
- Route: `GET /comments/{comment_id}`
- Mode: READ
- Summary: Get comment
- Parameters:
- `comment_id` in `path` required
- `fields` in `query`
### put_comments_id
- Operation ID: `put_comments_id`
- Route: `PUT /comments/{comment_id}`
- Mode: WRITE
- Summary: Update comment
- Parameters:
- `comment_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### delete_comments_id
- Operation ID: `delete_comments_id`
- Route: `DELETE /comments/{comment_id}`
- Mode: WRITE
- Summary: Remove comment
- Parameters:
- `comment_id` in `path` required
### post_comments
- Operation ID: `post_comments`
- Route: `POST /comments`
- Mode: WRITE
- Summary: Create comment
- Parameters:
- `fields` in `query`
- Body: JSON request body accepted.

View File

@@ -0,0 +1,32 @@
---
name: device-pinners-routes
description: Handle 2 OpenAPI operation(s) under /device_pinners/{device_pinner_id} for the device pinners route group.
---
# device pinners API Routes
Handle 2 OpenAPI operation(s) under /device_pinners/{device_pinner_id} for the device pinners route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_device_pinners_id
- Operation ID: `get_device_pinners_id`
- Route: `GET /device_pinners/{device_pinner_id}`
- Mode: READ
- Summary: Get device pin
- Parameters:
- `device_pinner_id` in `path` required
### delete_device_pinners_id
- Operation ID: `delete_device_pinners_id`
- Route: `DELETE /device_pinners/{device_pinner_id}`
- Mode: WRITE
- Summary: Remove device pin
- Parameters:
- `device_pinner_id` in `path` required

View File

@@ -0,0 +1,26 @@
---
name: enterprises-routes
description: Handle 1 OpenAPI operation(s) under /enterprises/{enterprise_id}/device_pinners for the enterprises route group.
---
# enterprises API Routes
Handle 1 OpenAPI operation(s) under /enterprises/{enterprise_id}/device_pinners for the enterprises route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_enterprises_id_device_pinners
- Operation ID: `get_enterprises_id_device_pinners`
- Route: `GET /enterprises/{enterprise_id}/device_pinners`
- Mode: READ
- Summary: List enterprise device pins
- Parameters:
- `enterprise_id` in `path` required
- `marker` in `query`
- `limit` in `query`
- `direction` in `query`

35
skills/events/SKILL.md Normal file
View File

@@ -0,0 +1,35 @@
---
name: events-routes
description: Handle 2 OpenAPI operation(s) under /events for the events route group.
---
# events API Routes
Handle 2 OpenAPI operation(s) under /events for the events route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### options_events
- Operation ID: `options_events`
- Route: `OPTIONS /events`
- Mode: READ
- Summary: Get events long poll endpoint
### get_events
- Operation ID: `get_events`
- Route: `GET /events`
- Mode: READ
- Summary: List user and enterprise events
- Parameters:
- `stream_type` in `query`
- `stream_position` in `query`
- `limit` in `query`
- `event_type` in `query`
- `created_after` in `query`
- `created_before` in `query`

View File

@@ -0,0 +1,53 @@
---
name: file-requests-routes
description: Handle 4 OpenAPI operation(s) under /file_requests/{file_request_id} for the file requests route group.
---
# file requests API Routes
Handle 4 OpenAPI operation(s) under /file_requests/{file_request_id} for the file requests route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_file_requests_id
- Operation ID: `get_file_requests_id`
- Route: `GET /file_requests/{file_request_id}`
- Mode: READ
- Summary: Get file request
- Parameters:
- `file_request_id` in `path` required
### put_file_requests_id
- Operation ID: `put_file_requests_id`
- Route: `PUT /file_requests/{file_request_id}`
- Mode: WRITE
- Summary: Update file request
- Parameters:
- `file_request_id` in `path` required
- `if-match` in `header`
- Body: JSON request body accepted.
### delete_file_requests_id
- Operation ID: `delete_file_requests_id`
- Route: `DELETE /file_requests/{file_request_id}`
- Mode: WRITE
- Summary: Delete file request
- Parameters:
- `file_request_id` in `path` required
### post_file_requests_id_copy
- Operation ID: `post_file_requests_id_copy`
- Route: `POST /file_requests/{file_request_id}/copy`
- Mode: WRITE
- Summary: Copy file request
- Parameters:
- `file_request_id` in `path` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,34 @@
---
name: file-version-legal-holds-routes
description: Handle 2 OpenAPI operation(s) under /file_version_legal_holds for the file version legal holds route group.
---
# file version legal holds API Routes
Handle 2 OpenAPI operation(s) under /file_version_legal_holds for the file version legal holds route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_file_version_legal_holds_id
- Operation ID: `get_file_version_legal_holds_id`
- Route: `GET /file_version_legal_holds/{file_version_legal_hold_id}`
- Mode: READ
- Summary: Get file version legal hold
- Parameters:
- `file_version_legal_hold_id` in `path` required
### get_file_version_legal_holds
- Operation ID: `get_file_version_legal_holds`
- Route: `GET /file_version_legal_holds`
- Mode: READ
- Summary: List file version legal holds
- Parameters:
- `policy_id` in `query` required
- `marker` in `query`
- `limit` in `query`

View File

@@ -0,0 +1,39 @@
---
name: file-version-retentions-routes
description: Handle 2 OpenAPI operation(s) under /file_version_retentions for the file version retentions route group.
---
# file version retentions API Routes
Handle 2 OpenAPI operation(s) under /file_version_retentions for the file version retentions route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_file_version_retentions
- Operation ID: `get_file_version_retentions`
- Route: `GET /file_version_retentions`
- Mode: READ
- Summary: List file version retentions
- Parameters:
- `file_id` in `query`
- `file_version_id` in `query`
- `policy_id` in `query`
- `disposition_action` in `query`
- `disposition_before` in `query`
- `disposition_after` in `query`
- `limit` in `query`
- `marker` in `query`
### get_file_version_retentions_id
- Operation ID: `get_file_version_retentions_id`
- Route: `GET /file_version_retentions/{file_version_retention_id}`
- Mode: READ
- Summary: Get retention on file
- Parameters:
- `file_version_retention_id` in `path` required

526
skills/files/SKILL.md Normal file
View File

@@ -0,0 +1,526 @@
---
name: files-routes
description: Handle 48 OpenAPI operation(s) under /files for the files route group.
---
# files API Routes
Handle 48 OpenAPI operation(s) under /files for the files route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_files_id
- Operation ID: `get_files_id`
- Route: `GET /files/{file_id}`
- Mode: READ
- Summary: Get file information
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- `if-none-match` in `header`
- `boxapi` in `header`
- `x-rep-hints` in `header`
### post_files_id
- Operation ID: `post_files_id`
- Route: `POST /files/{file_id}`
- Mode: WRITE
- Summary: Restore file
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### put_files_id
- Operation ID: `put_files_id`
- Route: `PUT /files/{file_id}`
- Mode: WRITE
- Summary: Update file
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- `if-match` in `header`
- Body: JSON request body accepted.
### delete_files_id
- Operation ID: `delete_files_id`
- Route: `DELETE /files/{file_id}`
- Mode: WRITE
- Summary: Delete file
- Parameters:
- `file_id` in `path` required
- `if-match` in `header`
### get_files_id_app_item_associations
- Operation ID: `get_files_id_app_item_associations`
- Route: `GET /files/{file_id}/app_item_associations`
- Mode: READ
- Summary: List file app item associations
- Parameters:
- `file_id` in `path` required
- `limit` in `query`
- `marker` in `query`
- `application_type` in `query`
### get_files_id_content
- Operation ID: `get_files_id_content`
- Route: `GET /files/{file_id}/content`
- Mode: READ
- Summary: Download file
- Parameters:
- `file_id` in `path` required
- `range` in `header`
- `boxapi` in `header`
- `version` in `query`
- `access_token` in `query`
### post_files_id_content
- Operation ID: `post_files_id_content`
- Route: `POST /files/{file_id}/content`
- Mode: WRITE
- Summary: Upload file version
- Parameters:
- `file_id` in `path` required
- `if-match` in `header`
- `fields` in `query`
- `content-md5` in `header`
- Body: JSON request body accepted.
### options_files_content
- Operation ID: `options_files_content`
- Route: `OPTIONS /files/content`
- Mode: READ
- Summary: Preflight check before upload
- Body: JSON request body accepted.
### post_files_content
- Operation ID: `post_files_content`
- Route: `POST /files/content`
- Mode: WRITE
- Summary: Upload file
- Parameters:
- `fields` in `query`
- `content-md5` in `header`
- Body: JSON request body accepted.
### post_files_upload_sessions
- Operation ID: `post_files_upload_sessions`
- Route: `POST /files/upload_sessions`
- Mode: WRITE
- Summary: Create upload session
- Body: JSON request body accepted.
### post_files_id_upload_sessions
- Operation ID: `post_files_id_upload_sessions`
- Route: `POST /files/{file_id}/upload_sessions`
- Mode: WRITE
- Summary: Create upload session for existing file
- Parameters:
- `file_id` in `path` required
- Body: JSON request body accepted.
### get_files_upload_sessions_id
- Operation ID: `get_files_upload_sessions_id`
- Route: `GET /files/upload_sessions/{upload_session_id}`
- Mode: READ
- Summary: Get upload session
- Parameters:
- `upload_session_id` in `path` required
### put_files_upload_sessions_id
- Operation ID: `put_files_upload_sessions_id`
- Route: `PUT /files/upload_sessions/{upload_session_id}`
- Mode: WRITE
- Summary: Upload part of file
- Parameters:
- `upload_session_id` in `path` required
- `digest` in `header` required
- `content-range` in `header` required
- Body: JSON request body accepted.
### delete_files_upload_sessions_id
- Operation ID: `delete_files_upload_sessions_id`
- Route: `DELETE /files/upload_sessions/{upload_session_id}`
- Mode: WRITE
- Summary: Remove upload session
- Parameters:
- `upload_session_id` in `path` required
### get_files_upload_sessions_id_parts
- Operation ID: `get_files_upload_sessions_id_parts`
- Route: `GET /files/upload_sessions/{upload_session_id}/parts`
- Mode: READ
- Summary: List parts
- Parameters:
- `upload_session_id` in `path` required
- `offset` in `query`
- `limit` in `query`
### post_files_upload_sessions_id_commit
- Operation ID: `post_files_upload_sessions_id_commit`
- Route: `POST /files/upload_sessions/{upload_session_id}/commit`
- Mode: WRITE
- Summary: Commit upload session
- Parameters:
- `upload_session_id` in `path` required
- `digest` in `header` required
- `if-match` in `header`
- `if-none-match` in `header`
- Body: JSON request body accepted.
### post_files_id_copy
- Operation ID: `post_files_id_copy`
- Route: `POST /files/{file_id}/copy`
- Mode: WRITE
- Summary: Copy file
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### get_files_id_thumbnail_id
- Operation ID: `get_files_id_thumbnail_id`
- Route: `GET /files/{file_id}/thumbnail.{extension}`
- Mode: READ
- Summary: Get file thumbnail
- Parameters:
- `file_id` in `path` required
- `extension` in `path` required
- `min_height` in `query`
- `min_width` in `query`
- `max_height` in `query`
- `max_width` in `query`
### get_files_id_collaborations
- Operation ID: `get_files_id_collaborations`
- Route: `GET /files/{file_id}/collaborations`
- Mode: READ
- Summary: List file collaborations
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- `limit` in `query`
- `marker` in `query`
### get_files_id_comments
- Operation ID: `get_files_id_comments`
- Route: `GET /files/{file_id}/comments`
- Mode: READ
- Summary: List file comments
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- `limit` in `query`
- `offset` in `query`
### get_files_id_tasks
- Operation ID: `get_files_id_tasks`
- Route: `GET /files/{file_id}/tasks`
- Mode: READ
- Summary: List tasks on file
- Parameters:
- `file_id` in `path` required
### get_files_id_trash
- Operation ID: `get_files_id_trash`
- Route: `GET /files/{file_id}/trash`
- Mode: READ
- Summary: Get trashed file
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
### delete_files_id_trash
- Operation ID: `delete_files_id_trash`
- Route: `DELETE /files/{file_id}/trash`
- Mode: WRITE
- Summary: Permanently remove file
- Parameters:
- `file_id` in `path` required
### get_files_id_versions
- Operation ID: `get_files_id_versions`
- Route: `GET /files/{file_id}/versions`
- Mode: READ
- Summary: List all file versions
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- `limit` in `query`
- `offset` in `query`
### get_files_id_versions_id
- Operation ID: `get_files_id_versions_id`
- Route: `GET /files/{file_id}/versions/{file_version_id}`
- Mode: READ
- Summary: Get file version
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- `file_version_id` in `path` required
### delete_files_id_versions_id
- Operation ID: `delete_files_id_versions_id`
- Route: `DELETE /files/{file_id}/versions/{file_version_id}`
- Mode: WRITE
- Summary: Remove file version
- Parameters:
- `file_id` in `path` required
- `file_version_id` in `path` required
- `if-match` in `header`
### put_files_id_versions_id
- Operation ID: `put_files_id_versions_id`
- Route: `PUT /files/{file_id}/versions/{file_version_id}`
- Mode: WRITE
- Summary: Restore file version
- Parameters:
- `file_id` in `path` required
- `file_version_id` in `path` required
- Body: JSON request body accepted.
### post_files_id_versions_current
- Operation ID: `post_files_id_versions_current`
- Route: `POST /files/{file_id}/versions/current`
- Mode: WRITE
- Summary: Promote file version
- Parameters:
- `file_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### get_files_id_metadata
- Operation ID: `get_files_id_metadata`
- Route: `GET /files/{file_id}/metadata`
- Mode: READ
- Summary: List metadata instances on file
- Parameters:
- `file_id` in `path` required
- `view` in `query`
### get_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `get_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `GET /files/{file_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: READ
- Summary: Get classification on file
- Parameters:
- `file_id` in `path` required
### post_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `post_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `POST /files/{file_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: WRITE
- Summary: Add classification to file
- Parameters:
- `file_id` in `path` required
- Body: JSON request body accepted.
### put_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `put_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `PUT /files/{file_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: WRITE
- Summary: Update classification on file
- Parameters:
- `file_id` in `path` required
- Body: JSON request body accepted.
### delete_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `delete_files_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `DELETE /files/{file_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: WRITE
- Summary: Remove classification from file
- Parameters:
- `file_id` in `path` required
### get_files_id_metadata_id_id
- Operation ID: `get_files_id_metadata_id_id`
- Route: `GET /files/{file_id}/metadata/{scope}/{template_key}`
- Mode: READ
- Summary: Get metadata instance on file
- Parameters:
- `file_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
- `view` in `query`
### post_files_id_metadata_id_id
- Operation ID: `post_files_id_metadata_id_id`
- Route: `POST /files/{file_id}/metadata/{scope}/{template_key}`
- Mode: WRITE
- Summary: Create metadata instance on file
- Parameters:
- `file_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
- Body: JSON request body accepted.
### put_files_id_metadata_id_id
- Operation ID: `put_files_id_metadata_id_id`
- Route: `PUT /files/{file_id}/metadata/{scope}/{template_key}`
- Mode: WRITE
- Summary: Update metadata instance on file
- Parameters:
- `file_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
- Body: JSON request body accepted.
### delete_files_id_metadata_id_id
- Operation ID: `delete_files_id_metadata_id_id`
- Route: `DELETE /files/{file_id}/metadata/{scope}/{template_key}`
- Mode: WRITE
- Summary: Remove metadata instance from file
- Parameters:
- `file_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
### get_files_id_metadata_global_box_skills_cards
- Operation ID: `get_files_id_metadata_global_box_skills_cards`
- Route: `GET /files/{file_id}/metadata/global/boxSkillsCards`
- Mode: READ
- Summary: List Box Skill cards on file
- Parameters:
- `file_id` in `path` required
### post_files_id_metadata_global_box_skills_cards
- Operation ID: `post_files_id_metadata_global_box_skills_cards`
- Route: `POST /files/{file_id}/metadata/global/boxSkillsCards`
- Mode: WRITE
- Summary: Create Box Skill cards on file
- Parameters:
- `file_id` in `path` required
- Body: JSON request body accepted.
### put_files_id_metadata_global_box_skills_cards
- Operation ID: `put_files_id_metadata_global_box_skills_cards`
- Route: `PUT /files/{file_id}/metadata/global/boxSkillsCards`
- Mode: WRITE
- Summary: Update Box Skill cards on file
- Parameters:
- `file_id` in `path` required
- Body: JSON request body accepted.
### delete_files_id_metadata_global_box_skills_cards
- Operation ID: `delete_files_id_metadata_global_box_skills_cards`
- Route: `DELETE /files/{file_id}/metadata/global/boxSkillsCards`
- Mode: WRITE
- Summary: Remove Box Skill cards from file
- Parameters:
- `file_id` in `path` required
### get_files_id_watermark
- Operation ID: `get_files_id_watermark`
- Route: `GET /files/{file_id}/watermark`
- Mode: READ
- Summary: Get watermark on file
- Parameters:
- `file_id` in `path` required
### put_files_id_watermark
- Operation ID: `put_files_id_watermark`
- Route: `PUT /files/{file_id}/watermark`
- Mode: WRITE
- Summary: Apply watermark to file
- Parameters:
- `file_id` in `path` required
- Body: JSON request body accepted.
### delete_files_id_watermark
- Operation ID: `delete_files_id_watermark`
- Route: `DELETE /files/{file_id}/watermark`
- Mode: WRITE
- Summary: Remove watermark from file
- Parameters:
- `file_id` in `path` required
### get_files_id_get_shared_link
- Operation ID: `get_files_id_get_shared_link`
- Route: `GET /files/{file_id}#get_shared_link`
- Mode: READ
- Summary: Get shared link for file
- Parameters:
- `file_id` in `path` required
- `fields` in `query` required
### put_files_id_add_shared_link
- Operation ID: `put_files_id_add_shared_link`
- Route: `PUT /files/{file_id}#add_shared_link`
- Mode: WRITE
- Summary: Add shared link to file
- Parameters:
- `file_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.
### put_files_id_update_shared_link
- Operation ID: `put_files_id_update_shared_link`
- Route: `PUT /files/{file_id}#update_shared_link`
- Mode: WRITE
- Summary: Update shared link on file
- Parameters:
- `file_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.
### put_files_id_remove_shared_link
- Operation ID: `put_files_id_remove_shared_link`
- Route: `PUT /files/{file_id}#remove_shared_link`
- Mode: WRITE
- Summary: Remove shared link from file
- Parameters:
- `file_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,40 @@
---
name: folder-locks-routes
description: Handle 3 OpenAPI operation(s) under /folder_locks for the folder locks route group.
---
# folder locks API Routes
Handle 3 OpenAPI operation(s) under /folder_locks for the folder locks route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_folder_locks
- Operation ID: `get_folder_locks`
- Route: `GET /folder_locks`
- Mode: READ
- Summary: List folder locks
- Parameters:
- `folder_id` in `query` required
### post_folder_locks
- Operation ID: `post_folder_locks`
- Route: `POST /folder_locks`
- Mode: WRITE
- Summary: Create folder lock
- Body: JSON request body accepted.
### delete_folder_locks_id
- Operation ID: `delete_folder_locks_id`
- Route: `DELETE /folder_locks/{folder_lock_id}`
- Mode: WRITE
- Summary: Delete folder lock
- Parameters:
- `folder_lock_id` in `path` required

325
skills/folders/SKILL.md Normal file
View File

@@ -0,0 +1,325 @@
---
name: folders-routes
description: Handle 28 OpenAPI operation(s) under /folders for the folders route group.
---
# folders API Routes
Handle 28 OpenAPI operation(s) under /folders for the folders route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_folders_id
- Operation ID: `get_folders_id`
- Route: `GET /folders/{folder_id}`
- Mode: READ
- Summary: Get folder information
- Parameters:
- `folder_id` in `path` required
- `fields` in `query`
- `if-none-match` in `header`
- `boxapi` in `header`
- `sort` in `query`
- `direction` in `query`
- `offset` in `query`
- `limit` in `query`
### post_folders_id
- Operation ID: `post_folders_id`
- Route: `POST /folders/{folder_id}`
- Mode: WRITE
- Summary: Restore folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### put_folders_id
- Operation ID: `put_folders_id`
- Route: `PUT /folders/{folder_id}`
- Mode: WRITE
- Summary: Update folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query`
- `if-match` in `header`
- Body: JSON request body accepted.
### delete_folders_id
- Operation ID: `delete_folders_id`
- Route: `DELETE /folders/{folder_id}`
- Mode: WRITE
- Summary: Delete folder
- Parameters:
- `folder_id` in `path` required
- `if-match` in `header`
- `recursive` in `query`
### get_folders_id_app_item_associations
- Operation ID: `get_folders_id_app_item_associations`
- Route: `GET /folders/{folder_id}/app_item_associations`
- Mode: READ
- Summary: List folder app item associations
- Parameters:
- `folder_id` in `path` required
- `limit` in `query`
- `marker` in `query`
- `application_type` in `query`
### get_folders_id_items
- Operation ID: `get_folders_id_items`
- Route: `GET /folders/{folder_id}/items`
- Mode: READ
- Summary: List items in folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query`
- `usemarker` in `query`
- `marker` in `query`
- `offset` in `query`
- `limit` in `query`
- `boxapi` in `header`
- `sort` in `query`
- `direction` in `query`
### post_folders
- Operation ID: `post_folders`
- Route: `POST /folders`
- Mode: WRITE
- Summary: Create folder
- Parameters:
- `fields` in `query`
- Body: JSON request body accepted.
### post_folders_id_copy
- Operation ID: `post_folders_id_copy`
- Route: `POST /folders/{folder_id}/copy`
- Mode: WRITE
- Summary: Copy folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### get_folders_id_collaborations
- Operation ID: `get_folders_id_collaborations`
- Route: `GET /folders/{folder_id}/collaborations`
- Mode: READ
- Summary: List folder collaborations
- Parameters:
- `folder_id` in `path` required
- `fields` in `query`
- `limit` in `query`
- `marker` in `query`
### get_folders_id_trash
- Operation ID: `get_folders_id_trash`
- Route: `GET /folders/{folder_id}/trash`
- Mode: READ
- Summary: Get trashed folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query`
### delete_folders_id_trash
- Operation ID: `delete_folders_id_trash`
- Route: `DELETE /folders/{folder_id}/trash`
- Mode: WRITE
- Summary: Permanently remove folder
- Parameters:
- `folder_id` in `path` required
### get_folders_id_metadata
- Operation ID: `get_folders_id_metadata`
- Route: `GET /folders/{folder_id}/metadata`
- Mode: READ
- Summary: List metadata instances on folder
- Parameters:
- `folder_id` in `path` required
- `view` in `query`
### get_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `get_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `GET /folders/{folder_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: READ
- Summary: Get classification on folder
- Parameters:
- `folder_id` in `path` required
### post_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `post_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `POST /folders/{folder_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: WRITE
- Summary: Add classification to folder
- Parameters:
- `folder_id` in `path` required
- Body: JSON request body accepted.
### put_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `put_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `PUT /folders/{folder_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: WRITE
- Summary: Update classification on folder
- Parameters:
- `folder_id` in `path` required
- Body: JSON request body accepted.
### delete_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo
- Operation ID: `delete_folders_id_metadata_enterprise_security_classification_6_vm_vochw_u_wo`
- Route: `DELETE /folders/{folder_id}/metadata/enterprise/securityClassification-6VMVochwUWo`
- Mode: WRITE
- Summary: Remove classification from folder
- Parameters:
- `folder_id` in `path` required
### get_folders_id_metadata_id_id
- Operation ID: `get_folders_id_metadata_id_id`
- Route: `GET /folders/{folder_id}/metadata/{scope}/{template_key}`
- Mode: READ
- Summary: Get metadata instance on folder
- Parameters:
- `folder_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
### post_folders_id_metadata_id_id
- Operation ID: `post_folders_id_metadata_id_id`
- Route: `POST /folders/{folder_id}/metadata/{scope}/{template_key}`
- Mode: WRITE
- Summary: Create metadata instance on folder
- Parameters:
- `folder_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
- Body: JSON request body accepted.
### put_folders_id_metadata_id_id
- Operation ID: `put_folders_id_metadata_id_id`
- Route: `PUT /folders/{folder_id}/metadata/{scope}/{template_key}`
- Mode: WRITE
- Summary: Update metadata instance on folder
- Parameters:
- `folder_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
- Body: JSON request body accepted.
### delete_folders_id_metadata_id_id
- Operation ID: `delete_folders_id_metadata_id_id`
- Route: `DELETE /folders/{folder_id}/metadata/{scope}/{template_key}`
- Mode: WRITE
- Summary: Remove metadata instance from folder
- Parameters:
- `folder_id` in `path` required
- `scope` in `path` required
- `template_key` in `path` required
### get_folders_trash_items
- Operation ID: `get_folders_trash_items`
- Route: `GET /folders/trash/items`
- Mode: READ
- Summary: List trashed items
- Parameters:
- `fields` in `query`
- `limit` in `query`
- `offset` in `query`
- `usemarker` in `query`
- `marker` in `query`
- `direction` in `query`
- `sort` in `query`
### get_folders_id_watermark
- Operation ID: `get_folders_id_watermark`
- Route: `GET /folders/{folder_id}/watermark`
- Mode: READ
- Summary: Get watermark for folder
- Parameters:
- `folder_id` in `path` required
### put_folders_id_watermark
- Operation ID: `put_folders_id_watermark`
- Route: `PUT /folders/{folder_id}/watermark`
- Mode: WRITE
- Summary: Apply watermark to folder
- Parameters:
- `folder_id` in `path` required
- Body: JSON request body accepted.
### delete_folders_id_watermark
- Operation ID: `delete_folders_id_watermark`
- Route: `DELETE /folders/{folder_id}/watermark`
- Mode: WRITE
- Summary: Remove watermark from folder
- Parameters:
- `folder_id` in `path` required
### get_folders_id_get_shared_link
- Operation ID: `get_folders_id_get_shared_link`
- Route: `GET /folders/{folder_id}#get_shared_link`
- Mode: READ
- Summary: Get shared link for folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query` required
### put_folders_id_add_shared_link
- Operation ID: `put_folders_id_add_shared_link`
- Route: `PUT /folders/{folder_id}#add_shared_link`
- Mode: WRITE
- Summary: Add shared link to folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.
### put_folders_id_update_shared_link
- Operation ID: `put_folders_id_update_shared_link`
- Route: `PUT /folders/{folder_id}#update_shared_link`
- Mode: WRITE
- Summary: Update shared link on folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.
### put_folders_id_remove_shared_link
- Operation ID: `put_folders_id_remove_shared_link`
- Route: `PUT /folders/{folder_id}#remove_shared_link`
- Mode: WRITE
- Summary: Remove shared link from folder
- Parameters:
- `folder_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,54 @@
---
name: group-memberships-routes
description: Handle 4 OpenAPI operation(s) under /group_memberships for the group memberships route group.
---
# group memberships API Routes
Handle 4 OpenAPI operation(s) under /group_memberships for the group memberships route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_group_memberships
- Operation ID: `post_group_memberships`
- Route: `POST /group_memberships`
- Mode: WRITE
- Summary: Add user to group
- Parameters:
- `fields` in `query`
- Body: JSON request body accepted.
### get_group_memberships_id
- Operation ID: `get_group_memberships_id`
- Route: `GET /group_memberships/{group_membership_id}`
- Mode: READ
- Summary: Get group membership
- Parameters:
- `group_membership_id` in `path` required
- `fields` in `query`
### put_group_memberships_id
- Operation ID: `put_group_memberships_id`
- Route: `PUT /group_memberships/{group_membership_id}`
- Mode: WRITE
- Summary: Update group membership
- Parameters:
- `group_membership_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### delete_group_memberships_id
- Operation ID: `delete_group_memberships_id`
- Route: `DELETE /group_memberships/{group_membership_id}`
- Mode: WRITE
- Summary: Remove user from group
- Parameters:
- `group_membership_id` in `path` required

96
skills/groups/SKILL.md Normal file
View File

@@ -0,0 +1,96 @@
---
name: groups-routes
description: Handle 8 OpenAPI operation(s) under /groups for the groups route group.
---
# groups API Routes
Handle 8 OpenAPI operation(s) under /groups for the groups route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_groups
- Operation ID: `get_groups`
- Route: `GET /groups`
- Mode: READ
- Summary: List groups for enterprise
- Parameters:
- `filter_term` in `query`
- `fields` in `query`
- `limit` in `query`
- `offset` in `query`
### post_groups
- Operation ID: `post_groups`
- Route: `POST /groups`
- Mode: WRITE
- Summary: Create group
- Parameters:
- `fields` in `query`
- Body: JSON request body accepted.
### post_groups_terminate_sessions
- Operation ID: `post_groups_terminate_sessions`
- Route: `POST /groups/terminate_sessions`
- Mode: WRITE
- Summary: Create jobs to terminate user group session
- Body: JSON request body accepted.
### get_groups_id
- Operation ID: `get_groups_id`
- Route: `GET /groups/{group_id}`
- Mode: READ
- Summary: Get group
- Parameters:
- `group_id` in `path` required
- `fields` in `query`
### put_groups_id
- Operation ID: `put_groups_id`
- Route: `PUT /groups/{group_id}`
- Mode: WRITE
- Summary: Update group
- Parameters:
- `group_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### delete_groups_id
- Operation ID: `delete_groups_id`
- Route: `DELETE /groups/{group_id}`
- Mode: WRITE
- Summary: Remove group
- Parameters:
- `group_id` in `path` required
### get_groups_id_memberships
- Operation ID: `get_groups_id_memberships`
- Route: `GET /groups/{group_id}/memberships`
- Mode: READ
- Summary: List members of group
- Parameters:
- `group_id` in `path` required
- `limit` in `query`
- `offset` in `query`
### get_groups_id_collaborations
- Operation ID: `get_groups_id_collaborations`
- Route: `GET /groups/{group_id}/collaborations`
- Mode: READ
- Summary: List group collaborations
- Parameters:
- `group_id` in `path` required
- `limit` in `query`
- `offset` in `query`

View File

@@ -0,0 +1,95 @@
---
name: integration-mappings-routes
description: Handle 8 OpenAPI operation(s) under /integration_mappings for the integration mappings route group.
---
# integration mappings API Routes
Handle 8 OpenAPI operation(s) under /integration_mappings for the integration mappings route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_integration_mappings_slack
- Operation ID: `get_integration_mappings_slack`
- Route: `GET /integration_mappings/slack`
- Mode: READ
- Summary: List Slack integration mappings
- Parameters:
- `marker` in `query`
- `limit` in `query`
- `partner_item_type` in `query`
- `partner_item_id` in `query`
- `box_item_id` in `query`
- `box_item_type` in `query`
- `is_manually_created` in `query`
### post_integration_mappings_slack
- Operation ID: `post_integration_mappings_slack`
- Route: `POST /integration_mappings/slack`
- Mode: WRITE
- Summary: Create Slack integration mapping
- Body: JSON request body accepted.
### put_integration_mappings_slack_id
- Operation ID: `put_integration_mappings_slack_id`
- Route: `PUT /integration_mappings/slack/{integration_mapping_id}`
- Mode: WRITE
- Summary: Update Slack integration mapping
- Parameters:
- `integration_mapping_id` in `path` required
- Body: JSON request body accepted.
### delete_integration_mappings_slack_id
- Operation ID: `delete_integration_mappings_slack_id`
- Route: `DELETE /integration_mappings/slack/{integration_mapping_id}`
- Mode: WRITE
- Summary: Delete Slack integration mapping
- Parameters:
- `integration_mapping_id` in `path` required
### get_integration_mappings_teams
- Operation ID: `get_integration_mappings_teams`
- Route: `GET /integration_mappings/teams`
- Mode: READ
- Summary: List Teams integration mappings
- Parameters:
- `partner_item_type` in `query`
- `partner_item_id` in `query`
- `box_item_id` in `query`
- `box_item_type` in `query`
### post_integration_mappings_teams
- Operation ID: `post_integration_mappings_teams`
- Route: `POST /integration_mappings/teams`
- Mode: WRITE
- Summary: Create Teams integration mapping
- Body: JSON request body accepted.
### put_integration_mappings_teams_id
- Operation ID: `put_integration_mappings_teams_id`
- Route: `PUT /integration_mappings/teams/{integration_mapping_id}`
- Mode: WRITE
- Summary: Update Teams integration mapping
- Parameters:
- `integration_mapping_id` in `path` required
- Body: JSON request body accepted.
### delete_integration_mappings_teams_id
- Operation ID: `delete_integration_mappings_teams_id`
- Route: `DELETE /integration_mappings/teams/{integration_mapping_id}`
- Mode: WRITE
- Summary: Delete Teams integration mapping
- Parameters:
- `integration_mapping_id` in `path` required

34
skills/invites/SKILL.md Normal file
View File

@@ -0,0 +1,34 @@
---
name: invites-routes
description: Handle 2 OpenAPI operation(s) under /invites for the invites route group.
---
# invites API Routes
Handle 2 OpenAPI operation(s) under /invites for the invites route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_invites
- Operation ID: `post_invites`
- Route: `POST /invites`
- Mode: WRITE
- Summary: Create user invite
- Parameters:
- `fields` in `query`
- Body: JSON request body accepted.
### get_invites_id
- Operation ID: `get_invites_id`
- Route: `GET /invites/{invite_id}`
- Mode: READ
- Summary: Get user invite status
- Parameters:
- `invite_id` in `path` required
- `fields` in `query`

View File

@@ -0,0 +1,62 @@
---
name: legal-hold-policies-routes
description: Handle 5 OpenAPI operation(s) under /legal_hold_policies for the legal hold policies route group.
---
# legal hold policies API Routes
Handle 5 OpenAPI operation(s) under /legal_hold_policies for the legal hold policies route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_legal_hold_policies
- Operation ID: `get_legal_hold_policies`
- Route: `GET /legal_hold_policies`
- Mode: READ
- Summary: List all legal hold policies
- Parameters:
- `policy_name` in `query`
- `fields` in `query`
- `marker` in `query`
- `limit` in `query`
### post_legal_hold_policies
- Operation ID: `post_legal_hold_policies`
- Route: `POST /legal_hold_policies`
- Mode: WRITE
- Summary: Create legal hold policy
- Body: JSON request body accepted.
### get_legal_hold_policies_id
- Operation ID: `get_legal_hold_policies_id`
- Route: `GET /legal_hold_policies/{legal_hold_policy_id}`
- Mode: READ
- Summary: Get legal hold policy
- Parameters:
- `legal_hold_policy_id` in `path` required
### put_legal_hold_policies_id
- Operation ID: `put_legal_hold_policies_id`
- Route: `PUT /legal_hold_policies/{legal_hold_policy_id}`
- Mode: WRITE
- Summary: Update legal hold policy
- Parameters:
- `legal_hold_policy_id` in `path` required
- Body: JSON request body accepted.
### delete_legal_hold_policies_id
- Operation ID: `delete_legal_hold_policies_id`
- Route: `DELETE /legal_hold_policies/{legal_hold_policy_id}`
- Mode: WRITE
- Summary: Remove legal hold policy
- Parameters:
- `legal_hold_policy_id` in `path` required

View File

@@ -0,0 +1,78 @@
---
name: legal-hold-policy-assignments-routes
description: Handle 6 OpenAPI operation(s) under /legal_hold_policy_assignments for the legal hold policy assignments route group.
---
# legal hold policy assignments API Routes
Handle 6 OpenAPI operation(s) under /legal_hold_policy_assignments for the legal hold policy assignments route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_legal_hold_policy_assignments
- Operation ID: `get_legal_hold_policy_assignments`
- Route: `GET /legal_hold_policy_assignments`
- Mode: READ
- Summary: List legal hold policy assignments
- Parameters:
- `policy_id` in `query` required
- `assign_to_type` in `query`
- `assign_to_id` in `query`
- `marker` in `query`
- `limit` in `query`
- `fields` in `query`
### post_legal_hold_policy_assignments
- Operation ID: `post_legal_hold_policy_assignments`
- Route: `POST /legal_hold_policy_assignments`
- Mode: WRITE
- Summary: Assign legal hold policy
- Body: JSON request body accepted.
### get_legal_hold_policy_assignments_id
- Operation ID: `get_legal_hold_policy_assignments_id`
- Route: `GET /legal_hold_policy_assignments/{legal_hold_policy_assignment_id}`
- Mode: READ
- Summary: Get legal hold policy assignment
- Parameters:
- `legal_hold_policy_assignment_id` in `path` required
### delete_legal_hold_policy_assignments_id
- Operation ID: `delete_legal_hold_policy_assignments_id`
- Route: `DELETE /legal_hold_policy_assignments/{legal_hold_policy_assignment_id}`
- Mode: WRITE
- Summary: Unassign legal hold policy
- Parameters:
- `legal_hold_policy_assignment_id` in `path` required
### get_legal_hold_policy_assignments_id_files_on_hold
- Operation ID: `get_legal_hold_policy_assignments_id_files_on_hold`
- Route: `GET /legal_hold_policy_assignments/{legal_hold_policy_assignment_id}/files_on_hold`
- Mode: READ
- Summary: List files with current file versions for legal hold policy assignment
- Parameters:
- `legal_hold_policy_assignment_id` in `path` required
- `marker` in `query`
- `limit` in `query`
- `fields` in `query`
### get_legal_hold_policy_assignments_id_file_versions_on_hold
- Operation ID: `get_legal_hold_policy_assignments_id_file_versions_on_hold`
- Route: `GET /legal_hold_policy_assignments/{legal_hold_policy_assignment_id}/file_versions_on_hold`
- Mode: READ
- Summary: List previous file versions for legal hold policy assignment
- Parameters:
- `legal_hold_policy_assignment_id` in `path` required
- `marker` in `query`
- `limit` in `query`
- `fields` in `query`

View File

@@ -0,0 +1,62 @@
---
name: metadata-cascade-policies-routes
description: Handle 5 OpenAPI operation(s) under /metadata_cascade_policies for the metadata cascade policies route group.
---
# metadata cascade policies API Routes
Handle 5 OpenAPI operation(s) under /metadata_cascade_policies for the metadata cascade policies route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_metadata_cascade_policies
- Operation ID: `get_metadata_cascade_policies`
- Route: `GET /metadata_cascade_policies`
- Mode: READ
- Summary: List metadata cascade policies
- Parameters:
- `folder_id` in `query` required
- `owner_enterprise_id` in `query`
- `marker` in `query`
- `offset` in `query`
### post_metadata_cascade_policies
- Operation ID: `post_metadata_cascade_policies`
- Route: `POST /metadata_cascade_policies`
- Mode: WRITE
- Summary: Create metadata cascade policy
- Body: JSON request body accepted.
### get_metadata_cascade_policies_id
- Operation ID: `get_metadata_cascade_policies_id`
- Route: `GET /metadata_cascade_policies/{metadata_cascade_policy_id}`
- Mode: READ
- Summary: Get metadata cascade policy
- Parameters:
- `metadata_cascade_policy_id` in `path` required
### delete_metadata_cascade_policies_id
- Operation ID: `delete_metadata_cascade_policies_id`
- Route: `DELETE /metadata_cascade_policies/{metadata_cascade_policy_id}`
- Mode: WRITE
- Summary: Remove metadata cascade policy
- Parameters:
- `metadata_cascade_policy_id` in `path` required
### post_metadata_cascade_policies_id_apply
- Operation ID: `post_metadata_cascade_policies_id_apply`
- Route: `POST /metadata_cascade_policies/{metadata_cascade_policy_id}/apply`
- Mode: WRITE
- Summary: Force-apply metadata cascade policy to folder
- Parameters:
- `metadata_cascade_policy_id` in `path` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,22 @@
---
name: metadata-queries-routes
description: Handle 1 OpenAPI operation(s) under /metadata_queries/execute_read for the metadata queries route group.
---
# metadata queries API Routes
Handle 1 OpenAPI operation(s) under /metadata_queries/execute_read for the metadata queries route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_metadata_queries_execute_read
- Operation ID: `post_metadata_queries_execute_read`
- Route: `POST /metadata_queries/execute_read`
- Mode: WRITE
- Summary: Query files/folders by metadata
- Body: JSON request body accepted.

View File

@@ -0,0 +1,170 @@
---
name: metadata-taxonomies-routes
description: Handle 14 OpenAPI operation(s) under /metadata_taxonomies for the metadata taxonomies route group.
---
# metadata taxonomies API Routes
Handle 14 OpenAPI operation(s) under /metadata_taxonomies for the metadata taxonomies route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_metadata_taxonomies
- Operation ID: `post_metadata_taxonomies`
- Route: `POST /metadata_taxonomies`
- Mode: WRITE
- Summary: Create metadata taxonomy
- Body: JSON request body accepted.
### get_metadata_taxonomies_id
- Operation ID: `get_metadata_taxonomies_id`
- Route: `GET /metadata_taxonomies/{namespace}`
- Mode: READ
- Summary: Get metadata taxonomies for namespace
- Parameters:
- `namespace` in `path` required
- `marker` in `query`
- `limit` in `query`
### get_metadata_taxonomies_id_id
- Operation ID: `get_metadata_taxonomies_id_id`
- Route: `GET /metadata_taxonomies/{namespace}/{taxonomy_key}`
- Mode: READ
- Summary: Get metadata taxonomy by taxonomy key
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
### patch_metadata_taxonomies_id_id
- Operation ID: `patch_metadata_taxonomies_id_id`
- Route: `PATCH /metadata_taxonomies/{namespace}/{taxonomy_key}`
- Mode: WRITE
- Summary: Update metadata taxonomy
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- Body: JSON request body accepted.
### delete_metadata_taxonomies_id_id
- Operation ID: `delete_metadata_taxonomies_id_id`
- Route: `DELETE /metadata_taxonomies/{namespace}/{taxonomy_key}`
- Mode: WRITE
- Summary: Remove metadata taxonomy
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
### post_metadata_taxonomies_id_id_levels
- Operation ID: `post_metadata_taxonomies_id_id_levels`
- Route: `POST /metadata_taxonomies/{namespace}/{taxonomy_key}/levels`
- Mode: WRITE
- Summary: Create metadata taxonomy levels
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- Body: JSON request body accepted.
### patch_metadata_taxonomies_id_id_levels_id
- Operation ID: `patch_metadata_taxonomies_id_id_levels_id`
- Route: `PATCH /metadata_taxonomies/{namespace}/{taxonomy_key}/levels/{level_index}`
- Mode: WRITE
- Summary: Update metadata taxonomy level
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- `level_index` in `path` required
- Body: JSON request body accepted.
### post_metadata_taxonomies_id_id_levels_append
- Operation ID: `post_metadata_taxonomies_id_id_levels_append`
- Route: `POST /metadata_taxonomies/{namespace}/{taxonomy_key}/levels:append`
- Mode: WRITE
- Summary: Add metadata taxonomy level
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- Body: JSON request body accepted.
### post_metadata_taxonomies_id_id_levels_trim
- Operation ID: `post_metadata_taxonomies_id_id_levels_trim`
- Route: `POST /metadata_taxonomies/{namespace}/{taxonomy_key}/levels:trim`
- Mode: WRITE
- Summary: Delete metadata taxonomy level
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
### get_metadata_taxonomies_id_id_nodes
- Operation ID: `get_metadata_taxonomies_id_id_nodes`
- Route: `GET /metadata_taxonomies/{namespace}/{taxonomy_key}/nodes`
- Mode: READ
- Summary: List metadata taxonomy nodes
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- `level` in `query`
- `parent` in `query`
- `ancestor` in `query`
- `query` in `query`
- `include-total-result-count` in `query`
- `marker` in `query`
- `limit` in `query`
### post_metadata_taxonomies_id_id_nodes
- Operation ID: `post_metadata_taxonomies_id_id_nodes`
- Route: `POST /metadata_taxonomies/{namespace}/{taxonomy_key}/nodes`
- Mode: WRITE
- Summary: Create metadata taxonomy node
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- Body: JSON request body accepted.
### get_metadata_taxonomies_id_id_nodes_id
- Operation ID: `get_metadata_taxonomies_id_id_nodes_id`
- Route: `GET /metadata_taxonomies/{namespace}/{taxonomy_key}/nodes/{node_id}`
- Mode: READ
- Summary: Get metadata taxonomy node by ID
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- `node_id` in `path` required
### patch_metadata_taxonomies_id_id_nodes_id
- Operation ID: `patch_metadata_taxonomies_id_id_nodes_id`
- Route: `PATCH /metadata_taxonomies/{namespace}/{taxonomy_key}/nodes/{node_id}`
- Mode: WRITE
- Summary: Update metadata taxonomy node
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- `node_id` in `path` required
- Body: JSON request body accepted.
### delete_metadata_taxonomies_id_id_nodes_id
- Operation ID: `delete_metadata_taxonomies_id_id_nodes_id`
- Route: `DELETE /metadata_taxonomies/{namespace}/{taxonomy_key}/nodes/{node_id}`
- Mode: WRITE
- Summary: Remove metadata taxonomy node
- Parameters:
- `namespace` in `path` required
- `taxonomy_key` in `path` required
- `node_id` in `path` required

View File

@@ -0,0 +1,143 @@
---
name: metadata-templates-routes
description: Handle 13 OpenAPI operation(s) under /metadata_templates for the metadata templates route group.
---
# metadata templates API Routes
Handle 13 OpenAPI operation(s) under /metadata_templates for the metadata templates route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_metadata_templates
- Operation ID: `get_metadata_templates`
- Route: `GET /metadata_templates`
- Mode: READ
- Summary: Find metadata template by instance ID
- Parameters:
- `metadata_instance_id` in `query` required
- `marker` in `query`
- `limit` in `query`
### get_metadata_templates_enterprise_security_classification_6_vm_vochw_u_wo_schema
- Operation ID: `get_metadata_templates_enterprise_security_classification_6_vm_vochw_u_wo_schema`
- Route: `GET /metadata_templates/enterprise/securityClassification-6VMVochwUWo/schema`
- Mode: READ
- Summary: List all classifications
### put_metadata_templates_enterprise_security_classification_6_vm_vochw_u_wo_schema
- Operation ID: `put_metadata_templates_enterprise_security_classification_6_vm_vochw_u_wo_schema`
- Route: `PUT /metadata_templates/enterprise/securityClassification-6VMVochwUWo/schema#add`
- Mode: WRITE
- Summary: Add classification
- Body: JSON request body accepted.
### put_metadata_templates_enterprise_security_classification_6_vm_vochw_u_wo_sche_2
- Operation ID: `put_metadata_templates_enterprise_security_classification_6_vm_vochw_u_wo_sche_2`
- Route: `PUT /metadata_templates/enterprise/securityClassification-6VMVochwUWo/schema#update`
- Mode: WRITE
- Summary: Update classification
- Body: JSON request body accepted.
### get_metadata_templates_id_id_schema
- Operation ID: `get_metadata_templates_id_id_schema`
- Route: `GET /metadata_templates/{scope}/{template_key}/schema`
- Mode: READ
- Summary: Get metadata template by name
- Parameters:
- `scope` in `path` required
- `template_key` in `path` required
### put_metadata_templates_id_id_schema
- Operation ID: `put_metadata_templates_id_id_schema`
- Route: `PUT /metadata_templates/{scope}/{template_key}/schema`
- Mode: WRITE
- Summary: Update metadata template
- Parameters:
- `scope` in `path` required
- `template_key` in `path` required
- Body: JSON request body accepted.
### delete_metadata_templates_id_id_schema
- Operation ID: `delete_metadata_templates_id_id_schema`
- Route: `DELETE /metadata_templates/{scope}/{template_key}/schema`
- Mode: WRITE
- Summary: Remove metadata template
- Parameters:
- `scope` in `path` required
- `template_key` in `path` required
### get_metadata_templates_id
- Operation ID: `get_metadata_templates_id`
- Route: `GET /metadata_templates/{template_id}`
- Mode: READ
- Summary: Get metadata template by ID
- Parameters:
- `template_id` in `path` required
### get_metadata_templates_global
- Operation ID: `get_metadata_templates_global`
- Route: `GET /metadata_templates/global`
- Mode: READ
- Summary: List all global metadata templates
- Parameters:
- `marker` in `query`
- `limit` in `query`
### get_metadata_templates_enterprise
- Operation ID: `get_metadata_templates_enterprise`
- Route: `GET /metadata_templates/enterprise`
- Mode: READ
- Summary: List all metadata templates for enterprise
- Parameters:
- `marker` in `query`
- `limit` in `query`
### post_metadata_templates_schema
- Operation ID: `post_metadata_templates_schema`
- Route: `POST /metadata_templates/schema`
- Mode: WRITE
- Summary: Create metadata template
- Body: JSON request body accepted.
### post_metadata_templates_schema_classifications
- Operation ID: `post_metadata_templates_schema_classifications`
- Route: `POST /metadata_templates/schema#classifications`
- Mode: WRITE
- Summary: Add initial classifications
- Body: JSON request body accepted.
### get_metadata_templates_id_id_fields_id_options
- Operation ID: `get_metadata_templates_id_id_fields_id_options`
- Route: `GET /metadata_templates/{namespace}/{template_key}/fields/{field_key}/options`
- Mode: READ
- Summary: List metadata template's options for taxonomy field
- Parameters:
- `namespace` in `path` required
- `template_key` in `path` required
- `field_key` in `path` required
- `level` in `query`
- `parent` in `query`
- `ancestor` in `query`
- `query` in `query`
- `include-total-result-count` in `query`
- `only-selectable-options` in `query`
- `marker` in `query`
- `limit` in `query`

38
skills/oauth2/SKILL.md Normal file
View File

@@ -0,0 +1,38 @@
---
name: oauth2-routes
description: Handle 3 OpenAPI operation(s) under /oauth2 for the oauth2 route group.
---
# oauth2 API Routes
Handle 3 OpenAPI operation(s) under /oauth2 for the oauth2 route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_oauth2_token
- Operation ID: `post_oauth2_token`
- Route: `POST /oauth2/token`
- Mode: WRITE
- Summary: Request access token
- Body: JSON request body accepted.
### post_oauth2_token_refresh
- Operation ID: `post_oauth2_token_refresh`
- Route: `POST /oauth2/token#refresh`
- Mode: WRITE
- Summary: Refresh access token
- Body: JSON request body accepted.
### post_oauth2_revoke
- Operation ID: `post_oauth2_revoke`
- Route: `POST /oauth2/revoke`
- Mode: WRITE
- Summary: Revoke access token
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: recent-items-routes
description: Handle 1 OpenAPI operation(s) under /recent_items for the recent items route group.
---
# recent items API Routes
Handle 1 OpenAPI operation(s) under /recent_items for the recent items route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_recent_items
- Operation ID: `get_recent_items`
- Route: `GET /recent_items`
- Mode: READ
- Summary: List recently accessed items
- Parameters:
- `fields` in `query`
- `limit` in `query`
- `marker` in `query`

View File

@@ -0,0 +1,78 @@
---
name: retention-policies-routes
description: Handle 6 OpenAPI operation(s) under /retention_policies for the retention policies route group.
---
# retention policies API Routes
Handle 6 OpenAPI operation(s) under /retention_policies for the retention policies route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_retention_policies
- Operation ID: `get_retention_policies`
- Route: `GET /retention_policies`
- Mode: READ
- Summary: List retention policies
- Parameters:
- `policy_name` in `query`
- `policy_type` in `query`
- `created_by_user_id` in `query`
- `fields` in `query`
- `limit` in `query`
- `marker` in `query`
### post_retention_policies
- Operation ID: `post_retention_policies`
- Route: `POST /retention_policies`
- Mode: WRITE
- Summary: Create retention policy
- Body: JSON request body accepted.
### get_retention_policies_id
- Operation ID: `get_retention_policies_id`
- Route: `GET /retention_policies/{retention_policy_id}`
- Mode: READ
- Summary: Get retention policy
- Parameters:
- `retention_policy_id` in `path` required
- `fields` in `query`
### put_retention_policies_id
- Operation ID: `put_retention_policies_id`
- Route: `PUT /retention_policies/{retention_policy_id}`
- Mode: WRITE
- Summary: Update retention policy
- Parameters:
- `retention_policy_id` in `path` required
- Body: JSON request body accepted.
### delete_retention_policies_id
- Operation ID: `delete_retention_policies_id`
- Route: `DELETE /retention_policies/{retention_policy_id}`
- Mode: WRITE
- Summary: Delete retention policy
- Parameters:
- `retention_policy_id` in `path` required
### get_retention_policies_id_assignments
- Operation ID: `get_retention_policies_id_assignments`
- Route: `GET /retention_policies/{retention_policy_id}/assignments`
- Mode: READ
- Summary: List retention policy assignments
- Parameters:
- `retention_policy_id` in `path` required
- `type` in `query`
- `fields` in `query`
- `marker` in `query`
- `limit` in `query`

View File

@@ -0,0 +1,63 @@
---
name: retention-policy-assignments-routes
description: Handle 5 OpenAPI operation(s) under /retention_policy_assignments for the retention policy assignments route group.
---
# retention policy assignments API Routes
Handle 5 OpenAPI operation(s) under /retention_policy_assignments for the retention policy assignments route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_retention_policy_assignments
- Operation ID: `post_retention_policy_assignments`
- Route: `POST /retention_policy_assignments`
- Mode: WRITE
- Summary: Assign retention policy
- Body: JSON request body accepted.
### get_retention_policy_assignments_id
- Operation ID: `get_retention_policy_assignments_id`
- Route: `GET /retention_policy_assignments/{retention_policy_assignment_id}`
- Mode: READ
- Summary: Get retention policy assignment
- Parameters:
- `retention_policy_assignment_id` in `path` required
- `fields` in `query`
### delete_retention_policy_assignments_id
- Operation ID: `delete_retention_policy_assignments_id`
- Route: `DELETE /retention_policy_assignments/{retention_policy_assignment_id}`
- Mode: WRITE
- Summary: Remove retention policy assignment
- Parameters:
- `retention_policy_assignment_id` in `path` required
### get_retention_policy_assignments_id_files_under_retention
- Operation ID: `get_retention_policy_assignments_id_files_under_retention`
- Route: `GET /retention_policy_assignments/{retention_policy_assignment_id}/files_under_retention`
- Mode: READ
- Summary: Get files under retention
- Parameters:
- `retention_policy_assignment_id` in `path` required
- `marker` in `query`
- `limit` in `query`
### get_retention_policy_assignments_id_file_versions_under_retention
- Operation ID: `get_retention_policy_assignments_id_file_versions_under_retention`
- Route: `GET /retention_policy_assignments/{retention_policy_assignment_id}/file_versions_under_retention`
- Mode: READ
- Summary: Get file versions under retention
- Parameters:
- `retention_policy_assignment_id` in `path` required
- `marker` in `query`
- `limit` in `query`

43
skills/search/SKILL.md Normal file
View File

@@ -0,0 +1,43 @@
---
name: search-routes
description: Handle 1 OpenAPI operation(s) under /search for the search route group.
---
# search API Routes
Handle 1 OpenAPI operation(s) under /search for the search route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_search
- Operation ID: `get_search`
- Route: `GET /search`
- Mode: READ
- Summary: Search for content
- Parameters:
- `query` in `query`
- `scope` in `query`
- `file_extensions` in `query`
- `created_at_range` in `query`
- `updated_at_range` in `query`
- `size_range` in `query`
- `owner_user_ids` in `query`
- `recent_updater_user_ids` in `query`
- `ancestor_folder_ids` in `query`
- `content_types` in `query`
- `type` in `query`
- `trash_content` in `query`
- `mdfilters` in `query`
- `sort` in `query`
- `direction` in `query`
- `limit` in `query`
- `include_recent_shared_links` in `query`
- `fields` in `query`
- `offset` in `query`
- `deleted_user_ids` in `query`
- `deleted_at_range` in `query`

View File

@@ -0,0 +1,23 @@
---
name: shared-items-app-items-routes
description: Handle 1 OpenAPI operation(s) under /shared_items#app_items for the shared items app items route group.
---
# shared items app items API Routes
Handle 1 OpenAPI operation(s) under /shared_items#app_items for the shared items app items route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shared_items_app_items
- Operation ID: `get_shared_items_app_items`
- Route: `GET /shared_items#app_items`
- Mode: READ
- Summary: Find app item for shared link
- Parameters:
- `boxapi` in `header` required

View File

@@ -0,0 +1,25 @@
---
name: shared-items-folders-routes
description: Handle 1 OpenAPI operation(s) under /shared_items#folders for the shared items folders route group.
---
# shared items folders API Routes
Handle 1 OpenAPI operation(s) under /shared_items#folders for the shared items folders route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shared_items_folders
- Operation ID: `get_shared_items_folders`
- Route: `GET /shared_items#folders`
- Mode: READ
- Summary: Find folder for shared link
- Parameters:
- `if-none-match` in `header`
- `fields` in `query`
- `boxapi` in `header` required

View File

@@ -0,0 +1,25 @@
---
name: shared-items-web-links-routes
description: Handle 1 OpenAPI operation(s) under /shared_items#web_links for the shared items web links route group.
---
# shared items web links API Routes
Handle 1 OpenAPI operation(s) under /shared_items#web_links for the shared items web links route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shared_items_web_links
- Operation ID: `get_shared_items_web_links`
- Route: `GET /shared_items#web_links`
- Mode: READ
- Summary: Find web link for shared link
- Parameters:
- `if-none-match` in `header`
- `fields` in `query`
- `boxapi` in `header` required

View File

@@ -0,0 +1,25 @@
---
name: shared-items-routes
description: Handle 1 OpenAPI operation(s) under /shared_items for the shared items route group.
---
# shared items API Routes
Handle 1 OpenAPI operation(s) under /shared_items for the shared items route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shared_items
- Operation ID: `get_shared_items`
- Route: `GET /shared_items`
- Mode: READ
- Summary: Find file for shared link
- Parameters:
- `if-none-match` in `header`
- `fields` in `query`
- `boxapi` in `header` required

View File

@@ -0,0 +1,42 @@
---
name: shield-information-barrier-reports-routes
description: Handle 3 OpenAPI operation(s) under /shield_information_barrier_reports for the shield information barrier reports route group.
---
# shield information barrier reports API Routes
Handle 3 OpenAPI operation(s) under /shield_information_barrier_reports for the shield information barrier reports route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shield_information_barrier_reports
- Operation ID: `get_shield_information_barrier_reports`
- Route: `GET /shield_information_barrier_reports`
- Mode: READ
- Summary: List shield information barrier reports
- Parameters:
- `shield_information_barrier_id` in `query` required
- `marker` in `query`
- `limit` in `query`
### post_shield_information_barrier_reports
- Operation ID: `post_shield_information_barrier_reports`
- Route: `POST /shield_information_barrier_reports`
- Mode: WRITE
- Summary: Create shield information barrier report
- Body: JSON request body accepted.
### get_shield_information_barrier_reports_id
- Operation ID: `get_shield_information_barrier_reports_id`
- Route: `GET /shield_information_barrier_reports/{shield_information_barrier_report_id}`
- Mode: READ
- Summary: Get shield information barrier report by ID
- Parameters:
- `shield_information_barrier_report_id` in `path` required

View File

@@ -0,0 +1,51 @@
---
name: shield-information-barrier-segment-members-routes
description: Handle 4 OpenAPI operation(s) under /shield_information_barrier_segment_members for the shield information barrier segment members route group.
---
# shield information barrier segment members API Routes
Handle 4 OpenAPI operation(s) under /shield_information_barrier_segment_members for the shield information barrier segment members route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shield_information_barrier_segment_members_id
- Operation ID: `get_shield_information_barrier_segment_members_id`
- Route: `GET /shield_information_barrier_segment_members/{shield_information_barrier_segment_member_id}`
- Mode: READ
- Summary: Get shield information barrier segment member by ID
- Parameters:
- `shield_information_barrier_segment_member_id` in `path` required
### delete_shield_information_barrier_segment_members_id
- Operation ID: `delete_shield_information_barrier_segment_members_id`
- Route: `DELETE /shield_information_barrier_segment_members/{shield_information_barrier_segment_member_id}`
- Mode: WRITE
- Summary: Delete shield information barrier segment member by ID
- Parameters:
- `shield_information_barrier_segment_member_id` in `path` required
### get_shield_information_barrier_segment_members
- Operation ID: `get_shield_information_barrier_segment_members`
- Route: `GET /shield_information_barrier_segment_members`
- Mode: READ
- Summary: List shield information barrier segment members
- Parameters:
- `shield_information_barrier_segment_id` in `query` required
- `marker` in `query`
- `limit` in `query`
### post_shield_information_barrier_segment_members
- Operation ID: `post_shield_information_barrier_segment_members`
- Route: `POST /shield_information_barrier_segment_members`
- Mode: WRITE
- Summary: Create shield information barrier segment member
- Body: JSON request body accepted.

View File

@@ -0,0 +1,51 @@
---
name: shield-information-barrier-segment-restrictions-routes
description: Handle 4 OpenAPI operation(s) under /shield_information_barrier_segment_restrictions for the shield information barrier segment restrictions route group.
---
# shield information barrier segment restrictions API Routes
Handle 4 OpenAPI operation(s) under /shield_information_barrier_segment_restrictions for the shield information barrier segment restrictions route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shield_information_barrier_segment_restrictions_id
- Operation ID: `get_shield_information_barrier_segment_restrictions_id`
- Route: `GET /shield_information_barrier_segment_restrictions/{shield_information_barrier_segment_restriction_id}`
- Mode: READ
- Summary: Get shield information barrier segment restriction by ID
- Parameters:
- `shield_information_barrier_segment_restriction_id` in `path` required
### delete_shield_information_barrier_segment_restrictions_id
- Operation ID: `delete_shield_information_barrier_segment_restrictions_id`
- Route: `DELETE /shield_information_barrier_segment_restrictions/{shield_information_barrier_segment_restriction_id}`
- Mode: WRITE
- Summary: Delete shield information barrier segment restriction by ID
- Parameters:
- `shield_information_barrier_segment_restriction_id` in `path` required
### get_shield_information_barrier_segment_restrictions
- Operation ID: `get_shield_information_barrier_segment_restrictions`
- Route: `GET /shield_information_barrier_segment_restrictions`
- Mode: READ
- Summary: List shield information barrier segment restrictions
- Parameters:
- `shield_information_barrier_segment_id` in `query` required
- `marker` in `query`
- `limit` in `query`
### post_shield_information_barrier_segment_restrictions
- Operation ID: `post_shield_information_barrier_segment_restrictions`
- Route: `POST /shield_information_barrier_segment_restrictions`
- Mode: WRITE
- Summary: Create shield information barrier segment restriction
- Body: JSON request body accepted.

View File

@@ -0,0 +1,61 @@
---
name: shield-information-barrier-segments-routes
description: Handle 5 OpenAPI operation(s) under /shield_information_barrier_segments for the shield information barrier segments route group.
---
# shield information barrier segments API Routes
Handle 5 OpenAPI operation(s) under /shield_information_barrier_segments for the shield information barrier segments route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shield_information_barrier_segments_id
- Operation ID: `get_shield_information_barrier_segments_id`
- Route: `GET /shield_information_barrier_segments/{shield_information_barrier_segment_id}`
- Mode: READ
- Summary: Get shield information barrier segment with specified ID
- Parameters:
- `shield_information_barrier_segment_id` in `path` required
### delete_shield_information_barrier_segments_id
- Operation ID: `delete_shield_information_barrier_segments_id`
- Route: `DELETE /shield_information_barrier_segments/{shield_information_barrier_segment_id}`
- Mode: WRITE
- Summary: Delete shield information barrier segment
- Parameters:
- `shield_information_barrier_segment_id` in `path` required
### put_shield_information_barrier_segments_id
- Operation ID: `put_shield_information_barrier_segments_id`
- Route: `PUT /shield_information_barrier_segments/{shield_information_barrier_segment_id}`
- Mode: WRITE
- Summary: Update shield information barrier segment with specified ID
- Parameters:
- `shield_information_barrier_segment_id` in `path` required
- Body: JSON request body accepted.
### get_shield_information_barrier_segments
- Operation ID: `get_shield_information_barrier_segments`
- Route: `GET /shield_information_barrier_segments`
- Mode: READ
- Summary: List shield information barrier segments
- Parameters:
- `shield_information_barrier_id` in `query` required
- `marker` in `query`
- `limit` in `query`
### post_shield_information_barrier_segments
- Operation ID: `post_shield_information_barrier_segments`
- Route: `POST /shield_information_barrier_segments`
- Mode: WRITE
- Summary: Create shield information barrier segment
- Body: JSON request body accepted.

View File

@@ -0,0 +1,49 @@
---
name: shield-information-barriers-routes
description: Handle 4 OpenAPI operation(s) under /shield_information_barriers for the shield information barriers route group.
---
# shield information barriers API Routes
Handle 4 OpenAPI operation(s) under /shield_information_barriers for the shield information barriers route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_shield_information_barriers_id
- Operation ID: `get_shield_information_barriers_id`
- Route: `GET /shield_information_barriers/{shield_information_barrier_id}`
- Mode: READ
- Summary: Get shield information barrier with specified ID
- Parameters:
- `shield_information_barrier_id` in `path` required
### post_shield_information_barriers_change_status
- Operation ID: `post_shield_information_barriers_change_status`
- Route: `POST /shield_information_barriers/change_status`
- Mode: WRITE
- Summary: Add changed status of shield information barrier with specified ID
- Body: JSON request body accepted.
### get_shield_information_barriers
- Operation ID: `get_shield_information_barriers`
- Route: `GET /shield_information_barriers`
- Mode: READ
- Summary: List shield information barriers
- Parameters:
- `marker` in `query`
- `limit` in `query`
### post_shield_information_barriers
- Operation ID: `post_shield_information_barriers`
- Route: `POST /shield_information_barriers`
- Mode: WRITE
- Summary: Create shield information barrier
- Body: JSON request body accepted.

View File

@@ -0,0 +1,62 @@
---
name: sign-requests-routes
description: Handle 5 OpenAPI operation(s) under /sign_requests for the sign requests route group.
---
# sign requests API Routes
Handle 5 OpenAPI operation(s) under /sign_requests for the sign requests route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_sign_requests_id_cancel
- Operation ID: `post_sign_requests_id_cancel`
- Route: `POST /sign_requests/{sign_request_id}/cancel`
- Mode: WRITE
- Summary: Cancel Box Sign request
- Parameters:
- `sign_request_id` in `path` required
- Body: JSON request body accepted.
### post_sign_requests_id_resend
- Operation ID: `post_sign_requests_id_resend`
- Route: `POST /sign_requests/{sign_request_id}/resend`
- Mode: WRITE
- Summary: Resend Box Sign request
- Parameters:
- `sign_request_id` in `path` required
### get_sign_requests_id
- Operation ID: `get_sign_requests_id`
- Route: `GET /sign_requests/{sign_request_id}`
- Mode: READ
- Summary: Get Box Sign request by ID
- Parameters:
- `sign_request_id` in `path` required
### get_sign_requests
- Operation ID: `get_sign_requests`
- Route: `GET /sign_requests`
- Mode: READ
- Summary: List Box Sign requests
- Parameters:
- `marker` in `query`
- `limit` in `query`
- `senders` in `query`
- `shared_requests` in `query`
### post_sign_requests
- Operation ID: `post_sign_requests`
- Route: `POST /sign_requests`
- Mode: WRITE
- Summary: Create Box Sign request
- Body: JSON request body accepted.

View File

@@ -0,0 +1,33 @@
---
name: sign-templates-routes
description: Handle 2 OpenAPI operation(s) under /sign_templates for the sign templates route group.
---
# sign templates API Routes
Handle 2 OpenAPI operation(s) under /sign_templates for the sign templates route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_sign_templates
- Operation ID: `get_sign_templates`
- Route: `GET /sign_templates`
- Mode: READ
- Summary: List Box Sign templates
- Parameters:
- `marker` in `query`
- `limit` in `query`
### get_sign_templates_id
- Operation ID: `get_sign_templates_id`
- Route: `GET /sign_templates/{template_id}`
- Mode: READ
- Summary: Get Box Sign template by ID
- Parameters:
- `template_id` in `path` required

View File

@@ -0,0 +1,24 @@
---
name: skill-invocations-routes
description: Handle 1 OpenAPI operation(s) under /skill_invocations/{skill_id} for the skill invocations route group.
---
# skill invocations API Routes
Handle 1 OpenAPI operation(s) under /skill_invocations/{skill_id} for the skill invocations route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### put_skill_invocations_id
- Operation ID: `put_skill_invocations_id`
- Route: `PUT /skill_invocations/{skill_id}`
- Mode: WRITE
- Summary: Update all Box Skill cards on file
- Parameters:
- `skill_id` in `path` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,34 @@
---
name: storage-policies-routes
description: Handle 2 OpenAPI operation(s) under /storage_policies for the storage policies route group.
---
# storage policies API Routes
Handle 2 OpenAPI operation(s) under /storage_policies for the storage policies route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_storage_policies
- Operation ID: `get_storage_policies`
- Route: `GET /storage_policies`
- Mode: READ
- Summary: List storage policies
- Parameters:
- `fields` in `query`
- `marker` in `query`
- `limit` in `query`
### get_storage_policies_id
- Operation ID: `get_storage_policies_id`
- Route: `GET /storage_policies/{storage_policy_id}`
- Mode: READ
- Summary: Get storage policy
- Parameters:
- `storage_policy_id` in `path` required

View File

@@ -0,0 +1,61 @@
---
name: storage-policy-assignments-routes
description: Handle 5 OpenAPI operation(s) under /storage_policy_assignments for the storage policy assignments route group.
---
# storage policy assignments API Routes
Handle 5 OpenAPI operation(s) under /storage_policy_assignments for the storage policy assignments route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_storage_policy_assignments
- Operation ID: `get_storage_policy_assignments`
- Route: `GET /storage_policy_assignments`
- Mode: READ
- Summary: List storage policy assignments
- Parameters:
- `marker` in `query`
- `resolved_for_type` in `query` required
- `resolved_for_id` in `query` required
### post_storage_policy_assignments
- Operation ID: `post_storage_policy_assignments`
- Route: `POST /storage_policy_assignments`
- Mode: WRITE
- Summary: Assign storage policy
- Body: JSON request body accepted.
### get_storage_policy_assignments_id
- Operation ID: `get_storage_policy_assignments_id`
- Route: `GET /storage_policy_assignments/{storage_policy_assignment_id}`
- Mode: READ
- Summary: Get storage policy assignment
- Parameters:
- `storage_policy_assignment_id` in `path` required
### put_storage_policy_assignments_id
- Operation ID: `put_storage_policy_assignments_id`
- Route: `PUT /storage_policy_assignments/{storage_policy_assignment_id}`
- Mode: WRITE
- Summary: Update storage policy assignment
- Parameters:
- `storage_policy_assignment_id` in `path` required
- Body: JSON request body accepted.
### delete_storage_policy_assignments_id
- Operation ID: `delete_storage_policy_assignments_id`
- Route: `DELETE /storage_policy_assignments/{storage_policy_assignment_id}`
- Mode: WRITE
- Summary: Unassign storage policy
- Parameters:
- `storage_policy_assignment_id` in `path` required

View File

@@ -0,0 +1,50 @@
---
name: task-assignments-routes
description: Handle 4 OpenAPI operation(s) under /task_assignments for the task assignments route group.
---
# task assignments API Routes
Handle 4 OpenAPI operation(s) under /task_assignments for the task assignments route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_task_assignments
- Operation ID: `post_task_assignments`
- Route: `POST /task_assignments`
- Mode: WRITE
- Summary: Assign task
- Body: JSON request body accepted.
### get_task_assignments_id
- Operation ID: `get_task_assignments_id`
- Route: `GET /task_assignments/{task_assignment_id}`
- Mode: READ
- Summary: Get task assignment
- Parameters:
- `task_assignment_id` in `path` required
### put_task_assignments_id
- Operation ID: `put_task_assignments_id`
- Route: `PUT /task_assignments/{task_assignment_id}`
- Mode: WRITE
- Summary: Update task assignment
- Parameters:
- `task_assignment_id` in `path` required
- Body: JSON request body accepted.
### delete_task_assignments_id
- Operation ID: `delete_task_assignments_id`
- Route: `DELETE /task_assignments/{task_assignment_id}`
- Mode: WRITE
- Summary: Unassign task
- Parameters:
- `task_assignment_id` in `path` required

59
skills/tasks/SKILL.md Normal file
View File

@@ -0,0 +1,59 @@
---
name: tasks-routes
description: Handle 5 OpenAPI operation(s) under /tasks for the tasks route group.
---
# tasks API Routes
Handle 5 OpenAPI operation(s) under /tasks for the tasks route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_tasks
- Operation ID: `post_tasks`
- Route: `POST /tasks`
- Mode: WRITE
- Summary: Create task
- Body: JSON request body accepted.
### get_tasks_id
- Operation ID: `get_tasks_id`
- Route: `GET /tasks/{task_id}`
- Mode: READ
- Summary: Get task
- Parameters:
- `task_id` in `path` required
### put_tasks_id
- Operation ID: `put_tasks_id`
- Route: `PUT /tasks/{task_id}`
- Mode: WRITE
- Summary: Update task
- Parameters:
- `task_id` in `path` required
- Body: JSON request body accepted.
### delete_tasks_id
- Operation ID: `delete_tasks_id`
- Route: `DELETE /tasks/{task_id}`
- Mode: WRITE
- Summary: Remove task
- Parameters:
- `task_id` in `path` required
### get_tasks_id_assignments
- Operation ID: `get_tasks_id_assignments`
- Route: `GET /tasks/{task_id}/assignments`
- Mode: READ
- Summary: List task assignments
- Parameters:
- `task_id` in `path` required

View File

@@ -0,0 +1,42 @@
---
name: terms-of-service-user-statuses-routes
description: Handle 3 OpenAPI operation(s) under /terms_of_service_user_statuses for the terms of service user statuses route group.
---
# terms of service user statuses API Routes
Handle 3 OpenAPI operation(s) under /terms_of_service_user_statuses for the terms of service user statuses route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_terms_of_service_user_statuses
- Operation ID: `get_terms_of_service_user_statuses`
- Route: `GET /terms_of_service_user_statuses`
- Mode: READ
- Summary: List terms of service user statuses
- Parameters:
- `tos_id` in `query` required
- `user_id` in `query`
### post_terms_of_service_user_statuses
- Operation ID: `post_terms_of_service_user_statuses`
- Route: `POST /terms_of_service_user_statuses`
- Mode: WRITE
- Summary: Create terms of service status for new user
- Body: JSON request body accepted.
### put_terms_of_service_user_statuses_id
- Operation ID: `put_terms_of_service_user_statuses_id`
- Route: `PUT /terms_of_service_user_statuses/{terms_of_service_user_status_id}`
- Mode: WRITE
- Summary: Update terms of service status for existing user
- Parameters:
- `terms_of_service_user_status_id` in `path` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,50 @@
---
name: terms-of-services-routes
description: Handle 4 OpenAPI operation(s) under /terms_of_services for the terms of services route group.
---
# terms of services API Routes
Handle 4 OpenAPI operation(s) under /terms_of_services for the terms of services route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_terms_of_services
- Operation ID: `get_terms_of_services`
- Route: `GET /terms_of_services`
- Mode: READ
- Summary: List terms of services
- Parameters:
- `tos_type` in `query`
### post_terms_of_services
- Operation ID: `post_terms_of_services`
- Route: `POST /terms_of_services`
- Mode: WRITE
- Summary: Create terms of service
- Body: JSON request body accepted.
### get_terms_of_services_id
- Operation ID: `get_terms_of_services_id`
- Route: `GET /terms_of_services/{terms_of_service_id}`
- Mode: READ
- Summary: Get terms of service
- Parameters:
- `terms_of_service_id` in `path` required
### put_terms_of_services_id
- Operation ID: `put_terms_of_services_id`
- Route: `PUT /terms_of_services/{terms_of_service_id}`
- Mode: WRITE
- Summary: Update terms of service
- Parameters:
- `terms_of_service_id` in `path` required
- Body: JSON request body accepted.

169
skills/users/SKILL.md Normal file
View File

@@ -0,0 +1,169 @@
---
name: users-routes
description: Handle 15 OpenAPI operation(s) under /users for the users route group.
---
# users API Routes
Handle 15 OpenAPI operation(s) under /users for the users route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_users
- Operation ID: `get_users`
- Route: `GET /users`
- Mode: READ
- Summary: List enterprise users
- Parameters:
- `filter_term` in `query`
- `user_type` in `query`
- `external_app_user_id` in `query`
- `fields` in `query`
- `offset` in `query`
- `limit` in `query`
- `usemarker` in `query`
- `marker` in `query`
### post_users
- Operation ID: `post_users`
- Route: `POST /users`
- Mode: WRITE
- Summary: Create user
- Parameters:
- `fields` in `query`
- Body: JSON request body accepted.
### get_users_me
- Operation ID: `get_users_me`
- Route: `GET /users/me`
- Mode: READ
- Summary: Get current user
- Parameters:
- `fields` in `query`
### post_users_terminate_sessions
- Operation ID: `post_users_terminate_sessions`
- Route: `POST /users/terminate_sessions`
- Mode: WRITE
- Summary: Create jobs to terminate users session
- Body: JSON request body accepted.
### get_users_id
- Operation ID: `get_users_id`
- Route: `GET /users/{user_id}`
- Mode: READ
- Summary: Get user
- Parameters:
- `user_id` in `path` required
- `fields` in `query`
### put_users_id
- Operation ID: `put_users_id`
- Route: `PUT /users/{user_id}`
- Mode: WRITE
- Summary: Update user
- Parameters:
- `user_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### delete_users_id
- Operation ID: `delete_users_id`
- Route: `DELETE /users/{user_id}`
- Mode: WRITE
- Summary: Delete user
- Parameters:
- `user_id` in `path` required
- `notify` in `query`
- `force` in `query`
### get_users_id_avatar
- Operation ID: `get_users_id_avatar`
- Route: `GET /users/{user_id}/avatar`
- Mode: READ
- Summary: Get user avatar
- Parameters:
- `user_id` in `path` required
### post_users_id_avatar
- Operation ID: `post_users_id_avatar`
- Route: `POST /users/{user_id}/avatar`
- Mode: WRITE
- Summary: Add or update user avatar
- Parameters:
- `user_id` in `path` required
- Body: JSON request body accepted.
### delete_users_id_avatar
- Operation ID: `delete_users_id_avatar`
- Route: `DELETE /users/{user_id}/avatar`
- Mode: WRITE
- Summary: Delete user avatar
- Parameters:
- `user_id` in `path` required
### put_users_id_folders_0
- Operation ID: `put_users_id_folders_0`
- Route: `PUT /users/{user_id}/folders/0`
- Mode: WRITE
- Summary: Transfer owned folders
- Parameters:
- `user_id` in `path` required
- `fields` in `query`
- `notify` in `query`
- Body: JSON request body accepted.
### get_users_id_email_aliases
- Operation ID: `get_users_id_email_aliases`
- Route: `GET /users/{user_id}/email_aliases`
- Mode: READ
- Summary: List user's email aliases
- Parameters:
- `user_id` in `path` required
### post_users_id_email_aliases
- Operation ID: `post_users_id_email_aliases`
- Route: `POST /users/{user_id}/email_aliases`
- Mode: WRITE
- Summary: Create email alias
- Parameters:
- `user_id` in `path` required
- Body: JSON request body accepted.
### delete_users_id_email_aliases_id
- Operation ID: `delete_users_id_email_aliases_id`
- Route: `DELETE /users/{user_id}/email_aliases/{email_alias_id}`
- Mode: WRITE
- Summary: Remove email alias
- Parameters:
- `user_id` in `path` required
- `email_alias_id` in `path` required
### get_users_id_memberships
- Operation ID: `get_users_id_memberships`
- Route: `GET /users/{user_id}/memberships`
- Mode: READ
- Summary: List user's groups
- Parameters:
- `user_id` in `path` required
- `limit` in `query`
- `offset` in `query`

124
skills/web-links/SKILL.md Normal file
View File

@@ -0,0 +1,124 @@
---
name: web-links-routes
description: Handle 11 OpenAPI operation(s) under /web_links for the web links route group.
---
# web links API Routes
Handle 11 OpenAPI operation(s) under /web_links for the web links route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_web_links
- Operation ID: `post_web_links`
- Route: `POST /web_links`
- Mode: WRITE
- Summary: Create web link
- Body: JSON request body accepted.
### get_web_links_id
- Operation ID: `get_web_links_id`
- Route: `GET /web_links/{web_link_id}`
- Mode: READ
- Summary: Get web link
- Parameters:
- `web_link_id` in `path` required
- `boxapi` in `header`
### post_web_links_id
- Operation ID: `post_web_links_id`
- Route: `POST /web_links/{web_link_id}`
- Mode: WRITE
- Summary: Restore web link
- Parameters:
- `web_link_id` in `path` required
- `fields` in `query`
- Body: JSON request body accepted.
### put_web_links_id
- Operation ID: `put_web_links_id`
- Route: `PUT /web_links/{web_link_id}`
- Mode: WRITE
- Summary: Update web link
- Parameters:
- `web_link_id` in `path` required
- Body: JSON request body accepted.
### delete_web_links_id
- Operation ID: `delete_web_links_id`
- Route: `DELETE /web_links/{web_link_id}`
- Mode: WRITE
- Summary: Remove web link
- Parameters:
- `web_link_id` in `path` required
### get_web_links_id_trash
- Operation ID: `get_web_links_id_trash`
- Route: `GET /web_links/{web_link_id}/trash`
- Mode: READ
- Summary: Get trashed web link
- Parameters:
- `web_link_id` in `path` required
- `fields` in `query`
### delete_web_links_id_trash
- Operation ID: `delete_web_links_id_trash`
- Route: `DELETE /web_links/{web_link_id}/trash`
- Mode: WRITE
- Summary: Permanently remove web link
- Parameters:
- `web_link_id` in `path` required
### get_web_links_id_get_shared_link
- Operation ID: `get_web_links_id_get_shared_link`
- Route: `GET /web_links/{web_link_id}#get_shared_link`
- Mode: READ
- Summary: Get shared link for web link
- Parameters:
- `web_link_id` in `path` required
- `fields` in `query` required
### put_web_links_id_add_shared_link
- Operation ID: `put_web_links_id_add_shared_link`
- Route: `PUT /web_links/{web_link_id}#add_shared_link`
- Mode: WRITE
- Summary: Add shared link to web link
- Parameters:
- `web_link_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.
### put_web_links_id_update_shared_link
- Operation ID: `put_web_links_id_update_shared_link`
- Route: `PUT /web_links/{web_link_id}#update_shared_link`
- Mode: WRITE
- Summary: Update shared link on web link
- Parameters:
- `web_link_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.
### put_web_links_id_remove_shared_link
- Operation ID: `put_web_links_id_remove_shared_link`
- Route: `PUT /web_links/{web_link_id}#remove_shared_link`
- Mode: WRITE
- Summary: Remove shared link from web link
- Parameters:
- `web_link_id` in `path` required
- `fields` in `query` required
- Body: JSON request body accepted.

60
skills/webhooks/SKILL.md Normal file
View File

@@ -0,0 +1,60 @@
---
name: webhooks-routes
description: Handle 5 OpenAPI operation(s) under /webhooks for the webhooks route group.
---
# webhooks API Routes
Handle 5 OpenAPI operation(s) under /webhooks for the webhooks route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_webhooks
- Operation ID: `get_webhooks`
- Route: `GET /webhooks`
- Mode: READ
- Summary: List all webhooks
- Parameters:
- `marker` in `query`
- `limit` in `query`
### post_webhooks
- Operation ID: `post_webhooks`
- Route: `POST /webhooks`
- Mode: WRITE
- Summary: Create webhook
- Body: JSON request body accepted.
### get_webhooks_id
- Operation ID: `get_webhooks_id`
- Route: `GET /webhooks/{webhook_id}`
- Mode: READ
- Summary: Get webhook
- Parameters:
- `webhook_id` in `path` required
### put_webhooks_id
- Operation ID: `put_webhooks_id`
- Route: `PUT /webhooks/{webhook_id}`
- Mode: WRITE
- Summary: Update webhook
- Parameters:
- `webhook_id` in `path` required
- Body: JSON request body accepted.
### delete_webhooks_id
- Operation ID: `delete_webhooks_id`
- Route: `DELETE /webhooks/{webhook_id}`
- Mode: WRITE
- Summary: Remove webhook
- Parameters:
- `webhook_id` in `path` required

36
skills/workflows/SKILL.md Normal file
View File

@@ -0,0 +1,36 @@
---
name: workflows-routes
description: Handle 2 OpenAPI operation(s) under /workflows for the workflows route group.
---
# workflows API Routes
Handle 2 OpenAPI operation(s) under /workflows for the workflows route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### get_workflows
- Operation ID: `get_workflows`
- Route: `GET /workflows`
- Mode: READ
- Summary: List workflows
- Parameters:
- `folder_id` in `query` required
- `trigger_type` in `query`
- `limit` in `query`
- `marker` in `query`
### post_workflows_id_start
- Operation ID: `post_workflows_id_start`
- Route: `POST /workflows/{workflow_id}/start`
- Mode: WRITE
- Summary: Starts workflow based on request body
- Parameters:
- `workflow_id` in `path` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,40 @@
---
name: zip-downloads-routes
description: Handle 3 OpenAPI operation(s) under /zip_downloads for the zip downloads route group.
---
# zip downloads API Routes
Handle 3 OpenAPI operation(s) under /zip_downloads for the zip downloads route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### post_zip_downloads
- Operation ID: `post_zip_downloads`
- Route: `POST /zip_downloads`
- Mode: WRITE
- Summary: Create zip download
- Body: JSON request body accepted.
### get_zip_downloads_id_content
- Operation ID: `get_zip_downloads_id_content`
- Route: `GET /zip_downloads/{zip_download_id}/content`
- Mode: READ
- Summary: Download zip archive
- Parameters:
- `zip_download_id` in `path` required
### get_zip_downloads_id_status
- Operation ID: `get_zip_downloads_id_status`
- Route: `GET /zip_downloads/{zip_download_id}/status`
- Mode: READ
- Summary: Get zip download status
- Parameters:
- `zip_download_id` in `path` required