SoCMate provides notification events and API endpoints that enable integration with SOAR platforms (Palo Alto XSOAR, Splunk SOAR, Microsoft Sentinel Playbooks), ticketing systems, and custom automation workflows.

Integration Architecture

Event Types

SoCMate generates notification events for the following actions:

SOAR Integration Pattern

The recommended integration pattern uses SoCMate’s API for pull-based integration:
1

Set up polling or event triggers

Configure your SOAR platform to periodically poll SoCMate for new incidents or investigation results, or use SoCMate’s notification system to receive events.
2

Create an API key

Create a SoCMate API key with appropriate scopes for your integration:
3

Poll for incidents

Your SOAR platform polls SoCMate for new high-severity incidents:
4

Trigger investigations

When your SOAR playbook identifies an incident that needs investigation, trigger a SoCMate investigation:
5

Retrieve results

Poll for investigation completion and retrieve the report:

Notification Payload Format

Events delivered through SoCMate’s notification system follow this structure:

Incident Alert

Investigation Completed

Investigation Failed

Example: XSOAR Playbook

A typical XSOAR integration flow:

Example: Sentinel Playbook (Logic App)

SoCMate can be called from a Microsoft Sentinel Playbook (Azure Logic App) when an incident is created:

API Endpoints for Integration

Best Practices

  • Use dedicated API keys — Create a separate API key for each integration with minimum required scopes
  • Handle rate limits — Implement retry logic with exponential backoff for 429 responses
  • Poll efficiently — Use time-based filters (timespan) to avoid re-processing old data
  • Check investigation status — Investigations take 30-120 seconds; poll the session endpoint rather than blocking
  • Log API key usage — Monitor last_used_at in the admin panel to track integration activity