Events

Endpoint POST /api/v1/events

The event endpoint takes one JSON event in Blipit's schema v1 and queues it. It is what every Blipit SDK and the Odoo module call.

1Request

Key in X-Blipit-Key (public or secret) or ?key=. Odoo also sends X-Blipit-Instance. Body up to 256 KB, nested at most 32 levels. Required: event_id (32 lowercase hex), timestamp (ISO 8601), platform, sdk {name, version}, and a message or an exception. Optional: level, release, environment, user {id, email, username}, tags, breadcrumbs, request {method, url, headers}, contexts, fingerprint (array of strings that replaces the computed grouping), security (secret key only).

sh
curl https://in.blipit.io/api/v1/events \
  -H "Content-Type: application/json" -H "X-Blipit-Key: <public key>" \
  -d '{
    "event_id": "0123456789abcdef0123456789abcdef",
    "timestamp": "2026-09-28T09:15:00Z",
    "platform": "python",
    "level": "error",
    "release": "shop@1.4.2",
    "environment": "production",
    "exception": {
      "type": "KeyError",
      "value": "customer_id",
      "stacktrace": { "frames": [{ "filename": "shop/cart.py", "function": "checkout", "lineno": 42, "in_app": true }] }
    },
    "tags": { "company_id": "1" },
    "sdk": { "name": "my-sdk", "version": "1.0.0" }
  }'

2Responses

202 {id} accepted. 202 {accepted: false, sampled: true, plan} over the monthly cap and sampled out: the event was counted, not stored. 202 {accepted: false, dropped: true, plan} past the overage ceiling (the cap on Free, twice the cap on paid plans): nothing is kept until next month. 400 schema error with detail, or nesting too deep. 401 unknown key. 403 key bound to another instance, security event with a public key (security_needs_secret_key), or security monitoring not in the plan. 429 rate limited.

Good to know

  • 300 requests a minute per key, shared with spans and logs.
  • Sending the same event_id twice stores it once.
  • The public key cannot set tags.db; it is dropped so the Odoo copy-detection baseline cannot be poisoned.
  • 409 when the data comes from a different platform than the project's, for example {"error": "This project is for iOS. Create a separate Android project in Blipit and use its key.", "reason": "platform_mismatch", "project_platform": "ios", "sent_platform": "android"}. Events, sessions, logs, OTLP traces and metrics, bug reports, replays and web vitals all answer this way. Refused data is not stored and does not count against the quota. The Blipit SDKs log this error once and stop sending for the rest of the run. To fix it, create a project for that platform and use its key.

Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.