Added 'created_at__gt', 'created_at__lt' params to get_alerts()

Author: phate999

docs/known-issues.md

@@ -527,3 +527,12 @@ The v2 `/groups/` endpoint DOES support `expand=account`. When used, the
 for a separate `/accounts/` fetch to resolve group account names. Known
 endpoints that support `expand`: `/routers/` (group, account), `/groups/`
 (account).
+
+### v2 `/alerts/` Endpoint Does Not Support `order_by` (discovered 2026-06-26)
+The `/alerts/` endpoint returns `409 Conflict` with `"Invalid ordering field
+specified: created_at"` when using `order_by=-created_at` or any `order_by`
+parameter. The endpoint does not support ordering — results must be sorted
+client-side. The endpoint does support `created_at__gt` for time filtering,
+but requires full ISO 8601 format with microseconds and timezone offset
+(e.g. `2026-06-26T15:00:37.703000+00:00`). The alert `type` field for
+custom alerts is `custom_alert` (not `custom`).

ncm/ncm/ncm.py

@@ -514,7 +514,8 @@ def get_alerts(self, **kwargs):
         call_type = 'Alerts'
         get_url = '{0}/alerts/'.format(self.base_url)
 
-        allowed_params = ['account', 'created_at', 'created_at_timeuuid',
+        allowed_params = ['account', 'created_at', 'created_at__gt',
+                          'created_at__lt', 'created_at_timeuuid',
                           'detected_at', 'friendly_info', 'info',
                           'router', 'type', 'order_by', 'limit', 'offset']
         params = self.__parse_kwargs(kwargs, allowed_params)