Sign in

API reference

Issues (read and status)

Endpoint GET /api/v1/issues, GET /api/v1/issues/:id, POST /api/v1/issues/:id/status

These endpoints back the Odoo module's issue list. They need the secret key and the X-Blipit-Instance header of the bound database, so from other tools use the MCP server, which needs only the key.

1List

GET /api/v1/issues?status=unresolved&limit=100&offset=0&order=last_seen. status is unresolved, resolved or ignored; limit 1 to 500 (default 100); order is last_seen or id.

sh
curl "https://in.blipit.io/api/v1/issues?status=unresolved&limit=50" \
  -H "X-Blipit-Key: <secret key>" -H "X-Blipit-Instance: <instance id>"

2Response

200 {issues, total, limit, offset, order}. Each issue: id, title, exception_type, level, status, first_seen, last_seen, event_count, last_release, regression_count, resolved_count, last_regressed_at, last_regression_kind (same_release or new_release), companies (company tags seen, up to 64).

3One issue and status

GET /api/v1/issues/<id> returns the issue with its latest event's payload. POST /api/v1/issues/<id>/status with {status} sets unresolved, resolved or ignored and answers {ok: true, status}.

sh
curl -X POST https://in.blipit.io/api/v1/issues/981/status \
  -H "Content-Type: application/json" -H "X-Blipit-Key: <secret key>" -H "X-Blipit-Instance: <instance id>" \
  -d '{"status":"resolved"}'

Good to know

  • 401 unknown key, 403 public key or wrong instance, 404 an issue that is not in this project, 400 an unknown status.
  • Resolving through the API behaves like the dashboard: the next event reopens the issue as a regression.

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