Skip to content
API

Status

Is the Manage²Hero API working right now? This page shows the state of the API and of webhook delivery, availability over the last 30 and 90 days, and recent incidents. It needs no sign-in and contains no information about individual customers.

No current measurement data

The latest measurement is too old to prove the current state.

As of: 2026-11-07 10:04 UTC

Components

  • API

    Reachability of the API and token validation (api.manage2hero.com/v1)

    Measurement: No current measurement
    Availability 30 days
    after 24 hours of measurement
    Availability 90 days
    after 24 hours of measurement
    Last 90 days

    Last 90 days: 0 days without impairment, 0 degraded, 0 with an outage, 90 without measurement.

    90 days agotoday

  • Webhook delivery

    Sending of due webhook messages to the customers’ endpoints

    Measurement: No current measurement
    Availability 30 days
    after 24 hours of measurement
    Availability 90 days
    after 24 hours of measurement
    Last 90 days

    Last 90 days: 0 days without impairment, 0 degraded, 0 with an outage, 90 without measurement.

    90 days agotoday

  • Reconciliation and background jobs

    Re-queuing of events that could not be queued, retention and resuming of paused deliveries

    Measurement: No current measurement
    Availability 30 days
    after 24 hours of measurement
    Availability 90 days
    after 24 hours of measurement
    Last 90 days

    Last 90 days: 0 days without impairment, 0 degraded, 0 with an outage, 90 without measurement.

    90 days agotoday

Key figures

Delivery delay
no measurement
How long due webhook messages wait at most until their first attempt begins – as a value experienced by at least three customers. “No delay” means: no delay that affects several customers.
Typical delivery latency (last hour)
not enough data
Wait between becoming due and the first delivery attempt (median across customers). The recipient’s response time is not included. Shown only with at least five customers with deliveries.
Average API response time (24 hours)
not enough data
Average of the sign-in and reachability checks, two per minute.

Incidents

An incident is detected automatically when a component is not healthy for five minutes in a row, or reported by our operations team.

There were no incidents in the last 90 days.

How we measure

  • Two checks per minute: a request to api.manage2hero.com with an invalid test token must be answered with 401 “invalid_token”. This checks reachability, routing, rate limiting and token validation – not every single endpoint.
  • Webhook delivery and reconciliation are derived from the background jobs running and from the backlog of due messages. Paused webhooks and disabled endpoints of customers do not count as a platform disruption.
  • A minute counts as available when the check succeeded. “Degraded” (for example slow) counts as available and colours the day yellow. A minute without a measurement after measurement began and planned restarts during updates count as unavailable.
  • Availability applies only to the period that was actually measured, which we state below the figure (“measured since …: X of 90 days”). The time before measurement began is no basis: it counts neither as available nor as unavailable and does not make the figure look better. A figure appears only after 24 hours of measurement; as long as the whole window is not measured, it is correspondingly less meaningful.
  • The measurement runs in the same service it checks. If the entire service goes down, this page is unavailable too; minutes without a measurement count as unavailable afterwards. Problems on the way of individual customers (such as their own network) are not captured.
  • Reports from our operations team are shown separately from the measurement. The overall status shows the worse of the two; a report does not change the measured values or the availability.
  • All times and days are in UTC. Figures appear only when several customers are affected or enough data exists – so nothing can be inferred about individual customers.

Further reading