Our legacy REST API provides comprehensive access to your uptime monitoring data through a straightforward HTTP interface. Whether you're building dashboards, automating workflows, or integrating monitoring into existing systems, this API delivers the flexibility you need.
The API supports multiple response formats including XML, JSON, and JSON-P, making it compatible with virtually any development environment. You can manage monitors, retrieve historical data, configure alert contacts, and control maintenance windows programmatically.
The legacy API exposes the following core functionality through POST endpoints:
PulseStack™ employs HTTP Basic Access Authentication to secure API access. Three distinct API key types provide granular access control:
Account-Level Keys: Provide complete access to all API methods across your entire monitoring setup. Ideal for administrative operations and bulk data management.
Monitor-Specific Keys: Restrict access to individual monitor data only. Perfect for client-facing applications where you need to expose specific monitoring information without revealing broader account access.
Read-Only Keys: Enable data retrieval without modification permissions. Recommended for reporting dashboards and analytics applications that don't require write operations.
All API keys are accessible through your account settings panel at pulsestack.co.uk.
To maintain optimal service quality, we implement tiered rate limiting based on your subscription level:
When rate limits are exceeded, the API returns a 429 status code alongside informative headers:
X-RateLimit-Limit: Your current rate limit thresholdX-RateLimit-Remaining: Available requests in current windowX-RateLimit-Reset: Epoch timestamp when limits resetRetry-After: Recommended retry delay in secondsThe API delivers data in your preferred format by specifying the format parameter:
For XML responses:https://api.pulsestack.co.uk/v2/methodName?format=xml
For JSON responses:https://api.pulsestack.co.uk/v2/methodName?format=json
JSON-P support is available by including a callback parameter, returning data wrapped in your specified function call.
Cross-Origin Resource Sharing (CORS) headers are automatically included for GET operations when using monitor-specific or read-only API keys, enabling seamless browser-based integrations.