thelab/openclaw-bms
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Grand Portage note type IDs (0-4) based on testing

Browse Source
This commit is contained in:
OpenClaw Agent
2026-04-07 21:20:39 +00:00
parent 635dbf7344
commit ef2aca507f
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
SKILL.md
View File

@@ -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. - **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. - **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 ## References
- [BMS API Swagger UI](https://api.bms.kaseya.com/swagger/index.html) - [BMS API Swagger UI](https://api.bms.kaseya.com/swagger/index.html)