Agent Skills
› netalertx/NetAlertX
› api-development
api-development
GitHub指导开发NetAlertX Flask REST API，涵盖入口点、现有路由、Bearer令牌认证及统一响应格式规范，用于创建或修改API端点。
Trigger Scenarios
创建新API端点
添加API路由
实现API功能
修改API响应
Install
npx skills add netalertx/NetAlertX --skill api-development -g -y
SKILL.md
Frontmatter
{
"name": "api-development",
"description": "Develop and extend NetAlertX REST API endpoints. Use this when asked to create endpoint, add API route, implement API, or modify API responses."
}
API Development
Entry Point
Flask app: server/api_server/api_server_start.py
Existing Routes
/device/<mac>- Single device operations/devices- Device list/devices/export/{csv,json}- Export devices/devices/import- Import devices/devices/totals- Device counts/devices/by-status- Devices grouped by status/nettools- Network utilities/events- Event log/sessions- Session management/dbquery- Database queries/metrics- Prometheus metrics/sync- Synchronization
Authorization
All routes require header:
Authorization: Bearer <API_TOKEN>
Retrieve token via get_setting_value('API_TOKEN').
Response Contract
MANDATORY: All responses must include "success": true|false
return {"success": False, "error": "Description of what went wrong"}
On success:
return {"success": True, "data": result}
return {"success": False, "error": "Description of what went wrong"}
On success:
return {"success": True, "data": result}
Exception: The legacy /device/<mac> GET endpoint does not follow this contract to maintain backward compatibility with the UI.
Adding New Endpoints
- Add route in
server/api_server/directory - Follow authorization pattern
- Return proper response contract
- Update UI to read/write JSON cache (don't bypass pipeline)
Version History
- 8aec57b Current 2026-07-24 22:14
