From ef2aca507fa44897d939661d55665d79570e3293 Mon Sep 17 00:00:00 2001 From: OpenClaw Agent Date: Tue, 7 Apr 2026 21:20:39 +0000 Subject: [PATCH] Add Grand Portage note type IDs (0-4) based on testing --- SKILL.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/SKILL.md b/SKILL.md index ba51e92..58f284d 100644 --- a/SKILL.md +++ b/SKILL.md @@ -166,6 +166,18 @@ Use `bms templates tickets list` to see available template IDs before creating. - **Note TypeId**: Required when posting notes. The public BMS v2 Swagger does not clearly expose a generic note-type lookup endpoint for all tenants, so you may need tenant-specific documentation or known values. - **Rate limits**: Not documented in the Swagger spec. Treat as standard REST API — avoid tight loops; add a small sleep between bulk operations. +## Note Type IDs (Grand Portage Tenant) + +Based on testing for Grand Portage, the following note type IDs are valid: + +- `0` — Email Sent +- `1` — Email Received +- `2` — General Notes +- `3` — Phone Call +- `4` — Resolution + +Note: These are tenant-specific and may differ in other BMS deployments. The public Swagger does not fully expose note type lookups. + ## References - [BMS API Swagger UI](https://api.bms.kaseya.com/swagger/index.html)