Skip to content
Communication/messaging

signl4.com

SIGNL4 sandbox and mock API

<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 Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
101
Collections
-
Event types
-
Start this simulation
example request
curl https://your-signl4.slurry.io/api/alerts/report \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version v1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 101.

  • POST/alerts
  • POST/alerts/acknowledgeAll
  • POST/alerts/acknowledgeMultiple
  • POST/alerts/closeAll
  • POST/alerts/closeMultiple
  • POST/alerts/paged
  • GET/alerts/report
  • POST/alerts/undoAcknowledgeMultiple
  • POST/alerts/undoCloseMultiple
  • GET/alerts/{alertId}
  • POST/alerts/{alertId}/acknowledge
  • POST/alerts/{alertId}/annotate
SIGNL4 sandbox and mock API | Slurry