canonical: https://jentic.com/apis/sophos.com/sophos

# Sophos SIEM Integration API

Retrieves alerts and events from Sophos Central for SIEM integration. The API exposes 2 endpoints secured with bearer authentication.

## For AI agents

Programmatically get alerts, get events. Covers 2 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get alerts
- Manage developer tools data programmatically
- Integrate Sophos SIEM Integration API into automated workflows
- Query and filter Sophos SIEM Integration API records by parameters
- Monitor Sophos SIEM Integration API operational status and events

## Use cases

### Developer Tools Operations

Use the Sophos SIEM Integration API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including get alerts, get events.

Example prompt: Call GET /alerts to get alerts

### Data Retrieval and Monitoring

Query Sophos SIEM Integration 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 Sophos SIEM Integration API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Sophos SIEM Integration 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 bearer tokens manually.

Example prompt: Search Jentic for 'get alerts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /alerts | Get alerts |
| GET | /events | Get events |

## Key resources

- **Alerts** — Operations related to Alerts
- **Events** — Operations related to Events

## Why Jentic

- **Setup:** Wiring the Sophos SIEM Integration API by hand means setting up its bearer auth and substituting your data region into the api-{dataRegion}.central.sophos.com host before you can pull alerts or events, then handling paging and retries yourself. Through Jentic you install once, import the Sophos SIEM Integration API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Sophos SIEM Integration API reads alerts and events through query parameters rather than resource ids in the URL path, so scope the agent to the operations it needs, such as fetching alerts or fetching events. You choose which operations are in the allowed set, so anything you do not add stays out of reach.
- **Credential handling:** Your Sophos token 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 'get security alerts' or 'get SIEM events', and Jentic returns the matching Sophos SIEM Integration API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Sophos SIEM Integration API use?

The Sophos SIEM Integration API uses a Bearer token in the Authorization header. 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 get alerts with the Sophos SIEM Integration API?

Yes. Use the GET /alerts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Sophos SIEM Integration 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 get alerts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get alerts'. Jentic returns the matching Sophos SIEM Integration API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Sophos SIEM Integration API have?

The Sophos SIEM Integration API exposes 2 endpoints covering alerts, events operations.

### Can I limit what my agent is allowed to do with the Sophos SIEM Integration API?

Yes. Because you run Jentic One yourself, you decide which of the Sophos SIEM Integration API operations your agent may call, so you can add fetching alerts (GET /alerts) or fetching events (GET /events) to the allowed set and leave the other out of reach. This API reads through query parameters rather than resource IDs in the URL path, so scoping is by operation, and any operation you do not add stays unavailable. Your Sophos bearer token is stored encrypted by your own instance and injected only at execution time, so the agent never sees the raw secret.