Ssf
Overview
Application Security (Pre-Release)
Assets
Chat
Cloud Security (In Development)
Endpoint Detection & Response (EDR)
Email Security
Endpoint Management
Governance, Risk, & Compliance (GRC) (In Development)
Hooks
Identity
Incident Response (In Development)
Integration Webhooks
Network Security (In Development)
Notifications
Operations (In Development)
Security Awareness (In Development)
Security Information & Event Management (SIEM)
Sink
Storage
Threat Intelligence (In Development)
Ticketing
Vulnerabilities
Signs a security signal as a Security Event Token and delivers it to the receiver configured with the token used for authentication. A success response means the receiver accepted the token. It does not mean the receiver acted on it.
Operation ID: ssf_post_event
Security
BearerAuth
Add metadata to the response by invoking meta functions. Documentation for meta functions is available. Not all meta functions are available at every endpoint.
The security signal. Supply the subject as a top-level sub_id and the event under events, keyed by event type URI. If you declare a mapping on this operation, post your own format instead: the mapping runs first, and its output is what must be a valid Security Event Token.
any
- Synqlyhttps://api.synqly.com/v1/ssf/events
curl -i -X POST \
https://api.synqly.com/v1/ssf/events \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json'Response
{ "result": { "event_id": "string" }, "messages": { "problems": [ … ] }, "meta": { "stats": { … }, "api": { … }, "mapping": { … } } }