Login attempts

Install one call where you check passwords

Report every sign-in attempt from the server that checks the password. Blipit groups them by actor and address and raises a security issue when a burst crosses the threshold you set under Alerts. Never send the password. Odoo does this for you once the module is installed.

Paste it into Claude Code, Cursor or any AI coding assistant. It carries the steps and the code. In app.blipit.io, API keys, the same prompt comes with your key filled in.

1The call

http
POST https://in.blipit.io/api/v1/events
Content-Type: application/json
X-Blipit-Key: <secret key>

{
  "event_id": "9f1c4b6d8e2a47f0b3c5d7e9a1b2c3d4",
  "timestamp": "2026-09-28T09:15:00.000Z",
  "platform": "other",
  "level": "warning",
  "environment": "production",
  "message": "Failed login for admin",
  "sdk": { "name": "myapp-auth", "version": "1.0.0" },
  "security": {
    "kind": "login_failed",
    "actor": "admin",
    "actor_id": "42",
    "ip": "203.0.113.42",
    "user_agent": "Mozilla/5.0",
    "outcome": "bad_password"
  }
}

Good to know

  • kind is login_failed, login_succeeded, login_blocked, password_reset_requested or privilege_granted.
  • event_id is a fresh 32-character lowercase hex string per attempt; sending the same one twice counts once.
  • The Python, PHP, Ruby, Go, Java and .NET SDKs send the same security object with capture_security (captureSecurity or CaptureSecurity); init them with the secret key. Browser and mobile apps hold only the public key, so report logins from your server.
  • From SDK 0.1.1 (Node, Python, PHP, Ruby, Go, Java, .NET), an SDK started with the public key sends no login attempts and logs one warning saying the secret key is needed.

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