Reference

Plan limits

Hard caps (any plan)

These caps are enforced on every request regardless of plan — defense-in-depth against buggy or hostile clients.

HTTP error codes

Quota headers

Non-empty ingest responses include the headers below so SDKs and operators can self-throttle (an empty batch returns a bare 204 without them).

To shed load before you hit the hourly quota, the Python SDK samples client-side: monitor.init(sample_rate=…, success_sample_rate=…) — keep-probabilities for error vs success/track events (default 1.0 = keep everything). A high-throughput backend can drop the noisy success events while keeping every error.

Status thresholds (Feature Health)

Source: backend/app/routes/monitor_mgmt.py. Thresholds are per-feature and configurable via the alert rule — the values below use the default of 0.10.

HTTP ping monitors use a different rule (same file): status is taken from the most recent ping and is only ever no_data, degraded, or ok — there is no down state. It reads degraded when the last ping failed or the error rate over the last 200 checks is ≥ 0.10.

Closed-list field values

Both platform and source are closed lists. Values outside the list are silently coerced to a sentinel — this prevents a malicious or buggy client from inflating another platform's counters in dashboards or billing.

Wire format

The single ingestion endpoint. The SDK's apiUrl is your Onelo API root.

POST {apiUrl}/api/sdk/monitor/events/batch
Content-Type: application/json

{
  "publishableKey": "onelo_pk_live_…",
  "events": [
    {
      "featureName": "checkout.charge",
      "ok": false,
      "durationMs": 1342,
      "error": "Stripe declined: insufficient_funds",
      "meta": { "amount": 1999 },
      "source": "track",
      "userId": "usr_abc",
      "platform": "swift",
      "sessionId": "sess_2026_05_10_42"
    }
  ]
}

The publishableKey field carries your app key. Client SDKs send the publishable key (onelo_pk_live_*); the backend SDKs (Python, Node.js, PHP) send their server secret key (onelo_sk_live_*) in this same field. The endpoint accepts either.

Two behaviours worth knowing: an optional client-supplied event timestamp is display-only and ignored when it is older than 1 hour or more than 60 seconds in the future (the row falls back to server receive time — quotas, windows and incidents always key on server time). And key lookups are cached for up to 60 seconds, so a revoked key can keep authenticating for up to a minute after revocation.

REST API (dashboard read)

All endpoints below require Authorization: Bearer <session_token> (the dashboard JWT). They are not part of the public SDK contract.