Quick Start with StatusPulse
Uptime monitoring without compromise
Get your first monitor running in under 3 minutes. This guide walks you through account creation, adding your primary endpoint, and configuring instant email alerts.
Create Free Account View API DocsCreate Your Workspace
Register using your corporate email to enable SSO and team collaboration from day one.
Verify Email Address
Check your inbox for the confirmation link from auth@statuspulse.io. Click it within 24 hours to activate your account and unlock dashboard access.
Name Your Workspace
Assign a clear identifier like Acme-Prod-Cluster or SaaS-Platform-EU. This workspace groups all monitors, alerts, and team members under a single billing scope.
Generate API Key
Navigate to Settings > Integration Keys and create your primary token. Store it in your vault; it authenticates webhook payloads and CLI commands.
Add Your Primary Endpoint
Configure your first HTTP check to track availability, response codes, and latency.
Endpoint Configuration
Go to Monitors > New Check and enter your production URL (e.g., https://api.yourdomain.com/v1/health). Set the check interval to 60s and enable TLS certificate tracking.
Global Probe Network
StatusPulse automatically routes requests through 12 regional nodes including Ashburn, Frankfurt, Tokyo, and Sydney. This eliminates single-region false positives.
Response Validation
Define success criteria: expect HTTP 200, a JSON body containing "status":"ok", and a response time under 800ms. Save the configuration to begin live polling.
Configure Email Notifications
Ensure your engineering team gets instant alerts when downtime occurs.
Channel Setup
Open Alerts > Channels > Add Email and input your on-call distribution list (e.g., ops-team@yourdomain.com). Verify the channel with the confirmation token sent to your inbox.
Threshold Rules
Set the trigger threshold to 1 consecutive failure for critical endpoints. Enable auto-recovery notifications so your team knows exactly when service is restored.
Quiet Hours & Testing
Configure quiet hours between 02:00–06:00 UTC to prevent overnight paging fatigue. Run a dry test using the Send Test Alert button to validate routing and formatting.