Webhook ingestion
Developer-facing overview of Cybatar signed webhook ingestion, endpoint credentials, IP restrictions, request signatures, payload limits and ingestion records.
Read guideCybatar / Developers
Developer documentation
Integration guidance grounded in the current Cybatar implementation.
These guides document public-safe implementation facts for webhooks, API-key records, event-source onboarding, connector setup and connector-health evidence. They do not expose live credentials, private endpoint identifiers or an invented API contract.
API-key management
How Cybatar issues API-key records using one-way token hashes, previews, scopes, status and expiry metadata for deployment-specific integration access.
Read guideEvent-source onboarding
How to register security event sources in Cybatar, preserve source identity and health context, and connect configured data to SIEM and security-operations workflows.
Read guideConnector setup workflow
How Cybatar records connector setup steps and integration context for deployment-specific security integrations.
Read guideIntegration health and evidence
How Cybatar represents connector health and why deployment teams should distinguish registry state from active probing or real telemetry evidence.
Read guideNeed source-specific context?
The connector library documents Microsoft 365, Google Workspace, Wazuh, firewall, endpoint, cloud, webhook and custom-source patterns.
Explore connectorsPublic documentation boundary
Connector availability depends on deployment configuration, credentials, source APIs, data formats and enabled modules. Public connector pages do not claim vendor certification, marketplace approval, complete field coverage, real-time delivery guarantees, universal API support or a successful connection to a third-party service unless that is verified in the specific deployment.