Skip to main content
Once a project is published, you can generate API monitoring for it: superun calls the endpoints you select on a fixed schedule and confirms the live service still responds, so you don’t learn an endpoint is down from user reports.
Monitoring applies to published projects only. Demo versions and unpublished projects do not offer API monitoring.

​
Generate monitoring

  1. In your project, go to Operations and open API monitoring.
  2. superun scans the live version and lists the endpoints that are safe to probe.
  3. Pick a probe frequency: 10 minutes / hourly / daily.
  4. Start monitoring. Probe results for each endpoint appear in the same place.
A higher frequency surfaces problems sooner, but every probe is a real call. Hourly or daily is enough for routine checks; save 10 minutes for critical endpoints.

​
Endpoints that are excluded

So the probe itself cannot affect live data, these endpoints are filtered out automatically and never appear in the selectable list:
  • Endpoints that may modify data, such as create, update, or delete operations.
  • Endpoints with side effects, such as sending mail, charging, or notifying external services.
  • Endpoints that require real business parameters, where no safe probe request can be constructed.
If an endpoint you care about is excluded, it is not suitable for unattended repeated calls. Verify those in a test backend instead — see Test environment.

​
After you publish a new version

Republishing changes the live endpoints, so an existing monitoring setup may no longer match. After publishing a new version, return to API monitoring and regenerate the configuration so monitoring covers the current live version.

Publish

Learn how to publish a project and how Build and Demo versions differ.