This commit is contained in:
a2a-platform
2026-06-27 01:03:04 +00:00
commit 15ec8b1d74
78 changed files with 91602 additions and 0 deletions

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

@@ -0,0 +1,35 @@
---
name: accounts-routes
description: Handle 2 OpenAPI operation(s) under /api/accounts for the accounts route group.
---
# accounts API Routes
Handle 2 OpenAPI operation(s) under /api/accounts for the accounts 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_accounts
- Operation ID: `get_accounts`
- Route: `GET /api/accounts`
- Mode: READ
- Summary: Get Accounts
- Parameters:
- `fields[account]` in `query`
- `revision` in `header` required
### get_account
- Operation ID: `get_account`
- Route: `GET /api/accounts/{id}`
- Mode: READ
- Summary: Get Account
- Parameters:
- `id` in `path` required
- `fields[account]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,24 @@
---
name: back-in-stock-subscriptions-routes
description: Handle 1 OpenAPI operation(s) under /api/back-in-stock-subscriptions for the back in stock subscriptions route group.
---
# back in stock subscriptions API Routes
Handle 1 OpenAPI operation(s) under /api/back-in-stock-subscriptions for the back in stock subscriptions 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
### create_back_in_stock_subscription
- Operation ID: `create_back_in_stock_subscription`
- Route: `POST /api/back-in-stock-subscriptions`
- Mode: WRITE
- Summary: Create Back In Stock Subscription
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: campaign-clone-routes
description: Handle 1 OpenAPI operation(s) under /api/campaign-clone for the campaign clone route group.
---
# campaign clone API Routes
Handle 1 OpenAPI operation(s) under /api/campaign-clone for the campaign clone 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
### create_campaign_clone
- Operation ID: `create_campaign_clone`
- Route: `POST /api/campaign-clone`
- Mode: WRITE
- Summary: Create Campaign Clone
- Parameters:
- `fields[campaign]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: campaign-message-assign-template-routes
description: Handle 1 OpenAPI operation(s) under /api/campaign-message-assign-template for the campaign message assign template route group.
---
# campaign message assign template API Routes
Handle 1 OpenAPI operation(s) under /api/campaign-message-assign-template for the campaign message assign template 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
### assign_template_to_campaign_message
- Operation ID: `assign_template_to_campaign_message`
- Route: `POST /api/campaign-message-assign-template`
- Mode: WRITE
- Summary: Assign Template to Campaign Message
- Parameters:
- `fields[campaign-message]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,115 @@
---
name: campaign-messages-routes
description: Handle 9 OpenAPI operation(s) under /api/campaign-messages/{id} for the campaign messages route group.
---
# campaign messages API Routes
Handle 9 OpenAPI operation(s) under /api/campaign-messages/{id} for the campaign messages 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_campaign_message
- Operation ID: `get_campaign_message`
- Route: `GET /api/campaign-messages/{id}`
- Mode: READ
- Summary: Get Campaign Message
- Parameters:
- `id` in `path` required
- `fields[campaign-message]` in `query`
- `fields[campaign]` in `query`
- `fields[image]` in `query`
- `fields[template]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_campaign_message
- Operation ID: `update_campaign_message`
- Route: `PATCH /api/campaign-messages/{id}`
- Mode: WRITE
- Summary: Update Campaign Message
- Parameters:
- `id` in `path` required
- `fields[campaign-message]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_campaign_for_campaign_message
- Operation ID: `get_campaign_for_campaign_message`
- Route: `GET /api/campaign-messages/{id}/campaign`
- Mode: READ
- Summary: Get Campaign for Campaign Message
- Parameters:
- `id` in `path` required
- `fields[campaign]` in `query`
- `revision` in `header` required
### get_campaign_id_for_campaign_message
- Operation ID: `get_campaign_id_for_campaign_message`
- Route: `GET /api/campaign-messages/{id}/relationships/campaign`
- Mode: READ
- Summary: Get Campaign ID for Campaign Message
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_template_for_campaign_message
- Operation ID: `get_template_for_campaign_message`
- Route: `GET /api/campaign-messages/{id}/template`
- Mode: READ
- Summary: Get Template for Campaign Message
- Parameters:
- `id` in `path` required
- `fields[template]` in `query`
- `revision` in `header` required
### get_template_id_for_campaign_message
- Operation ID: `get_template_id_for_campaign_message`
- Route: `GET /api/campaign-messages/{id}/relationships/template`
- Mode: READ
- Summary: Get Template ID for Campaign Message
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_image_for_campaign_message
- Operation ID: `get_image_for_campaign_message`
- Route: `GET /api/campaign-messages/{id}/image`
- Mode: READ
- Summary: Get Image for Campaign Message
- Parameters:
- `id` in `path` required
- `fields[image]` in `query`
- `revision` in `header` required
### get_image_id_for_campaign_message
- Operation ID: `get_image_id_for_campaign_message`
- Route: `GET /api/campaign-messages/{id}/relationships/image`
- Mode: READ
- Summary: Get Image ID for Campaign Message
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### update_image_for_campaign_message
- Operation ID: `update_image_for_campaign_message`
- Route: `PATCH /api/campaign-messages/{id}/relationships/image`
- Mode: WRITE
- Summary: Update Image for Campaign Message
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,36 @@
---
name: campaign-recipient-estimation-jobs-routes
description: Handle 2 OpenAPI operation(s) under /api/campaign-recipient-estimation-jobs for the campaign recipient estimation jobs route group.
---
# campaign recipient estimation jobs API Routes
Handle 2 OpenAPI operation(s) under /api/campaign-recipient-estimation-jobs for the campaign recipient estimation jobs 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_campaign_recipient_estimation_job
- Operation ID: `get_campaign_recipient_estimation_job`
- Route: `GET /api/campaign-recipient-estimation-jobs/{id}`
- Mode: READ
- Summary: Get Campaign Recipient Estimation Job
- Parameters:
- `id` in `path` required
- `fields[campaign-recipient-estimation-job]` in `query`
- `revision` in `header` required
### refresh_campaign_recipient_estimation
- Operation ID: `refresh_campaign_recipient_estimation`
- Route: `POST /api/campaign-recipient-estimation-jobs`
- Mode: WRITE
- Summary: Refresh Campaign Recipient Estimation
- Parameters:
- `fields[campaign-recipient-estimation-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: campaign-recipient-estimations-routes
description: Handle 1 OpenAPI operation(s) under /api/campaign-recipient-estimations/{id} for the campaign recipient estimations route group.
---
# campaign recipient estimations API Routes
Handle 1 OpenAPI operation(s) under /api/campaign-recipient-estimations/{id} for the campaign recipient estimations 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_campaign_recipient_estimation
- Operation ID: `get_campaign_recipient_estimation`
- Route: `GET /api/campaign-recipient-estimations/{id}`
- Mode: READ
- Summary: Get Campaign Recipient Estimation
- Parameters:
- `id` in `path` required
- `fields[campaign-recipient-estimation]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,47 @@
---
name: campaign-send-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/campaign-send-jobs for the campaign send jobs route group.
---
# campaign send jobs API Routes
Handle 3 OpenAPI operation(s) under /api/campaign-send-jobs for the campaign send jobs 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_campaign_send_job
- Operation ID: `get_campaign_send_job`
- Route: `GET /api/campaign-send-jobs/{id}`
- Mode: READ
- Summary: Get Campaign Send Job
- Parameters:
- `id` in `path` required
- `fields[campaign-send-job]` in `query`
- `revision` in `header` required
### cancel_campaign_send
- Operation ID: `cancel_campaign_send`
- Route: `PATCH /api/campaign-send-jobs/{id}`
- Mode: WRITE
- Summary: Cancel Campaign Send
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### send_campaign
- Operation ID: `send_campaign`
- Route: `POST /api/campaign-send-jobs`
- Mode: WRITE
- Summary: Send Campaign
- Parameters:
- `fields[campaign-send-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,26 @@
---
name: campaign-values-reports-routes
description: Handle 1 OpenAPI operation(s) under /api/campaign-values-reports for the campaign values reports route group.
---
# campaign values reports API Routes
Handle 1 OpenAPI operation(s) under /api/campaign-values-reports for the campaign values 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
### query_campaign_values
- Operation ID: `query_campaign_values`
- Route: `POST /api/campaign-values-reports`
- Mode: WRITE
- Summary: Query Campaign Values
- Parameters:
- `fields[campaign-values-report]` in `query`
- `page_cursor` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

124
skills/campaigns/SKILL.md Normal file
View File

@@ -0,0 +1,124 @@
---
name: campaigns-routes
description: Handle 9 OpenAPI operation(s) under /api/campaigns for the campaigns route group.
---
# campaigns API Routes
Handle 9 OpenAPI operation(s) under /api/campaigns for the campaigns 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_campaigns
- Operation ID: `get_campaigns`
- Route: `GET /api/campaigns`
- Mode: READ
- Summary: Get Campaigns
- Parameters:
- `fields[campaign-message]` in `query`
- `fields[campaign]` in `query`
- `fields[tag]` in `query`
- `filter` in `query` required
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_campaign
- Operation ID: `create_campaign`
- Route: `POST /api/campaigns`
- Mode: WRITE
- Summary: Create Campaign
- Parameters:
- `fields[campaign]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_campaign
- Operation ID: `get_campaign`
- Route: `GET /api/campaigns/{id}`
- Mode: READ
- Summary: Get Campaign
- Parameters:
- `id` in `path` required
- `fields[campaign-message]` in `query`
- `fields[campaign]` in `query`
- `fields[tag]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_campaign
- Operation ID: `update_campaign`
- Route: `PATCH /api/campaigns/{id}`
- Mode: WRITE
- Summary: Update Campaign
- Parameters:
- `id` in `path` required
- `fields[campaign]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_campaign
- Operation ID: `delete_campaign`
- Route: `DELETE /api/campaigns/{id}`
- Mode: WRITE
- Summary: Delete Campaign
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_tags_for_campaign
- Operation ID: `get_tags_for_campaign`
- Route: `GET /api/campaigns/{id}/tags`
- Mode: READ
- Summary: Get Tags for Campaign
- Parameters:
- `id` in `path` required
- `fields[tag]` in `query`
- `revision` in `header` required
### get_tag_ids_for_campaign
- Operation ID: `get_tag_ids_for_campaign`
- Route: `GET /api/campaigns/{id}/relationships/tags`
- Mode: READ
- Summary: Get Tag IDs for Campaign
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_messages_for_campaign
- Operation ID: `get_messages_for_campaign`
- Route: `GET /api/campaigns/{id}/campaign-messages`
- Mode: READ
- Summary: Get Messages for Campaign
- Parameters:
- `id` in `path` required
- `fields[campaign-message]` in `query`
- `fields[campaign]` in `query`
- `fields[image]` in `query`
- `fields[template]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_message_ids_for_campaign
- Operation ID: `get_message_ids_for_campaign`
- Route: `GET /api/campaigns/{id}/relationships/campaign-messages`
- Mode: READ
- Summary: Get Message IDs for Campaign
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,136 @@
---
name: catalog-categories-routes
description: Handle 10 OpenAPI operation(s) under /api/catalog-categories for the catalog categories route group.
---
# catalog categories API Routes
Handle 10 OpenAPI operation(s) under /api/catalog-categories for the catalog categories 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_catalog_categories
- Operation ID: `get_catalog_categories`
- Route: `GET /api/catalog-categories`
- Mode: READ
- Summary: Get Catalog Categories
- Parameters:
- `fields[catalog-category]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_catalog_category
- Operation ID: `create_catalog_category`
- Route: `POST /api/catalog-categories`
- Mode: WRITE
- Summary: Create Catalog Category
- Parameters:
- `fields[catalog-category]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_catalog_category
- Operation ID: `get_catalog_category`
- Route: `GET /api/catalog-categories/{id}`
- Mode: READ
- Summary: Get Catalog Category
- Parameters:
- `id` in `path` required
- `fields[catalog-category]` in `query`
- `revision` in `header` required
### update_catalog_category
- Operation ID: `update_catalog_category`
- Route: `PATCH /api/catalog-categories/{id}`
- Mode: WRITE
- Summary: Update Catalog Category
- Parameters:
- `id` in `path` required
- `fields[catalog-category]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_catalog_category
- Operation ID: `delete_catalog_category`
- Route: `DELETE /api/catalog-categories/{id}`
- Mode: WRITE
- Summary: Delete Catalog Category
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_items_for_catalog_category
- Operation ID: `get_items_for_catalog_category`
- Route: `GET /api/catalog-categories/{id}/items`
- Mode: READ
- Summary: Get Items for Catalog Category
- Parameters:
- `id` in `path` required
- `fields[catalog-item]` in `query`
- `fields[catalog-variant]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_item_ids_for_catalog_category
- Operation ID: `get_item_ids_for_catalog_category`
- Route: `GET /api/catalog-categories/{id}/relationships/items`
- Mode: READ
- Summary: Get Item IDs for Catalog Category
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### add_items_to_catalog_category
- Operation ID: `add_items_to_catalog_category`
- Route: `POST /api/catalog-categories/{id}/relationships/items`
- Mode: WRITE
- Summary: Add Items to Catalog Category
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### update_items_for_catalog_category
- Operation ID: `update_items_for_catalog_category`
- Route: `PATCH /api/catalog-categories/{id}/relationships/items`
- Mode: WRITE
- Summary: Update Items for Catalog Category
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### remove_items_from_catalog_category
- Operation ID: `remove_items_from_catalog_category`
- Route: `DELETE /api/catalog-categories/{id}/relationships/items`
- Mode: WRITE
- Summary: Remove Items from Catalog Category
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,50 @@
---
name: catalog-category-bulk-create-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-category-bulk-create-jobs for the catalog category bulk create jobs route group.
---
# catalog category bulk create jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-category-bulk-create-jobs for the catalog category bulk create jobs 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_bulk_create_categories_jobs
- Operation ID: `get_bulk_create_categories_jobs`
- Route: `GET /api/catalog-category-bulk-create-jobs`
- Mode: READ
- Summary: Get Bulk Create Categories Jobs
- Parameters:
- `fields[catalog-category-bulk-create-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_create_catalog_categories
- Operation ID: `bulk_create_catalog_categories`
- Route: `POST /api/catalog-category-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Create Catalog Categories
- Parameters:
- `fields[catalog-category-bulk-create-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_create_categories_job
- Operation ID: `get_bulk_create_categories_job`
- Route: `GET /api/catalog-category-bulk-create-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Create Categories Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-category-bulk-create-job]` in `query`
- `fields[catalog-category]` in `query`
- `include` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,48 @@
---
name: catalog-category-bulk-delete-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-category-bulk-delete-jobs for the catalog category bulk delete jobs route group.
---
# catalog category bulk delete jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-category-bulk-delete-jobs for the catalog category bulk delete jobs 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_bulk_delete_categories_jobs
- Operation ID: `get_bulk_delete_categories_jobs`
- Route: `GET /api/catalog-category-bulk-delete-jobs`
- Mode: READ
- Summary: Get Bulk Delete Categories Jobs
- Parameters:
- `fields[catalog-category-bulk-delete-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_delete_catalog_categories
- Operation ID: `bulk_delete_catalog_categories`
- Route: `POST /api/catalog-category-bulk-delete-jobs`
- Mode: WRITE
- Summary: Bulk Delete Catalog Categories
- Parameters:
- `fields[catalog-category-bulk-delete-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_delete_categories_job
- Operation ID: `get_bulk_delete_categories_job`
- Route: `GET /api/catalog-category-bulk-delete-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Delete Categories Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-category-bulk-delete-job]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,50 @@
---
name: catalog-category-bulk-update-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-category-bulk-update-jobs for the catalog category bulk update jobs route group.
---
# catalog category bulk update jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-category-bulk-update-jobs for the catalog category bulk update jobs 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_bulk_update_categories_jobs
- Operation ID: `get_bulk_update_categories_jobs`
- Route: `GET /api/catalog-category-bulk-update-jobs`
- Mode: READ
- Summary: Get Bulk Update Categories Jobs
- Parameters:
- `fields[catalog-category-bulk-update-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_update_catalog_categories
- Operation ID: `bulk_update_catalog_categories`
- Route: `POST /api/catalog-category-bulk-update-jobs`
- Mode: WRITE
- Summary: Bulk Update Catalog Categories
- Parameters:
- `fields[catalog-category-bulk-update-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_update_categories_job
- Operation ID: `get_bulk_update_categories_job`
- Route: `GET /api/catalog-category-bulk-update-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Update Categories Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-category-bulk-update-job]` in `query`
- `fields[catalog-category]` in `query`
- `include` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,50 @@
---
name: catalog-item-bulk-create-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-item-bulk-create-jobs for the catalog item bulk create jobs route group.
---
# catalog item bulk create jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-item-bulk-create-jobs for the catalog item bulk create jobs 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_bulk_create_catalog_items_jobs
- Operation ID: `get_bulk_create_catalog_items_jobs`
- Route: `GET /api/catalog-item-bulk-create-jobs`
- Mode: READ
- Summary: Get Bulk Create Catalog Items Jobs
- Parameters:
- `fields[catalog-item-bulk-create-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_create_catalog_items
- Operation ID: `bulk_create_catalog_items`
- Route: `POST /api/catalog-item-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Create Catalog Items
- Parameters:
- `fields[catalog-item-bulk-create-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_create_catalog_items_job
- Operation ID: `get_bulk_create_catalog_items_job`
- Route: `GET /api/catalog-item-bulk-create-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Create Catalog Items Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-item-bulk-create-job]` in `query`
- `fields[catalog-item]` in `query`
- `include` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,48 @@
---
name: catalog-item-bulk-delete-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-item-bulk-delete-jobs for the catalog item bulk delete jobs route group.
---
# catalog item bulk delete jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-item-bulk-delete-jobs for the catalog item bulk delete jobs 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_bulk_delete_catalog_items_jobs
- Operation ID: `get_bulk_delete_catalog_items_jobs`
- Route: `GET /api/catalog-item-bulk-delete-jobs`
- Mode: READ
- Summary: Get Bulk Delete Catalog Items Jobs
- Parameters:
- `fields[catalog-item-bulk-delete-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_delete_catalog_items
- Operation ID: `bulk_delete_catalog_items`
- Route: `POST /api/catalog-item-bulk-delete-jobs`
- Mode: WRITE
- Summary: Bulk Delete Catalog Items
- Parameters:
- `fields[catalog-item-bulk-delete-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_delete_catalog_items_job
- Operation ID: `get_bulk_delete_catalog_items_job`
- Route: `GET /api/catalog-item-bulk-delete-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Delete Catalog Items Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-item-bulk-delete-job]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,50 @@
---
name: catalog-item-bulk-update-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-item-bulk-update-jobs for the catalog item bulk update jobs route group.
---
# catalog item bulk update jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-item-bulk-update-jobs for the catalog item bulk update jobs 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_bulk_update_catalog_items_jobs
- Operation ID: `get_bulk_update_catalog_items_jobs`
- Route: `GET /api/catalog-item-bulk-update-jobs`
- Mode: READ
- Summary: Get Bulk Update Catalog Items Jobs
- Parameters:
- `fields[catalog-item-bulk-update-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_update_catalog_items
- Operation ID: `bulk_update_catalog_items`
- Route: `POST /api/catalog-item-bulk-update-jobs`
- Mode: WRITE
- Summary: Bulk Update Catalog Items
- Parameters:
- `fields[catalog-item-bulk-update-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_update_catalog_items_job
- Operation ID: `get_bulk_update_catalog_items_job`
- Route: `GET /api/catalog-item-bulk-update-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Update Catalog Items Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-item-bulk-update-job]` in `query`
- `fields[catalog-item]` in `query`
- `include` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,167 @@
---
name: catalog-items-routes
description: Handle 12 OpenAPI operation(s) under /api/catalog-items for the catalog items route group.
---
# catalog items API Routes
Handle 12 OpenAPI operation(s) under /api/catalog-items for the catalog 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_catalog_items
- Operation ID: `get_catalog_items`
- Route: `GET /api/catalog-items`
- Mode: READ
- Summary: Get Catalog Items
- Parameters:
- `fields[catalog-item]` in `query`
- `fields[catalog-variant]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_catalog_item
- Operation ID: `create_catalog_item`
- Route: `POST /api/catalog-items`
- Mode: WRITE
- Summary: Create Catalog Item
- Parameters:
- `fields[catalog-item]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_catalog_item
- Operation ID: `get_catalog_item`
- Route: `GET /api/catalog-items/{id}`
- Mode: READ
- Summary: Get Catalog Item
- Parameters:
- `id` in `path` required
- `fields[catalog-item]` in `query`
- `fields[catalog-variant]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_catalog_item
- Operation ID: `update_catalog_item`
- Route: `PATCH /api/catalog-items/{id}`
- Mode: WRITE
- Summary: Update Catalog Item
- Parameters:
- `id` in `path` required
- `fields[catalog-item]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_catalog_item
- Operation ID: `delete_catalog_item`
- Route: `DELETE /api/catalog-items/{id}`
- Mode: WRITE
- Summary: Delete Catalog Item
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_variants_for_catalog_item
- Operation ID: `get_variants_for_catalog_item`
- Route: `GET /api/catalog-items/{id}/variants`
- Mode: READ
- Summary: Get Variants for Catalog Item
- Parameters:
- `id` in `path` required
- `fields[catalog-variant]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_variant_ids_for_catalog_item
- Operation ID: `get_variant_ids_for_catalog_item`
- Route: `GET /api/catalog-items/{id}/relationships/variants`
- Mode: READ
- Summary: Get Variant IDs for Catalog Item
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_categories_for_catalog_item
- Operation ID: `get_categories_for_catalog_item`
- Route: `GET /api/catalog-items/{id}/categories`
- Mode: READ
- Summary: Get Categories for Catalog Item
- Parameters:
- `id` in `path` required
- `fields[catalog-category]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_category_ids_for_catalog_item
- Operation ID: `get_category_ids_for_catalog_item`
- Route: `GET /api/catalog-items/{id}/relationships/categories`
- Mode: READ
- Summary: Get Category IDs for Catalog Item
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### add_categories_to_catalog_item
- Operation ID: `add_categories_to_catalog_item`
- Route: `POST /api/catalog-items/{id}/relationships/categories`
- Mode: WRITE
- Summary: Add Categories to Catalog Item
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### update_categories_for_catalog_item
- Operation ID: `update_categories_for_catalog_item`
- Route: `PATCH /api/catalog-items/{id}/relationships/categories`
- Mode: WRITE
- Summary: Update Categories for Catalog Item
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### remove_categories_from_catalog_item
- Operation ID: `remove_categories_from_catalog_item`
- Route: `DELETE /api/catalog-items/{id}/relationships/categories`
- Mode: WRITE
- Summary: Remove Categories from Catalog Item
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,50 @@
---
name: catalog-variant-bulk-create-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-variant-bulk-create-jobs for the catalog variant bulk create jobs route group.
---
# catalog variant bulk create jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-variant-bulk-create-jobs for the catalog variant bulk create jobs 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_bulk_create_variants_jobs
- Operation ID: `get_bulk_create_variants_jobs`
- Route: `GET /api/catalog-variant-bulk-create-jobs`
- Mode: READ
- Summary: Get Bulk Create Variants Jobs
- Parameters:
- `fields[catalog-variant-bulk-create-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_create_catalog_variants
- Operation ID: `bulk_create_catalog_variants`
- Route: `POST /api/catalog-variant-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Create Catalog Variants
- Parameters:
- `fields[catalog-variant-bulk-create-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_create_variants_job
- Operation ID: `get_bulk_create_variants_job`
- Route: `GET /api/catalog-variant-bulk-create-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Create Variants Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-variant-bulk-create-job]` in `query`
- `fields[catalog-variant]` in `query`
- `include` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,48 @@
---
name: catalog-variant-bulk-delete-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-variant-bulk-delete-jobs for the catalog variant bulk delete jobs route group.
---
# catalog variant bulk delete jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-variant-bulk-delete-jobs for the catalog variant bulk delete jobs 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_bulk_delete_variants_jobs
- Operation ID: `get_bulk_delete_variants_jobs`
- Route: `GET /api/catalog-variant-bulk-delete-jobs`
- Mode: READ
- Summary: Get Bulk Delete Variants Jobs
- Parameters:
- `fields[catalog-variant-bulk-delete-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_delete_catalog_variants
- Operation ID: `bulk_delete_catalog_variants`
- Route: `POST /api/catalog-variant-bulk-delete-jobs`
- Mode: WRITE
- Summary: Bulk Delete Catalog Variants
- Parameters:
- `fields[catalog-variant-bulk-delete-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_delete_variants_job
- Operation ID: `get_bulk_delete_variants_job`
- Route: `GET /api/catalog-variant-bulk-delete-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Delete Variants Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-variant-bulk-delete-job]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,50 @@
---
name: catalog-variant-bulk-update-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/catalog-variant-bulk-update-jobs for the catalog variant bulk update jobs route group.
---
# catalog variant bulk update jobs API Routes
Handle 3 OpenAPI operation(s) under /api/catalog-variant-bulk-update-jobs for the catalog variant bulk update jobs 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_bulk_update_variants_jobs
- Operation ID: `get_bulk_update_variants_jobs`
- Route: `GET /api/catalog-variant-bulk-update-jobs`
- Mode: READ
- Summary: Get Bulk Update Variants Jobs
- Parameters:
- `fields[catalog-variant-bulk-update-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_update_catalog_variants
- Operation ID: `bulk_update_catalog_variants`
- Route: `POST /api/catalog-variant-bulk-update-jobs`
- Mode: WRITE
- Summary: Bulk Update Catalog Variants
- Parameters:
- `fields[catalog-variant-bulk-update-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_update_variants_job
- Operation ID: `get_bulk_update_variants_job`
- Route: `GET /api/catalog-variant-bulk-update-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Update Variants Job
- Parameters:
- `job_id` in `path` required
- `fields[catalog-variant-bulk-update-job]` in `query`
- `fields[catalog-variant]` in `query`
- `include` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,72 @@
---
name: catalog-variants-routes
description: Handle 5 OpenAPI operation(s) under /api/catalog-variants for the catalog variants route group.
---
# catalog variants API Routes
Handle 5 OpenAPI operation(s) under /api/catalog-variants for the catalog variants 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_catalog_variants
- Operation ID: `get_catalog_variants`
- Route: `GET /api/catalog-variants`
- Mode: READ
- Summary: Get Catalog Variants
- Parameters:
- `fields[catalog-variant]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_catalog_variant
- Operation ID: `create_catalog_variant`
- Route: `POST /api/catalog-variants`
- Mode: WRITE
- Summary: Create Catalog Variant
- Parameters:
- `fields[catalog-variant]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_catalog_variant
- Operation ID: `get_catalog_variant`
- Route: `GET /api/catalog-variants/{id}`
- Mode: READ
- Summary: Get Catalog Variant
- Parameters:
- `id` in `path` required
- `fields[catalog-variant]` in `query`
- `revision` in `header` required
### update_catalog_variant
- Operation ID: `update_catalog_variant`
- Route: `PATCH /api/catalog-variants/{id}`
- Mode: WRITE
- Summary: Update Catalog Variant
- Parameters:
- `id` in `path` required
- `fields[catalog-variant]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_catalog_variant
- Operation ID: `delete_catalog_variant`
- Route: `DELETE /api/catalog-variants/{id}`
- Mode: WRITE
- Summary: Delete Catalog Variant
- Parameters:
- `id` in `path` required
- `revision` in `header` required

148
skills/client/SKILL.md Normal file
View File

@@ -0,0 +1,148 @@
---
name: client-routes
description: Handle 11 OpenAPI operation(s) under /client for the client route group.
---
# client API Routes
Handle 11 OpenAPI operation(s) under /client for the client 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_client_review_values_reports
- Operation ID: `get_client_review_values_reports`
- Route: `GET /client/review-values-reports`
- Mode: READ
- Summary: Get Client Review Values Reports
- Parameters:
- `company_id` in `query` required
- `fields[review-values-report]` in `query`
- `filter` in `query`
- `group_by` in `query` required
- `page[cursor]` in `query`
- `page[size]` in `query`
- `statistics` in `query` required
- `timeframe` in `query` required
- `revision` in `header` required
### get_client_reviews
- Operation ID: `get_client_reviews`
- Route: `GET /client/reviews`
- Mode: READ
- Summary: Get Client Reviews
- Parameters:
- `company_id` in `query` required
- `fields[review]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_client_review
- Operation ID: `create_client_review`
- Route: `POST /client/reviews`
- Mode: WRITE
- Summary: Create Client Review
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.
### get_client_geofences
- Operation ID: `get_client_geofences`
- Route: `GET /client/geofences`
- Mode: READ
- Summary: Get Client Geofences
- Parameters:
- `company_id` in `query` required
- `fields[geofence]` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `X-Klaviyo-API-Filters` in `header`
- `revision` in `header` required
### create_client_subscription
- Operation ID: `create_client_subscription`
- Route: `POST /client/subscriptions`
- Mode: WRITE
- Summary: Create Client Subscription
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.
### create_client_push_token
- Operation ID: `create_client_push_token`
- Route: `POST /client/push-tokens`
- Mode: WRITE
- Summary: Create or Update Client Push Token
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.
### unregister_client_push_token
- Operation ID: `unregister_client_push_token`
- Route: `POST /client/push-token-unregister`
- Mode: WRITE
- Summary: Unregister Client Push Token
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.
### create_client_event
- Operation ID: `create_client_event`
- Route: `POST /client/events`
- Mode: WRITE
- Summary: Create Client Event
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.
### create_client_profile
- Operation ID: `create_client_profile`
- Route: `POST /client/profiles`
- Mode: WRITE
- Summary: Create or Update Client Profile
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.
### bulk_create_client_events
- Operation ID: `bulk_create_client_events`
- Route: `POST /client/event-bulk-create`
- Mode: WRITE
- Summary: Bulk Create Client Events
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.
### create_client_back_in_stock_subscription
- Operation ID: `create_client_back_in_stock_subscription`
- Route: `POST /client/back-in-stock-subscriptions`
- Mode: WRITE
- Summary: Create Client Back In Stock Subscription
- Parameters:
- `company_id` in `query` required
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,24 @@
---
name: conversation-messages-routes
description: Handle 1 OpenAPI operation(s) under /api/conversation-messages for the conversation messages route group.
---
# conversation messages API Routes
Handle 1 OpenAPI operation(s) under /api/conversation-messages for the conversation messages 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
### create_conversation_message
- Operation ID: `create_conversation_message`
- Route: `POST /api/conversation-messages`
- Mode: WRITE
- Summary: Create Conversation Message
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,50 @@
---
name: coupon-code-bulk-create-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/coupon-code-bulk-create-jobs for the coupon code bulk create jobs route group.
---
# coupon code bulk create jobs API Routes
Handle 3 OpenAPI operation(s) under /api/coupon-code-bulk-create-jobs for the coupon code bulk create jobs 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_bulk_create_coupon_code_jobs
- Operation ID: `get_bulk_create_coupon_code_jobs`
- Route: `GET /api/coupon-code-bulk-create-jobs`
- Mode: READ
- Summary: Get Bulk Create Coupon Code Jobs
- Parameters:
- `fields[coupon-code-bulk-create-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### bulk_create_coupon_codes
- Operation ID: `bulk_create_coupon_codes`
- Route: `POST /api/coupon-code-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Create Coupon Codes
- Parameters:
- `fields[coupon-code-bulk-create-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_create_coupon_codes_job
- Operation ID: `get_bulk_create_coupon_codes_job`
- Route: `GET /api/coupon-code-bulk-create-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Create Coupon Codes Job
- Parameters:
- `job_id` in `path` required
- `fields[coupon-code-bulk-create-job]` in `query`
- `fields[coupon-code]` in `query`
- `include` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,96 @@
---
name: coupon-codes-routes
description: Handle 7 OpenAPI operation(s) under /api/coupon-codes for the coupon codes route group.
---
# coupon codes API Routes
Handle 7 OpenAPI operation(s) under /api/coupon-codes for the coupon codes 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_coupon_codes
- Operation ID: `get_coupon_codes`
- Route: `GET /api/coupon-codes`
- Mode: READ
- Summary: Get Coupon Codes
- Parameters:
- `fields[coupon-code]` in `query`
- `fields[coupon]` in `query`
- `filter` in `query` required
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### create_coupon_code
- Operation ID: `create_coupon_code`
- Route: `POST /api/coupon-codes`
- Mode: WRITE
- Summary: Create Coupon Code
- Parameters:
- `fields[coupon-code]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_coupon_code
- Operation ID: `get_coupon_code`
- Route: `GET /api/coupon-codes/{id}`
- Mode: READ
- Summary: Get Coupon Code
- Parameters:
- `id` in `path` required
- `fields[coupon-code]` in `query`
- `fields[coupon]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_coupon_code
- Operation ID: `update_coupon_code`
- Route: `PATCH /api/coupon-codes/{id}`
- Mode: WRITE
- Summary: Update Coupon Code
- Parameters:
- `id` in `path` required
- `fields[coupon-code]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_coupon_code
- Operation ID: `delete_coupon_code`
- Route: `DELETE /api/coupon-codes/{id}`
- Mode: WRITE
- Summary: Delete Coupon Code
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_coupon_for_coupon_code
- Operation ID: `get_coupon_for_coupon_code`
- Route: `GET /api/coupon-codes/{id}/coupon`
- Mode: READ
- Summary: Get Coupon For Coupon Code
- Parameters:
- `id` in `path` required
- `fields[coupon]` in `query`
- `revision` in `header` required
### get_coupon_id_for_coupon_code
- Operation ID: `get_coupon_id_for_coupon_code`
- Route: `GET /api/coupon-codes/{id}/relationships/coupon`
- Mode: READ
- Summary: Get Coupon ID for Coupon Code
- Parameters:
- `id` in `path` required
- `revision` in `header` required

97
skills/coupons/SKILL.md Normal file
View File

@@ -0,0 +1,97 @@
---
name: coupons-routes
description: Handle 7 OpenAPI operation(s) under /api/coupons for the coupons route group.
---
# coupons API Routes
Handle 7 OpenAPI operation(s) under /api/coupons for the coupons 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_coupons
- Operation ID: `get_coupons`
- Route: `GET /api/coupons`
- Mode: READ
- Summary: Get Coupons
- Parameters:
- `fields[coupon]` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### create_coupon
- Operation ID: `create_coupon`
- Route: `POST /api/coupons`
- Mode: WRITE
- Summary: Create Coupon
- Parameters:
- `fields[coupon]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_coupon
- Operation ID: `get_coupon`
- Route: `GET /api/coupons/{id}`
- Mode: READ
- Summary: Get Coupon
- Parameters:
- `id` in `path` required
- `fields[coupon]` in `query`
- `revision` in `header` required
### update_coupon
- Operation ID: `update_coupon`
- Route: `PATCH /api/coupons/{id}`
- Mode: WRITE
- Summary: Update Coupon
- Parameters:
- `id` in `path` required
- `fields[coupon]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_coupon
- Operation ID: `delete_coupon`
- Route: `DELETE /api/coupons/{id}`
- Mode: WRITE
- Summary: Delete Coupon
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_coupon_codes_for_coupon
- Operation ID: `get_coupon_codes_for_coupon`
- Route: `GET /api/coupons/{id}/coupon-codes`
- Mode: READ
- Summary: Get Coupon Codes for Coupon
- Parameters:
- `id` in `path` required
- `fields[coupon-code]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### get_coupon_code_ids_for_coupon
- Operation ID: `get_coupon_code_ids_for_coupon`
- Route: `GET /api/coupons/{id}/relationships/coupon-codes`
- Mode: READ
- Summary: Get Coupon Code IDs for Coupon
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,93 @@
---
name: custom-metrics-routes
description: Handle 7 OpenAPI operation(s) under /api/custom-metrics for the custom metrics route group.
---
# custom metrics API Routes
Handle 7 OpenAPI operation(s) under /api/custom-metrics for the custom metrics 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_custom_metrics
- Operation ID: `get_custom_metrics`
- Route: `GET /api/custom-metrics`
- Mode: READ
- Summary: Get Custom Metrics
- Parameters:
- `fields[custom-metric]` in `query`
- `fields[metric]` in `query`
- `include` in `query`
- `revision` in `header` required
### create_custom_metric
- Operation ID: `create_custom_metric`
- Route: `POST /api/custom-metrics`
- Mode: WRITE
- Summary: Create Custom Metric
- Parameters:
- `fields[custom-metric]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_custom_metric
- Operation ID: `get_custom_metric`
- Route: `GET /api/custom-metrics/{id}`
- Mode: READ
- Summary: Get Custom Metric
- Parameters:
- `id` in `path` required
- `fields[custom-metric]` in `query`
- `fields[metric]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_custom_metric
- Operation ID: `update_custom_metric`
- Route: `PATCH /api/custom-metrics/{id}`
- Mode: WRITE
- Summary: Update Custom Metric
- Parameters:
- `id` in `path` required
- `fields[custom-metric]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_custom_metric
- Operation ID: `delete_custom_metric`
- Route: `DELETE /api/custom-metrics/{id}`
- Mode: WRITE
- Summary: Delete Custom Metric
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_metrics_for_custom_metric
- Operation ID: `get_metrics_for_custom_metric`
- Route: `GET /api/custom-metrics/{id}/metrics`
- Mode: READ
- Summary: Get Metrics for Custom Metric
- Parameters:
- `id` in `path` required
- `fields[metric]` in `query`
- `revision` in `header` required
### get_metric_ids_for_custom_metric
- Operation ID: `get_metric_ids_for_custom_metric`
- Route: `GET /api/custom-metrics/{id}/relationships/metrics`
- Mode: READ
- Summary: Get Metric IDs for Custom Metric
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,24 @@
---
name: data-privacy-deletion-jobs-routes
description: Handle 1 OpenAPI operation(s) under /api/data-privacy-deletion-jobs for the data privacy deletion jobs route group.
---
# data privacy deletion jobs API Routes
Handle 1 OpenAPI operation(s) under /api/data-privacy-deletion-jobs for the data privacy deletion jobs 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
### request_profile_deletion
- Operation ID: `request_profile_deletion`
- Route: `POST /api/data-privacy-deletion-jobs`
- Mode: WRITE
- Summary: Request Profile Deletion
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,24 @@
---
name: data-source-record-bulk-create-jobs-routes
description: Handle 1 OpenAPI operation(s) under /api/data-source-record-bulk-create-jobs for the data source record bulk create jobs route group.
---
# data source record bulk create jobs API Routes
Handle 1 OpenAPI operation(s) under /api/data-source-record-bulk-create-jobs for the data source record bulk create jobs 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
### bulk_create_data_source_records
- Operation ID: `bulk_create_data_source_records`
- Route: `POST /api/data-source-record-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Create Data Source Records
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,24 @@
---
name: data-source-record-create-jobs-routes
description: Handle 1 OpenAPI operation(s) under /api/data-source-record-create-jobs for the data source record create jobs route group.
---
# data source record create jobs API Routes
Handle 1 OpenAPI operation(s) under /api/data-source-record-create-jobs for the data source record create jobs 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
### create_data_source_record
- Operation ID: `create_data_source_record`
- Route: `POST /api/data-source-record-create-jobs`
- Mode: WRITE
- Summary: Create Data Source Record
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,58 @@
---
name: data-sources-routes
description: Handle 4 OpenAPI operation(s) under /api/data-sources for the data sources route group.
---
# data sources API Routes
Handle 4 OpenAPI operation(s) under /api/data-sources for the data sources 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_data_sources
- Operation ID: `get_data_sources`
- Route: `GET /api/data-sources`
- Mode: READ
- Summary: Get Data Sources
- Parameters:
- `fields[data-source]` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### create_data_source
- Operation ID: `create_data_source`
- Route: `POST /api/data-sources`
- Mode: WRITE
- Summary: Create Data Source
- Parameters:
- `fields[data-source]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_data_source
- Operation ID: `get_data_source`
- Route: `GET /api/data-sources/{id}`
- Mode: READ
- Summary: Get Data Source
- Parameters:
- `id` in `path` required
- `fields[data-source]` in `query`
- `revision` in `header` required
### delete_data_source
- Operation ID: `delete_data_source`
- Route: `DELETE /api/data-sources/{id}`
- Mode: WRITE
- Summary: Delete Data Source
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,24 @@
---
name: event-bulk-create-jobs-routes
description: Handle 1 OpenAPI operation(s) under /api/event-bulk-create-jobs for the event bulk create jobs route group.
---
# event bulk create jobs API Routes
Handle 1 OpenAPI operation(s) under /api/event-bulk-create-jobs for the event bulk create jobs 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
### bulk_create_events
- Operation ID: `bulk_create_events`
- Route: `POST /api/event-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Create Events
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

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

@@ -0,0 +1,100 @@
---
name: events-routes
description: Handle 7 OpenAPI operation(s) under /api/events for the events route group.
---
# events API Routes
Handle 7 OpenAPI operation(s) under /api/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
### get_events
- Operation ID: `get_events`
- Route: `GET /api/events`
- Mode: READ
- Summary: Get Events
- Parameters:
- `fields[attribution]` in `query`
- `fields[event]` in `query`
- `fields[metric]` in `query`
- `fields[profile]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_event
- Operation ID: `create_event`
- Route: `POST /api/events`
- Mode: WRITE
- Summary: Create Event
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.
### get_event
- Operation ID: `get_event`
- Route: `GET /api/events/{id}`
- Mode: READ
- Summary: Get Event
- Parameters:
- `id` in `path` required
- `fields[attribution]` in `query`
- `fields[event]` in `query`
- `fields[metric]` in `query`
- `fields[profile]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_metric_for_event
- Operation ID: `get_metric_for_event`
- Route: `GET /api/events/{id}/metric`
- Mode: READ
- Summary: Get Metric for Event
- Parameters:
- `id` in `path` required
- `fields[metric]` in `query`
- `revision` in `header` required
### get_metric_id_for_event
- Operation ID: `get_metric_id_for_event`
- Route: `GET /api/events/{id}/relationships/metric`
- Mode: READ
- Summary: Get Metric ID for Event
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_profile_for_event
- Operation ID: `get_profile_for_event`
- Route: `GET /api/events/{id}/profile`
- Mode: READ
- Summary: Get Profile for Event
- Parameters:
- `id` in `path` required
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `revision` in `header` required
### get_profile_id_for_event
- Operation ID: `get_profile_id_for_event`
- Route: `GET /api/events/{id}/relationships/profile`
- Mode: READ
- Summary: Get Profile ID for Event
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,100 @@
---
name: flow-actions-routes
description: Handle 7 OpenAPI operation(s) under /api/flow-actions/{id} for the flow actions route group.
---
# flow actions API Routes
Handle 7 OpenAPI operation(s) under /api/flow-actions/{id} for the flow actions 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_flow_action
- Operation ID: `get_flow_action`
- Route: `GET /api/flow-actions/{id}`
- Mode: READ
- Summary: Get Flow Action
- Parameters:
- `id` in `path` required
- `fields[flow-action]` in `query`
- `fields[flow-message]` in `query`
- `fields[flow]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_flow_action
- Operation ID: `update_flow_action`
- Route: `PATCH /api/flow-actions/{id}`
- Mode: WRITE
- Summary: Update Flow Action
- Parameters:
- `id` in `path` required
- `fields[flow-action]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_flow_action
- Operation ID: `delete_flow_action`
- Route: `DELETE /api/flow-actions/{id}`
- Mode: WRITE
- Summary: Delete Flow Action
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_flow_for_flow_action
- Operation ID: `get_flow_for_flow_action`
- Route: `GET /api/flow-actions/{id}/flow`
- Mode: READ
- Summary: Get Flow for Flow Action
- Parameters:
- `id` in `path` required
- `fields[flow]` in `query`
- `revision` in `header` required
### get_flow_id_for_flow_action
- Operation ID: `get_flow_id_for_flow_action`
- Route: `GET /api/flow-actions/{id}/relationships/flow`
- Mode: READ
- Summary: Get Flow ID for Flow Action
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_flow_action_messages
- Operation ID: `get_flow_action_messages`
- Route: `GET /api/flow-actions/{id}/flow-messages`
- Mode: READ
- Summary: Get Messages For Flow Action
- Parameters:
- `id` in `path` required
- `fields[flow-message]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_message_ids_for_flow_action
- Operation ID: `get_message_ids_for_flow_action`
- Route: `GET /api/flow-actions/{id}/relationships/flow-messages`
- Mode: READ
- Summary: Get Message IDs for Flow Action
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,70 @@
---
name: flow-messages-routes
description: Handle 5 OpenAPI operation(s) under /api/flow-messages/{id} for the flow messages route group.
---
# flow messages API Routes
Handle 5 OpenAPI operation(s) under /api/flow-messages/{id} for the flow messages 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_flow_message
- Operation ID: `get_flow_message`
- Route: `GET /api/flow-messages/{id}`
- Mode: READ
- Summary: Get Flow Message
- Parameters:
- `id` in `path` required
- `fields[flow-action]` in `query`
- `fields[flow-message]` in `query`
- `fields[template]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_action_for_flow_message
- Operation ID: `get_action_for_flow_message`
- Route: `GET /api/flow-messages/{id}/flow-action`
- Mode: READ
- Summary: Get Action for Flow Message
- Parameters:
- `id` in `path` required
- `fields[flow-action]` in `query`
- `revision` in `header` required
### get_action_id_for_flow_message
- Operation ID: `get_action_id_for_flow_message`
- Route: `GET /api/flow-messages/{id}/relationships/flow-action`
- Mode: READ
- Summary: Get Action ID for Flow Message
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_template_for_flow_message
- Operation ID: `get_template_for_flow_message`
- Route: `GET /api/flow-messages/{id}/template`
- Mode: READ
- Summary: Get Template for Flow Message
- Parameters:
- `id` in `path` required
- `fields[template]` in `query`
- `revision` in `header` required
### get_template_id_for_flow_message
- Operation ID: `get_template_id_for_flow_message`
- Route: `GET /api/flow-messages/{id}/relationships/template`
- Mode: READ
- Summary: Get Template ID for Flow Message
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,26 @@
---
name: flow-series-reports-routes
description: Handle 1 OpenAPI operation(s) under /api/flow-series-reports for the flow series reports route group.
---
# flow series reports API Routes
Handle 1 OpenAPI operation(s) under /api/flow-series-reports for the flow series 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
### query_flow_series
- Operation ID: `query_flow_series`
- Route: `POST /api/flow-series-reports`
- Mode: WRITE
- Summary: Query Flow Series
- Parameters:
- `fields[flow-series-report]` in `query`
- `page_cursor` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,26 @@
---
name: flow-values-reports-routes
description: Handle 1 OpenAPI operation(s) under /api/flow-values-reports for the flow values reports route group.
---
# flow values reports API Routes
Handle 1 OpenAPI operation(s) under /api/flow-values-reports for the flow values 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
### query_flow_values
- Operation ID: `query_flow_values`
- Route: `POST /api/flow-values-reports`
- Mode: WRITE
- Summary: Query Flow Values
- Parameters:
- `fields[flow-values-report]` in `query`
- `page_cursor` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

130
skills/flows/SKILL.md Normal file
View File

@@ -0,0 +1,130 @@
---
name: flows-routes
description: Handle 9 OpenAPI operation(s) under /api/flows for the flows route group.
---
# flows API Routes
Handle 9 OpenAPI operation(s) under /api/flows for the flows 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_flows
- Operation ID: `get_flows`
- Route: `GET /api/flows`
- Mode: READ
- Summary: Get Flows
- Parameters:
- `fields[flow-action]` in `query`
- `fields[flow]` in `query`
- `fields[tag]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_flow
- Operation ID: `create_flow`
- Route: `POST /api/flows`
- Mode: WRITE
- Summary: Create Flow
- Parameters:
- `additional-fields[flow]` in `query`
- `fields[flow]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_flow
- Operation ID: `get_flow`
- Route: `GET /api/flows/{id}`
- Mode: READ
- Summary: Get Flow
- Parameters:
- `id` in `path` required
- `additional-fields[flow]` in `query`
- `fields[flow-action]` in `query`
- `fields[flow]` in `query`
- `fields[tag]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_flow
- Operation ID: `update_flow`
- Route: `PATCH /api/flows/{id}`
- Mode: WRITE
- Summary: Update Flow Status
- Parameters:
- `id` in `path` required
- `fields[flow]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_flow
- Operation ID: `delete_flow`
- Route: `DELETE /api/flows/{id}`
- Mode: WRITE
- Summary: Delete Flow
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_actions_for_flow
- Operation ID: `get_actions_for_flow`
- Route: `GET /api/flows/{id}/flow-actions`
- Mode: READ
- Summary: Get Actions for Flow
- Parameters:
- `id` in `path` required
- `fields[flow-action]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_action_ids_for_flow
- Operation ID: `get_action_ids_for_flow`
- Route: `GET /api/flows/{id}/relationships/flow-actions`
- Mode: READ
- Summary: Get Action IDs for Flow
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_tags_for_flow
- Operation ID: `get_tags_for_flow`
- Route: `GET /api/flows/{id}/tags`
- Mode: READ
- Summary: Get Tags for Flow
- Parameters:
- `id` in `path` required
- `fields[tag]` in `query`
- `revision` in `header` required
### get_tag_ids_for_flow
- Operation ID: `get_tag_ids_for_flow`
- Route: `GET /api/flows/{id}/relationships/tags`
- Mode: READ
- Summary: Get Tag IDs for Flow
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,25 @@
---
name: form-series-reports-routes
description: Handle 1 OpenAPI operation(s) under /api/form-series-reports for the form series reports route group.
---
# form series reports API Routes
Handle 1 OpenAPI operation(s) under /api/form-series-reports for the form series 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
### query_form_series
- Operation ID: `query_form_series`
- Route: `POST /api/form-series-reports`
- Mode: WRITE
- Summary: Query Form Series
- Parameters:
- `fields[form-series-report]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: form-values-reports-routes
description: Handle 1 OpenAPI operation(s) under /api/form-values-reports for the form values reports route group.
---
# form values reports API Routes
Handle 1 OpenAPI operation(s) under /api/form-values-reports for the form values 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
### query_form_values
- Operation ID: `query_form_values`
- Route: `POST /api/form-values-reports`
- Mode: WRITE
- Summary: Query Form Values
- Parameters:
- `fields[form-values-report]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,48 @@
---
name: form-versions-routes
description: Handle 3 OpenAPI operation(s) under /api/form-versions/{id} for the form versions route group.
---
# form versions API Routes
Handle 3 OpenAPI operation(s) under /api/form-versions/{id} for the form versions 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_form_version
- Operation ID: `get_form_version`
- Route: `GET /api/form-versions/{id}`
- Mode: READ
- Summary: Get Form Version
- Parameters:
- `id` in `path` required
- `fields[form-version]` in `query`
- `fields[form]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_form_for_form_version
- Operation ID: `get_form_for_form_version`
- Route: `GET /api/form-versions/{id}/form`
- Mode: READ
- Summary: Get Form for Form Version
- Parameters:
- `id` in `path` required
- `fields[form]` in `query`
- `revision` in `header` required
### get_form_id_for_form_version
- Operation ID: `get_form_id_for_form_version`
- Route: `GET /api/form-versions/{id}/relationships/form`
- Mode: READ
- Summary: Get Form ID for Form Version
- Parameters:
- `id` in `path` required
- `revision` in `header` required

89
skills/forms/SKILL.md Normal file
View File

@@ -0,0 +1,89 @@
---
name: forms-routes
description: Handle 6 OpenAPI operation(s) under /api/forms for the forms route group.
---
# forms API Routes
Handle 6 OpenAPI operation(s) under /api/forms for the forms 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_forms
- Operation ID: `get_forms`
- Route: `GET /api/forms`
- Mode: READ
- Summary: Get Forms
- Parameters:
- `fields[form]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_form
- Operation ID: `create_form`
- Route: `POST /api/forms`
- Mode: WRITE
- Summary: Create Form
- Parameters:
- `fields[form]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_form
- Operation ID: `get_form`
- Route: `GET /api/forms/{id}`
- Mode: READ
- Summary: Get Form
- Parameters:
- `id` in `path` required
- `fields[form]` in `query`
- `revision` in `header` required
### delete_form
- Operation ID: `delete_form`
- Route: `DELETE /api/forms/{id}`
- Mode: WRITE
- Summary: Delete Form
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_versions_for_form
- Operation ID: `get_versions_for_form`
- Route: `GET /api/forms/{id}/form-versions`
- Mode: READ
- Summary: Get Versions for Form
- Parameters:
- `id` in `path` required
- `fields[form-version]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_version_ids_for_form
- Operation ID: `get_version_ids_for_form`
- Route: `GET /api/forms/{id}/relationships/form-versions`
- Mode: READ
- Summary: Get Version IDs for Form
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,25 @@
---
name: image-upload-routes
description: Handle 1 OpenAPI operation(s) under /api/image-upload for the image upload route group.
---
# image upload API Routes
Handle 1 OpenAPI operation(s) under /api/image-upload for the image upload 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
### upload_image_from_file
- Operation ID: `upload_image_from_file`
- Route: `POST /api/image-upload`
- Mode: WRITE
- Summary: Upload Image From File
- Parameters:
- `fields[image]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

62
skills/images/SKILL.md Normal file
View File

@@ -0,0 +1,62 @@
---
name: images-routes
description: Handle 4 OpenAPI operation(s) under /api/images for the images route group.
---
# images API Routes
Handle 4 OpenAPI operation(s) under /api/images for the images 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_images
- Operation ID: `get_images`
- Route: `GET /api/images`
- Mode: READ
- Summary: Get Images
- Parameters:
- `fields[image]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### upload_image_from_url
- Operation ID: `upload_image_from_url`
- Route: `POST /api/images`
- Mode: WRITE
- Summary: Upload Image From URL
- Parameters:
- `fields[image]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_image
- Operation ID: `get_image`
- Route: `GET /api/images/{id}`
- Mode: READ
- Summary: Get Image
- Parameters:
- `id` in `path` required
- `fields[image]` in `query`
- `revision` in `header` required
### update_image
- Operation ID: `update_image`
- Route: `PATCH /api/images/{id}`
- Mode: WRITE
- Summary: Update Image
- Parameters:
- `id` in `path` required
- `fields[image]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

173
skills/lists/SKILL.md Normal file
View File

@@ -0,0 +1,173 @@
---
name: lists-routes
description: Handle 13 OpenAPI operation(s) under /api/lists for the lists route group.
---
# lists API Routes
Handle 13 OpenAPI operation(s) under /api/lists for the lists 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_lists
- Operation ID: `get_lists`
- Route: `GET /api/lists`
- Mode: READ
- Summary: Get Lists
- Parameters:
- `fields[flow]` in `query`
- `fields[list]` in `query`
- `fields[tag]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_list
- Operation ID: `create_list`
- Route: `POST /api/lists`
- Mode: WRITE
- Summary: Create List
- Parameters:
- `fields[list]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_list
- Operation ID: `get_list`
- Route: `GET /api/lists/{id}`
- Mode: READ
- Summary: Get List
- Parameters:
- `id` in `path` required
- `additional-fields[list]` in `query`
- `fields[flow]` in `query`
- `fields[list]` in `query`
- `fields[tag]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_list
- Operation ID: `update_list`
- Route: `PATCH /api/lists/{id}`
- Mode: WRITE
- Summary: Update List
- Parameters:
- `id` in `path` required
- `fields[list]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_list
- Operation ID: `delete_list`
- Route: `DELETE /api/lists/{id}`
- Mode: WRITE
- Summary: Delete List
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_tags_for_list
- Operation ID: `get_tags_for_list`
- Route: `GET /api/lists/{id}/tags`
- Mode: READ
- Summary: Get Tags for List
- Parameters:
- `id` in `path` required
- `fields[tag]` in `query`
- `revision` in `header` required
### get_tag_ids_for_list
- Operation ID: `get_tag_ids_for_list`
- Route: `GET /api/lists/{id}/relationships/tags`
- Mode: READ
- Summary: Get Tag IDs for List
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_profiles_for_list
- Operation ID: `get_profiles_for_list`
- Route: `GET /api/lists/{id}/profiles`
- Mode: READ
- Summary: Get Profiles for List
- Parameters:
- `id` in `path` required
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_profile_ids_for_list
- Operation ID: `get_profile_ids_for_list`
- Route: `GET /api/lists/{id}/relationships/profiles`
- Mode: READ
- Summary: Get Profile IDs for List
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### add_profiles_to_list
- Operation ID: `add_profiles_to_list`
- Route: `POST /api/lists/{id}/relationships/profiles`
- Mode: WRITE
- Summary: Add Profiles to List
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### remove_profiles_from_list
- Operation ID: `remove_profiles_from_list`
- Route: `DELETE /api/lists/{id}/relationships/profiles`
- Mode: WRITE
- Summary: Remove Profiles from List
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### get_flows_triggered_by_list
- Operation ID: `get_flows_triggered_by_list`
- Route: `GET /api/lists/{id}/flow-triggers`
- Mode: READ
- Summary: Get Flows Triggered by List
- Parameters:
- `id` in `path` required
- `fields[flow]` in `query`
- `revision` in `header` required
### get_ids_for_flows_triggered_by_list
- Operation ID: `get_ids_for_flows_triggered_by_list`
- Route: `GET /api/lists/{id}/relationships/flow-triggers`
- Mode: READ
- Summary: Get IDs for Flows Triggered by List
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,95 @@
---
name: mapped-metrics-routes
description: Handle 7 OpenAPI operation(s) under /api/mapped-metrics for the mapped metrics route group.
---
# mapped metrics API Routes
Handle 7 OpenAPI operation(s) under /api/mapped-metrics for the mapped metrics 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_mapped_metrics
- Operation ID: `get_mapped_metrics`
- Route: `GET /api/mapped-metrics`
- Mode: READ
- Summary: Get Mapped Metrics
- Parameters:
- `fields[custom-metric]` in `query`
- `fields[mapped-metric]` in `query`
- `fields[metric]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_mapped_metric
- Operation ID: `get_mapped_metric`
- Route: `GET /api/mapped-metrics/{id}`
- Mode: READ
- Summary: Get Mapped Metric
- Parameters:
- `id` in `path` required
- `fields[custom-metric]` in `query`
- `fields[mapped-metric]` in `query`
- `fields[metric]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_mapped_metric
- Operation ID: `update_mapped_metric`
- Route: `PATCH /api/mapped-metrics/{id}`
- Mode: WRITE
- Summary: Update Mapped Metric
- Parameters:
- `id` in `path` required
- `fields[mapped-metric]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_metric_for_mapped_metric
- Operation ID: `get_metric_for_mapped_metric`
- Route: `GET /api/mapped-metrics/{id}/metric`
- Mode: READ
- Summary: Get Metric for Mapped Metric
- Parameters:
- `id` in `path` required
- `fields[metric]` in `query`
- `revision` in `header` required
### get_metric_id_for_mapped_metric
- Operation ID: `get_metric_id_for_mapped_metric`
- Route: `GET /api/mapped-metrics/{id}/relationships/metric`
- Mode: READ
- Summary: Get Metric ID for Mapped Metric
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_custom_metric_for_mapped_metric
- Operation ID: `get_custom_metric_for_mapped_metric`
- Route: `GET /api/mapped-metrics/{id}/custom-metric`
- Mode: READ
- Summary: Get Custom Metric for Mapped Metric
- Parameters:
- `id` in `path` required
- `fields[custom-metric]` in `query`
- `revision` in `header` required
### get_custom_metric_id_for_mapped_metric
- Operation ID: `get_custom_metric_id_for_mapped_metric`
- Route: `GET /api/mapped-metrics/{id}/relationships/custom-metric`
- Mode: READ
- Summary: Get Custom Metric ID for Mapped Metric
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,25 @@
---
name: metric-aggregates-routes
description: Handle 1 OpenAPI operation(s) under /api/metric-aggregates for the metric aggregates route group.
---
# metric aggregates API Routes
Handle 1 OpenAPI operation(s) under /api/metric-aggregates for the metric aggregates 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
### query_metric_aggregates
- Operation ID: `query_metric_aggregates`
- Route: `POST /api/metric-aggregates`
- Mode: WRITE
- Summary: Query Metric Aggregates
- Parameters:
- `fields[metric-aggregate]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,49 @@
---
name: metric-properties-routes
description: Handle 3 OpenAPI operation(s) under /api/metric-properties/{id} for the metric properties route group.
---
# metric properties API Routes
Handle 3 OpenAPI operation(s) under /api/metric-properties/{id} for the metric properties 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_metric_property
- Operation ID: `get_metric_property`
- Route: `GET /api/metric-properties/{id}`
- Mode: READ
- Summary: Get Metric Property
- Parameters:
- `id` in `path` required
- `additional-fields[metric-property]` in `query`
- `fields[metric-property]` in `query`
- `fields[metric]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_metric_for_metric_property
- Operation ID: `get_metric_for_metric_property`
- Route: `GET /api/metric-properties/{id}/metric`
- Mode: READ
- Summary: Get Metric for Metric Property
- Parameters:
- `id` in `path` required
- `fields[metric]` in `query`
- `revision` in `header` required
### get_metric_id_for_metric_property
- Operation ID: `get_metric_id_for_metric_property`
- Route: `GET /api/metric-properties/{id}/relationships/metric`
- Mode: READ
- Summary: Get Metric ID for Metric Property
- Parameters:
- `id` in `path` required
- `revision` in `header` required

84
skills/metrics/SKILL.md Normal file
View File

@@ -0,0 +1,84 @@
---
name: metrics-routes
description: Handle 6 OpenAPI operation(s) under /api/metrics for the metrics route group.
---
# metrics API Routes
Handle 6 OpenAPI operation(s) under /api/metrics for the metrics 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_metrics
- Operation ID: `get_metrics`
- Route: `GET /api/metrics`
- Mode: READ
- Summary: Get Metrics
- Parameters:
- `fields[flow]` in `query`
- `fields[metric]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `revision` in `header` required
### get_metric
- Operation ID: `get_metric`
- Route: `GET /api/metrics/{id}`
- Mode: READ
- Summary: Get Metric
- Parameters:
- `id` in `path` required
- `fields[flow]` in `query`
- `fields[metric]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_flows_triggered_by_metric
- Operation ID: `get_flows_triggered_by_metric`
- Route: `GET /api/metrics/{id}/flow-triggers`
- Mode: READ
- Summary: Get Flows Triggered by Metric
- Parameters:
- `id` in `path` required
- `fields[flow]` in `query`
- `revision` in `header` required
### get_ids_for_flows_triggered_by_metric
- Operation ID: `get_ids_for_flows_triggered_by_metric`
- Route: `GET /api/metrics/{id}/relationships/flow-triggers`
- Mode: READ
- Summary: Get IDs for Flows Triggered by Metric
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_properties_for_metric
- Operation ID: `get_properties_for_metric`
- Route: `GET /api/metrics/{id}/metric-properties`
- Mode: READ
- Summary: Get Properties for Metric
- Parameters:
- `id` in `path` required
- `additional-fields[metric-property]` in `query`
- `fields[metric-property]` in `query`
- `revision` in `header` required
### get_property_ids_for_metric
- Operation ID: `get_property_ids_for_metric`
- Route: `GET /api/metrics/{id}/relationships/metric-properties`
- Mode: READ
- Summary: Get Property IDs for Metric
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,112 @@
---
name: profile-bulk-import-jobs-routes
description: Handle 8 OpenAPI operation(s) under /api/profile-bulk-import-jobs for the profile bulk import jobs route group.
---
# profile bulk import jobs API Routes
Handle 8 OpenAPI operation(s) under /api/profile-bulk-import-jobs for the profile bulk import jobs 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_bulk_import_profiles_jobs
- Operation ID: `get_bulk_import_profiles_jobs`
- Route: `GET /api/profile-bulk-import-jobs`
- Mode: READ
- Summary: Get Bulk Import Profiles Jobs
- Parameters:
- `fields[profile-bulk-import-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### bulk_import_profiles
- Operation ID: `bulk_import_profiles`
- Route: `POST /api/profile-bulk-import-jobs`
- Mode: WRITE
- Summary: Bulk Import Profiles
- Parameters:
- `fields[profile-bulk-import-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_import_profiles_job
- Operation ID: `get_bulk_import_profiles_job`
- Route: `GET /api/profile-bulk-import-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Import Profiles Job
- Parameters:
- `job_id` in `path` required
- `fields[list]` in `query`
- `fields[profile-bulk-import-job]` in `query`
- `include` in `query`
- `revision` in `header` required
### get_list_for_bulk_import_profiles_job
- Operation ID: `get_list_for_bulk_import_profiles_job`
- Route: `GET /api/profile-bulk-import-jobs/{id}/lists`
- Mode: READ
- Summary: Get List for Bulk Import Profiles Job
- Parameters:
- `id` in `path` required
- `fields[list]` in `query`
- `revision` in `header` required
### get_list_ids_for_bulk_import_profiles_job
- Operation ID: `get_list_ids_for_bulk_import_profiles_job`
- Route: `GET /api/profile-bulk-import-jobs/{id}/relationships/lists`
- Mode: READ
- Summary: Get List IDs for Bulk Import Profiles Job
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_profiles_for_bulk_import_profiles_job
- Operation ID: `get_profiles_for_bulk_import_profiles_job`
- Route: `GET /api/profile-bulk-import-jobs/{id}/profiles`
- Mode: READ
- Summary: Get Profiles for Bulk Import Profiles Job
- Parameters:
- `id` in `path` required
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### get_profile_ids_for_bulk_import_profiles_job
- Operation ID: `get_profile_ids_for_bulk_import_profiles_job`
- Route: `GET /api/profile-bulk-import-jobs/{id}/relationships/profiles`
- Mode: READ
- Summary: Get Profile IDs for Bulk Import Profiles Job
- Parameters:
- `id` in `path` required
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### get_errors_for_bulk_import_profiles_job
- Operation ID: `get_errors_for_bulk_import_profiles_job`
- Route: `GET /api/profile-bulk-import-jobs/{id}/import-errors`
- Mode: READ
- Summary: Get Errors for Bulk Import Profiles Job
- Parameters:
- `id` in `path` required
- `fields[import-error]` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,26 @@
---
name: profile-import-routes
description: Handle 1 OpenAPI operation(s) under /api/profile-import for the profile import route group.
---
# profile import API Routes
Handle 1 OpenAPI operation(s) under /api/profile-import for the profile import 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
### create_or_update_profile
- Operation ID: `create_or_update_profile`
- Route: `POST /api/profile-import`
- Mode: WRITE
- Summary: Create or Update Profile
- Parameters:
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: profile-merge-routes
description: Handle 1 OpenAPI operation(s) under /api/profile-merge for the profile merge route group.
---
# profile merge API Routes
Handle 1 OpenAPI operation(s) under /api/profile-merge for the profile merge 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
### merge_profiles
- Operation ID: `merge_profiles`
- Route: `POST /api/profile-merge`
- Mode: WRITE
- Summary: Merge Profiles
- Parameters:
- `fields[profile]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,24 @@
---
name: profile-subscription-bulk-create-jobs-routes
description: Handle 1 OpenAPI operation(s) under /api/profile-subscription-bulk-create-jobs for the profile subscription bulk create jobs route group.
---
# profile subscription bulk create jobs API Routes
Handle 1 OpenAPI operation(s) under /api/profile-subscription-bulk-create-jobs for the profile subscription bulk create jobs 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
### bulk_subscribe_profiles
- Operation ID: `bulk_subscribe_profiles`
- Route: `POST /api/profile-subscription-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Subscribe Profiles
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,24 @@
---
name: profile-subscription-bulk-delete-jobs-routes
description: Handle 1 OpenAPI operation(s) under /api/profile-subscription-bulk-delete-jobs for the profile subscription bulk delete jobs route group.
---
# profile subscription bulk delete jobs API Routes
Handle 1 OpenAPI operation(s) under /api/profile-subscription-bulk-delete-jobs for the profile subscription bulk delete jobs 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
### bulk_unsubscribe_profiles
- Operation ID: `bulk_unsubscribe_profiles`
- Route: `POST /api/profile-subscription-bulk-delete-jobs`
- Mode: WRITE
- Summary: Bulk Unsubscribe Profiles
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,49 @@
---
name: profile-suppression-bulk-create-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/profile-suppression-bulk-create-jobs for the profile suppression bulk create jobs route group.
---
# profile suppression bulk create jobs API Routes
Handle 3 OpenAPI operation(s) under /api/profile-suppression-bulk-create-jobs for the profile suppression bulk create jobs 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_bulk_suppress_profiles_jobs
- Operation ID: `get_bulk_suppress_profiles_jobs`
- Route: `GET /api/profile-suppression-bulk-create-jobs`
- Mode: READ
- Summary: Get Bulk Suppress Profiles Jobs
- Parameters:
- `fields[profile-suppression-bulk-create-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `sort` in `query`
- `revision` in `header` required
### bulk_suppress_profiles
- Operation ID: `bulk_suppress_profiles`
- Route: `POST /api/profile-suppression-bulk-create-jobs`
- Mode: WRITE
- Summary: Bulk Suppress Profiles
- Parameters:
- `fields[profile-suppression-bulk-create-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_suppress_profiles_job
- Operation ID: `get_bulk_suppress_profiles_job`
- Route: `GET /api/profile-suppression-bulk-create-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Suppress Profiles Job
- Parameters:
- `job_id` in `path` required
- `fields[profile-suppression-bulk-create-job]` in `query`
- `revision` in `header` required

View File

@@ -0,0 +1,49 @@
---
name: profile-suppression-bulk-delete-jobs-routes
description: Handle 3 OpenAPI operation(s) under /api/profile-suppression-bulk-delete-jobs for the profile suppression bulk delete jobs route group.
---
# profile suppression bulk delete jobs API Routes
Handle 3 OpenAPI operation(s) under /api/profile-suppression-bulk-delete-jobs for the profile suppression bulk delete jobs 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_bulk_unsuppress_profiles_jobs
- Operation ID: `get_bulk_unsuppress_profiles_jobs`
- Route: `GET /api/profile-suppression-bulk-delete-jobs`
- Mode: READ
- Summary: Get Bulk Unsuppress Profiles Jobs
- Parameters:
- `fields[profile-suppression-bulk-delete-job]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `sort` in `query`
- `revision` in `header` required
### bulk_unsuppress_profiles
- Operation ID: `bulk_unsuppress_profiles`
- Route: `POST /api/profile-suppression-bulk-delete-jobs`
- Mode: WRITE
- Summary: Bulk Unsuppress Profiles
- Parameters:
- `fields[profile-suppression-bulk-delete-job]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_bulk_unsuppress_profiles_job
- Operation ID: `get_bulk_unsuppress_profiles_job`
- Route: `GET /api/profile-suppression-bulk-delete-jobs/{job_id}`
- Mode: READ
- Summary: Get Bulk Unsuppress Profiles Job
- Parameters:
- `job_id` in `path` required
- `fields[profile-suppression-bulk-delete-job]` in `query`
- `revision` in `header` required

158
skills/profiles/SKILL.md Normal file
View File

@@ -0,0 +1,158 @@
---
name: profiles-routes
description: Handle 12 OpenAPI operation(s) under /api/profiles for the profiles route group.
---
# profiles API Routes
Handle 12 OpenAPI operation(s) under /api/profiles for the profiles 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_profiles
- Operation ID: `get_profiles`
- Route: `GET /api/profiles`
- Mode: READ
- Summary: Get Profiles
- Parameters:
- `additional-fields[profile]` in `query`
- `fields[conversation]` in `query`
- `fields[profile]` in `query`
- `fields[push-token]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_profile
- Operation ID: `create_profile`
- Route: `POST /api/profiles`
- Mode: WRITE
- Summary: Create Profile
- Parameters:
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_profile
- Operation ID: `get_profile`
- Route: `GET /api/profiles/{id}`
- Mode: READ
- Summary: Get Profile
- Parameters:
- `id` in `path` required
- `additional-fields[profile]` in `query`
- `fields[conversation]` in `query`
- `fields[list]` in `query`
- `fields[profile]` in `query`
- `fields[push-token]` in `query`
- `fields[segment]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_profile
- Operation ID: `update_profile`
- Route: `PATCH /api/profiles/{id}`
- Mode: WRITE
- Summary: Update Profile
- Parameters:
- `id` in `path` required
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_push_tokens_for_profile
- Operation ID: `get_push_tokens_for_profile`
- Route: `GET /api/profiles/{id}/push-tokens`
- Mode: READ
- Summary: Get Push Tokens for Profile
- Parameters:
- `id` in `path` required
- `fields[push-token]` in `query`
- `revision` in `header` required
### get_push_token_ids_for_profile
- Operation ID: `get_push_token_ids_for_profile`
- Route: `GET /api/profiles/{id}/relationships/push-tokens`
- Mode: READ
- Summary: Get Push Token IDs for Profile
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_lists_for_profile
- Operation ID: `get_lists_for_profile`
- Route: `GET /api/profiles/{id}/lists`
- Mode: READ
- Summary: Get Lists for Profile
- Parameters:
- `id` in `path` required
- `fields[list]` in `query`
- `revision` in `header` required
### get_list_ids_for_profile
- Operation ID: `get_list_ids_for_profile`
- Route: `GET /api/profiles/{id}/relationships/lists`
- Mode: READ
- Summary: Get List IDs for Profile
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_segments_for_profile
- Operation ID: `get_segments_for_profile`
- Route: `GET /api/profiles/{id}/segments`
- Mode: READ
- Summary: Get Segments for Profile
- Parameters:
- `id` in `path` required
- `fields[segment]` in `query`
- `revision` in `header` required
### get_segment_ids_for_profile
- Operation ID: `get_segment_ids_for_profile`
- Route: `GET /api/profiles/{id}/relationships/segments`
- Mode: READ
- Summary: Get Segment IDs for Profile
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_conversation_for_profile
- Operation ID: `get_conversation_for_profile`
- Route: `GET /api/profiles/{id}/conversation`
- Mode: READ
- Summary: Get Conversation for Profile
- Parameters:
- `id` in `path` required
- `fields[conversation]` in `query`
- `revision` in `header` required
### get_conversation_id_for_profile
- Operation ID: `get_conversation_id_for_profile`
- Route: `GET /api/profiles/{id}/relationships/conversation`
- Mode: READ
- Summary: Get Conversation ID for Profile
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,84 @@
---
name: push-tokens-routes
description: Handle 6 OpenAPI operation(s) under /api/push-tokens for the push tokens route group.
---
# push tokens API Routes
Handle 6 OpenAPI operation(s) under /api/push-tokens for the push tokens 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_push_tokens
- Operation ID: `get_push_tokens`
- Route: `GET /api/push-tokens`
- Mode: READ
- Summary: Get Push Tokens
- Parameters:
- `fields[profile]` in `query`
- `fields[push-token]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### create_push_token
- Operation ID: `create_push_token`
- Route: `POST /api/push-tokens`
- Mode: WRITE
- Summary: Create or Update Push Token
- Parameters:
- `revision` in `header` required
- Body: JSON request body accepted.
### get_push_token
- Operation ID: `get_push_token`
- Route: `GET /api/push-tokens/{id}`
- Mode: READ
- Summary: Get Push Token
- Parameters:
- `id` in `path` required
- `fields[profile]` in `query`
- `fields[push-token]` in `query`
- `include` in `query`
- `revision` in `header` required
### delete_push_token
- Operation ID: `delete_push_token`
- Route: `DELETE /api/push-tokens/{id}`
- Mode: WRITE
- Summary: Delete Push Token
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_profile_for_push_token
- Operation ID: `get_profile_for_push_token`
- Route: `GET /api/push-tokens/{id}/profile`
- Mode: READ
- Summary: Get Profile for Push Token
- Parameters:
- `id` in `path` required
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `revision` in `header` required
### get_profile_id_for_push_token
- Operation ID: `get_profile_id_for_push_token`
- Route: `GET /api/push-tokens/{id}/relationships/profile`
- Mode: READ
- Summary: Get Profile ID for Push Token
- Parameters:
- `id` in `path` required
- `revision` in `header` required

55
skills/reviews/SKILL.md Normal file
View File

@@ -0,0 +1,55 @@
---
name: reviews-routes
description: Handle 3 OpenAPI operation(s) under /api/reviews for the reviews route group.
---
# reviews API Routes
Handle 3 OpenAPI operation(s) under /api/reviews for the reviews 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_reviews
- Operation ID: `get_reviews`
- Route: `GET /api/reviews`
- Mode: READ
- Summary: Get Reviews
- Parameters:
- `fields[event]` in `query`
- `fields[review]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_review
- Operation ID: `get_review`
- Route: `GET /api/reviews/{id}`
- Mode: READ
- Summary: Get Review
- Parameters:
- `id` in `path` required
- `fields[event]` in `query`
- `fields[review]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_review
- Operation ID: `update_review`
- Route: `PATCH /api/reviews/{id}`
- Mode: WRITE
- Summary: Update Review
- Parameters:
- `id` in `path` required
- `fields[review]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: segment-series-reports-routes
description: Handle 1 OpenAPI operation(s) under /api/segment-series-reports for the segment series reports route group.
---
# segment series reports API Routes
Handle 1 OpenAPI operation(s) under /api/segment-series-reports for the segment series 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
### query_segment_series
- Operation ID: `query_segment_series`
- Route: `POST /api/segment-series-reports`
- Mode: WRITE
- Summary: Query Segment Series
- Parameters:
- `fields[segment-series-report]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: segment-values-reports-routes
description: Handle 1 OpenAPI operation(s) under /api/segment-values-reports for the segment values reports route group.
---
# segment values reports API Routes
Handle 1 OpenAPI operation(s) under /api/segment-values-reports for the segment values 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
### query_segment_values
- Operation ID: `query_segment_values`
- Route: `POST /api/segment-values-reports`
- Mode: WRITE
- Summary: Query Segment Values
- Parameters:
- `fields[segment-values-report]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

151
skills/segments/SKILL.md Normal file
View File

@@ -0,0 +1,151 @@
---
name: segments-routes
description: Handle 11 OpenAPI operation(s) under /api/segments for the segments route group.
---
# segments API Routes
Handle 11 OpenAPI operation(s) under /api/segments for the 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_segments
- Operation ID: `get_segments`
- Route: `GET /api/segments`
- Mode: READ
- Summary: Get Segments
- Parameters:
- `fields[flow]` in `query`
- `fields[segment]` in `query`
- `fields[tag]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_segment
- Operation ID: `create_segment`
- Route: `POST /api/segments`
- Mode: WRITE
- Summary: Create Segment
- Parameters:
- `fields[segment]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_segment
- Operation ID: `get_segment`
- Route: `GET /api/segments/{id}`
- Mode: READ
- Summary: Get Segment
- Parameters:
- `id` in `path` required
- `additional-fields[segment]` in `query`
- `fields[flow]` in `query`
- `fields[segment]` in `query`
- `fields[tag]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_segment
- Operation ID: `update_segment`
- Route: `PATCH /api/segments/{id}`
- Mode: WRITE
- Summary: Update Segment
- Parameters:
- `id` in `path` required
- `fields[segment]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_segment
- Operation ID: `delete_segment`
- Route: `DELETE /api/segments/{id}`
- Mode: WRITE
- Summary: Delete Segment
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_tags_for_segment
- Operation ID: `get_tags_for_segment`
- Route: `GET /api/segments/{id}/tags`
- Mode: READ
- Summary: Get Tags for Segment
- Parameters:
- `id` in `path` required
- `fields[tag]` in `query`
- `revision` in `header` required
### get_tag_ids_for_segment
- Operation ID: `get_tag_ids_for_segment`
- Route: `GET /api/segments/{id}/relationships/tags`
- Mode: READ
- Summary: Get Tag IDs for Segment
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_profiles_for_segment
- Operation ID: `get_profiles_for_segment`
- Route: `GET /api/segments/{id}/profiles`
- Mode: READ
- Summary: Get Profiles for Segment
- Parameters:
- `id` in `path` required
- `additional-fields[profile]` in `query`
- `fields[profile]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_profile_ids_for_segment
- Operation ID: `get_profile_ids_for_segment`
- Route: `GET /api/segments/{id}/relationships/profiles`
- Mode: READ
- Summary: Get Profile IDs for Segment
- Parameters:
- `id` in `path` required
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### get_flows_triggered_by_segment
- Operation ID: `get_flows_triggered_by_segment`
- Route: `GET /api/segments/{id}/flow-triggers`
- Mode: READ
- Summary: Get Flows Triggered by Segment
- Parameters:
- `id` in `path` required
- `fields[flow]` in `query`
- `revision` in `header` required
### get_ids_for_flows_triggered_by_segment
- Operation ID: `get_ids_for_flows_triggered_by_segment`
- Route: `GET /api/segments/{id}/relationships/flow-triggers`
- Mode: READ
- Summary: Get IDs for Flows Triggered by Segment
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,92 @@
---
name: tag-groups-routes
description: Handle 7 OpenAPI operation(s) under /api/tag-groups for the tag groups route group.
---
# tag groups API Routes
Handle 7 OpenAPI operation(s) under /api/tag-groups for the tag 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_tag_groups
- Operation ID: `get_tag_groups`
- Route: `GET /api/tag-groups`
- Mode: READ
- Summary: Get Tag Groups
- Parameters:
- `fields[tag-group]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_tag_group
- Operation ID: `create_tag_group`
- Route: `POST /api/tag-groups`
- Mode: WRITE
- Summary: Create Tag Group
- Parameters:
- `fields[tag-group]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_tag_group
- Operation ID: `get_tag_group`
- Route: `GET /api/tag-groups/{id}`
- Mode: READ
- Summary: Get Tag Group
- Parameters:
- `id` in `path` required
- `fields[tag-group]` in `query`
- `revision` in `header` required
### update_tag_group
- Operation ID: `update_tag_group`
- Route: `PATCH /api/tag-groups/{id}`
- Mode: WRITE
- Summary: Update Tag Group
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_tag_group
- Operation ID: `delete_tag_group`
- Route: `DELETE /api/tag-groups/{id}`
- Mode: WRITE
- Summary: Delete Tag Group
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_tags_for_tag_group
- Operation ID: `get_tags_for_tag_group`
- Route: `GET /api/tag-groups/{id}/tags`
- Mode: READ
- Summary: Get Tags for Tag Group
- Parameters:
- `id` in `path` required
- `fields[tag]` in `query`
- `revision` in `header` required
### get_tag_ids_for_tag_group
- Operation ID: `get_tag_ids_for_tag_group`
- Route: `GET /api/tag-groups/{id}/relationships/tags`
- Mode: READ
- Summary: Get Tag IDs for Tag Group
- Parameters:
- `id` in `path` required
- `revision` in `header` required

224
skills/tags/SKILL.md Normal file
View File

@@ -0,0 +1,224 @@
---
name: tags-routes
description: Handle 19 OpenAPI operation(s) under /api/tags for the tags route group.
---
# tags API Routes
Handle 19 OpenAPI operation(s) under /api/tags for the tags 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_tags
- Operation ID: `get_tags`
- Route: `GET /api/tags`
- Mode: READ
- Summary: Get Tags
- Parameters:
- `fields[tag-group]` in `query`
- `fields[tag]` in `query`
- `filter` in `query`
- `include` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_tag
- Operation ID: `create_tag`
- Route: `POST /api/tags`
- Mode: WRITE
- Summary: Create Tag
- Parameters:
- `fields[tag]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_tag
- Operation ID: `get_tag`
- Route: `GET /api/tags/{id}`
- Mode: READ
- Summary: Get Tag
- Parameters:
- `id` in `path` required
- `fields[tag-group]` in `query`
- `fields[tag]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_tag
- Operation ID: `update_tag`
- Route: `PATCH /api/tags/{id}`
- Mode: WRITE
- Summary: Update Tag
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_tag
- Operation ID: `delete_tag`
- Route: `DELETE /api/tags/{id}`
- Mode: WRITE
- Summary: Delete Tag
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### get_flow_ids_for_tag
- Operation ID: `get_flow_ids_for_tag`
- Route: `GET /api/tags/{id}/relationships/flows`
- Mode: READ
- Summary: Get Flow IDs for Tag
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### tag_flows
- Operation ID: `tag_flows`
- Route: `POST /api/tags/{id}/relationships/flows`
- Mode: WRITE
- Summary: Tag Flows
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### remove_tag_from_flows
- Operation ID: `remove_tag_from_flows`
- Route: `DELETE /api/tags/{id}/relationships/flows`
- Mode: WRITE
- Summary: Remove Tag from Flows
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### get_campaign_ids_for_tag
- Operation ID: `get_campaign_ids_for_tag`
- Route: `GET /api/tags/{id}/relationships/campaigns`
- Mode: READ
- Summary: Get Campaign IDs for Tag
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### tag_campaigns
- Operation ID: `tag_campaigns`
- Route: `POST /api/tags/{id}/relationships/campaigns`
- Mode: WRITE
- Summary: Tag Campaigns
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### remove_tag_from_campaigns
- Operation ID: `remove_tag_from_campaigns`
- Route: `DELETE /api/tags/{id}/relationships/campaigns`
- Mode: WRITE
- Summary: Remove Tag from Campaigns
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### get_list_ids_for_tag
- Operation ID: `get_list_ids_for_tag`
- Route: `GET /api/tags/{id}/relationships/lists`
- Mode: READ
- Summary: Get List IDs for Tag
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### tag_lists
- Operation ID: `tag_lists`
- Route: `POST /api/tags/{id}/relationships/lists`
- Mode: WRITE
- Summary: Tag Lists
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### remove_tag_from_lists
- Operation ID: `remove_tag_from_lists`
- Route: `DELETE /api/tags/{id}/relationships/lists`
- Mode: WRITE
- Summary: Remove Tag from Lists
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### get_segment_ids_for_tag
- Operation ID: `get_segment_ids_for_tag`
- Route: `GET /api/tags/{id}/relationships/segments`
- Mode: READ
- Summary: Get Segment IDs for Tag
- Parameters:
- `id` in `path` required
- `revision` in `header` required
### tag_segments
- Operation ID: `tag_segments`
- Route: `POST /api/tags/{id}/relationships/segments`
- Mode: WRITE
- Summary: Tag Segments
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### remove_tag_from_segments
- Operation ID: `remove_tag_from_segments`
- Route: `DELETE /api/tags/{id}/relationships/segments`
- Mode: WRITE
- Summary: Remove Tag from Segments
- Parameters:
- `id` in `path` required
- `revision` in `header` required
- Body: JSON request body accepted.
### get_tag_group_for_tag
- Operation ID: `get_tag_group_for_tag`
- Route: `GET /api/tags/{id}/tag-group`
- Mode: READ
- Summary: Get Tag Group for Tag
- Parameters:
- `id` in `path` required
- `fields[tag-group]` in `query`
- `revision` in `header` required
### get_tag_group_id_for_tag
- Operation ID: `get_tag_group_id_for_tag`
- Route: `GET /api/tags/{id}/relationships/tag-group`
- Mode: READ
- Summary: Get Tag Group ID for Tag
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,25 @@
---
name: template-clone-routes
description: Handle 1 OpenAPI operation(s) under /api/template-clone for the template clone route group.
---
# template clone API Routes
Handle 1 OpenAPI operation(s) under /api/template-clone for the template clone 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
### clone_template
- Operation ID: `clone_template`
- Route: `POST /api/template-clone`
- Mode: WRITE
- Summary: Clone Template
- Parameters:
- `fields[template]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,25 @@
---
name: template-render-routes
description: Handle 1 OpenAPI operation(s) under /api/template-render for the template render route group.
---
# template render API Routes
Handle 1 OpenAPI operation(s) under /api/template-render for the template render 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
### render_template
- Operation ID: `render_template`
- Route: `POST /api/template-render`
- Mode: WRITE
- Summary: Render Template
- Parameters:
- `fields[template]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

View File

@@ -0,0 +1,72 @@
---
name: template-universal-content-routes
description: Handle 5 OpenAPI operation(s) under /api/template-universal-content for the template universal content route group.
---
# template universal content API Routes
Handle 5 OpenAPI operation(s) under /api/template-universal-content for the template universal content 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_all_universal_content
- Operation ID: `get_all_universal_content`
- Route: `GET /api/template-universal-content`
- Mode: READ
- Summary: Get All Universal Content
- Parameters:
- `fields[template-universal-content]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_universal_content
- Operation ID: `create_universal_content`
- Route: `POST /api/template-universal-content`
- Mode: WRITE
- Summary: Create Universal Content
- Parameters:
- `fields[template-universal-content]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_universal_content
- Operation ID: `get_universal_content`
- Route: `GET /api/template-universal-content/{id}`
- Mode: READ
- Summary: Get Universal Content
- Parameters:
- `id` in `path` required
- `fields[template-universal-content]` in `query`
- `revision` in `header` required
### update_universal_content
- Operation ID: `update_universal_content`
- Route: `PATCH /api/template-universal-content/{id}`
- Mode: WRITE
- Summary: Update Universal Content
- Parameters:
- `id` in `path` required
- `fields[template-universal-content]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_universal_content
- Operation ID: `delete_universal_content`
- Route: `DELETE /api/template-universal-content/{id}`
- Mode: WRITE
- Summary: Delete Universal Content
- Parameters:
- `id` in `path` required
- `revision` in `header` required

76
skills/templates/SKILL.md Normal file
View File

@@ -0,0 +1,76 @@
---
name: templates-routes
description: Handle 5 OpenAPI operation(s) under /api/templates for the templates route group.
---
# templates API Routes
Handle 5 OpenAPI operation(s) under /api/templates for the 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_templates
- Operation ID: `get_templates`
- Route: `GET /api/templates`
- Mode: READ
- Summary: Get Templates
- Parameters:
- `additional-fields[template]` in `query`
- `fields[template]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_template
- Operation ID: `create_template`
- Route: `POST /api/templates`
- Mode: WRITE
- Summary: Create Template
- Parameters:
- `additional-fields[template]` in `query`
- `fields[template]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_template
- Operation ID: `get_template`
- Route: `GET /api/templates/{id}`
- Mode: READ
- Summary: Get Template
- Parameters:
- `id` in `path` required
- `additional-fields[template]` in `query`
- `fields[template]` in `query`
- `revision` in `header` required
### update_template
- Operation ID: `update_template`
- Route: `PATCH /api/templates/{id}`
- Mode: WRITE
- Summary: Update Template
- Parameters:
- `id` in `path` required
- `additional-fields[template]` in `query`
- `fields[template]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_template
- Operation ID: `delete_template`
- Route: `DELETE /api/templates/{id}`
- Mode: WRITE
- Summary: Delete Template
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,49 @@
---
name: tracking-settings-routes
description: Handle 3 OpenAPI operation(s) under /api/tracking-settings for the tracking settings route group.
---
# tracking settings API Routes
Handle 3 OpenAPI operation(s) under /api/tracking-settings for the tracking settings 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_tracking_settings
- Operation ID: `get_tracking_settings`
- Route: `GET /api/tracking-settings`
- Mode: READ
- Summary: Get Tracking Settings
- Parameters:
- `fields[tracking-setting]` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `revision` in `header` required
### get_tracking_setting
- Operation ID: `get_tracking_setting`
- Route: `GET /api/tracking-settings/{id}`
- Mode: READ
- Summary: Get Tracking Setting
- Parameters:
- `id` in `path` required
- `fields[tracking-setting]` in `query`
- `revision` in `header` required
### update_tracking_setting
- Operation ID: `update_tracking_setting`
- Route: `PATCH /api/tracking-settings/{id}`
- Mode: WRITE
- Summary: Update Tracking Setting
- Parameters:
- `id` in `path` required
- `fields[tracking-setting]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.

72
skills/web-feeds/SKILL.md Normal file
View File

@@ -0,0 +1,72 @@
---
name: web-feeds-routes
description: Handle 5 OpenAPI operation(s) under /api/web-feeds for the web feeds route group.
---
# web feeds API Routes
Handle 5 OpenAPI operation(s) under /api/web-feeds for the web feeds 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_web_feeds
- Operation ID: `get_web_feeds`
- Route: `GET /api/web-feeds`
- Mode: READ
- Summary: Get Web Feeds
- Parameters:
- `fields[web-feed]` in `query`
- `filter` in `query`
- `page[cursor]` in `query`
- `page[size]` in `query`
- `sort` in `query`
- `revision` in `header` required
### create_web_feed
- Operation ID: `create_web_feed`
- Route: `POST /api/web-feeds`
- Mode: WRITE
- Summary: Create Web Feed
- Parameters:
- `fields[web-feed]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_web_feed
- Operation ID: `get_web_feed`
- Route: `GET /api/web-feeds/{id}`
- Mode: READ
- Summary: Get Web Feed
- Parameters:
- `id` in `path` required
- `fields[web-feed]` in `query`
- `revision` in `header` required
### update_web_feed
- Operation ID: `update_web_feed`
- Route: `PATCH /api/web-feeds/{id}`
- Mode: WRITE
- Summary: Update Web Feed
- Parameters:
- `id` in `path` required
- `fields[web-feed]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_web_feed
- Operation ID: `delete_web_feed`
- Route: `DELETE /api/web-feeds/{id}`
- Mode: WRITE
- Summary: Delete Web Feed
- Parameters:
- `id` in `path` required
- `revision` in `header` required

View File

@@ -0,0 +1,35 @@
---
name: webhook-topics-routes
description: Handle 2 OpenAPI operation(s) under /api/webhook-topics for the webhook topics route group.
---
# webhook topics API Routes
Handle 2 OpenAPI operation(s) under /api/webhook-topics for the webhook topics 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_webhook_topics
- Operation ID: `get_webhook_topics`
- Route: `GET /api/webhook-topics`
- Mode: READ
- Summary: Get Webhook Topics
- Parameters:
- `fields[webhook-topic]` in `query`
- `revision` in `header` required
### get_webhook_topic
- Operation ID: `get_webhook_topic`
- Route: `GET /api/webhook-topics/{id}`
- Mode: READ
- Summary: Get Webhook Topic
- Parameters:
- `id` in `path` required
- `fields[webhook-topic]` in `query`
- `revision` in `header` required

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

@@ -0,0 +1,72 @@
---
name: webhooks-routes
description: Handle 5 OpenAPI operation(s) under /api/webhooks for the webhooks route group.
---
# webhooks API Routes
Handle 5 OpenAPI operation(s) under /api/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 /api/webhooks`
- Mode: READ
- Summary: Get Webhooks
- Parameters:
- `fields[webhook-topic]` in `query`
- `fields[webhook]` in `query`
- `include` in `query`
- `revision` in `header` required
### create_webhook
- Operation ID: `create_webhook`
- Route: `POST /api/webhooks`
- Mode: WRITE
- Summary: Create Webhook
- Parameters:
- `fields[webhook]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### get_webhook
- Operation ID: `get_webhook`
- Route: `GET /api/webhooks/{id}`
- Mode: READ
- Summary: Get Webhook
- Parameters:
- `id` in `path` required
- `fields[webhook-topic]` in `query`
- `fields[webhook]` in `query`
- `include` in `query`
- `revision` in `header` required
### update_webhook
- Operation ID: `update_webhook`
- Route: `PATCH /api/webhooks/{id}`
- Mode: WRITE
- Summary: Update Webhook
- Parameters:
- `id` in `path` required
- `fields[webhook]` in `query`
- `revision` in `header` required
- Body: JSON request body accepted.
### delete_webhook
- Operation ID: `delete_webhook`
- Route: `DELETE /api/webhooks/{id}`
- Mode: WRITE
- Summary: Delete Webhook
- Parameters:
- `id` in `path` required
- `revision` in `header` required