External REST API

A token-authenticated REST API for integrating Cronix PRO with external systems. Manage your cron schedule from CI/CD pipelines, monitoring dashboards, deployment scripts, or any tool that can make an HTTP request.

Enable under Addons > External REST API.

#Setup

1. Enable the addon under Addons > External REST API

2. Click Generate Token to create a new API token

3. Copy the token - it is only shown once

4. Use the token in the Authorization: Bearer <token> header on all requests

#Authentication

All external API requests must include a Bearer token in the Authorization header. Standard WordPress cookie or nonce authentication is not accepted for external API requests.

Tokens can be scoped to read-only or read-write access. Create separate tokens for monitoring systems (read-only) and deployment scripts (read-write).

#Token Management

• Create - generate a new named token with a defined scope

• Revoke - immediately invalidate a specific token

• Last used - see when and from which IP address each token was last used

#Available Endpoints

The External REST API exposes all core Cronix PRO operations:

Method	Endpoint	Description
GET	/events	List all events
POST	/events/{hook}/run	Run an event immediately
POST	/events/{hook}/pause	Pause an event
POST	/events/{hook}/resume	Resume an event
GET	/health/score	Get the current health score
GET	/log	Query the execution log

See the REST API Reference article for the complete endpoint list with all parameters.

#Use Cases

Deployment scripts - pause non-critical events before deploying, then resume after:

Send a POST to /events/{hook}/pause before your migration runs, then POST to /events/{hook}/resume when the deploy is complete.

Health monitoring - poll the health score from an uptime service:

Send a GET to /health/score on an interval and alert your team if the score drops below a threshold.

Last updated 5 Apr 2026