canonical: https://jentic.com/apis/swaggerhub.netreo/swaggerhub-netreo # Netreo Incident Acknowledgment API Remotely acknowledge or unacknowledge an active incident. The API exposes 2 endpoints. ## For AI agents Programmatically acknowledge an incident in netreo, acknowledge an incident in netreo. Covers 2 operations. ## Scope Does not handle payments, communications, or crm - use for security only. ## Capabilities - Acknowledge an incident in Netreo - Manage security data programmatically - Integrate Incident Acknowledgment API into automated workflows - Query and filter Incident Acknowledgment API records by parameters - Monitor Incident Acknowledgment API operational status and events ## Use cases ### Security Operations Use the Incident Acknowledgment API to perform security operations programmatically. The API provides 2 endpoints covering core functionality including acknowledge an incident in netreo, acknowledge an incident in netreo. Example prompt: Call POST `/incident/acknowledge` to acknowledge an incident in netreo ### Data Retrieval and Monitoring Query Incident Acknowledgment API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed. Example prompt: Poll the primary Incident Acknowledgment API endpoint, compare response to last known state, and alert if changed ### AI Agent Integration via Jentic AI agents discover and call Incident Acknowledgment API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually. Example prompt: Search Jentic for 'acknowledge an incident in netreo', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/incident/acknowledge` | Acknowledge an incident in Netreo | | POST | `/incident/unacknowledge` | Acknowledge an incident in Netreo | ## Key resources - **developers** — Operations related to developers ## Why Jentic - **Setup:** Wiring the Incident Acknowledgment API by hand means resolving your Netreo server address and posting acknowledgement calls against it yourself. Through Jentic you install once, import the Incident Acknowledgment API from the API Directory, store any connection detail once, and your agent calls it. - **Permission scoping:** This API carries the incident target in the request body rather than the URL path, so scope your agent by the operations it needs: for example let it acknowledge incidents while leaving unacknowledge out of the allowed set. You choose which operations it may call, so it only runs the ones you list. - **Credential handling:** Any Incident Acknowledgment API connection detail is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'acknowledge an incident in Netreo' or 'clear an incident acknowledgement', and Jentic returns the matching Incident Acknowledgment API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Snyk** — Alternative security API - **Crowdstrike** — Alternative security API ## FAQ ### What authentication does the Incident Acknowledgment API use? The Incident Acknowledgment API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I acknowledge an incident in netreo with the Incident Acknowledgment API? Yes. Use the POST `/incident/acknowledge` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Incident Acknowledgment API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I acknowledge an incident in netreo through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'acknowledge an incident in netreo'. Jentic returns the matching Incident Acknowledgment API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Incident Acknowledgment API have? The Incident Acknowledgment API exposes 2 endpoints covering developers operations. ### Can I limit what my agent is allowed to do with the Incident Acknowledgment API? Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, and this API has just two: POST `/incident/acknowledge` and POST `/incident/unacknowledge.` You can allow the agent to acknowledge incidents while leaving unacknowledge out of the permitted set, so it only runs the operations you list. Since the incident target travels in the request body rather than the URL, scoping by operation is how you control what the agent can do.