SIGNL4 API
messaging · signl4.com
Watched for drift — classified from the API's own spec; not yet a gate-proven pack.
<p>Use our API for systems integration or to build your own use cases. Sample scenarios include but are not limited to:</p><ul><li>2-way integration: Triggering of Signls and updates in the third party systems when alert state changes occur</li><li>Retrieving alarms for logging purposes</li><li>Calendar integrations: Creation and management of on-call duties</li><li>Punch users in and out based on external calendars</li><li>etc.</li></ul><p>AUTHENTICATION<br>Using the API requires an API key, which you can generate in the SIGNL4 portal under 'Developers'.<br>This key must then be specified in a special header in every HTTP request.<br>This header is called <b style='color:#F8B41F'>X-S4-Api-Key</b>.<br><br>The base URL of the API is <a rel='noopener noreferrer' target='_blank' href='https://connect.signl4.com/api/'>https://connect.signl4.com/api/</a>.<br>Copyright © Derdack GmbH<br></p>
Install
watched · not yet packagednpx verifyport add signl4-com --lang python npx verifyport add signl4-com --lang go npx verifyport add signl4-com --lang node Agent trust (law 4)
the agent verdict →A tool has degraded — pin to a known-good version.
Behavioral replay
No live replays yet — this connector is spec-monitored. Behavioral proof arrives with credentialed, read-only replay.
Drift timeline
No drift recorded yet — the spec has held its shape.
Spec history
- 11h ago 101 tools CLEAN:86 BAD_SPEC:8 HANDLEABLE_VARIANT:7 residual 15%