API Overview¶
API Guide
The NOB.center REST API gives you programmatic access to every monitoring module — the same API the web application uses. You can use it to automate configuration, integrate monitoring data into your own tooling, or build custom alerting pipelines.
Base URL¶
https://app.nob.center/api
All endpoints return JSON. Request bodies, where required, are also JSON (Content-Type: application/json).
Interactive reference¶
The full API reference is available as an interactive Swagger UI at:
You must be logged in to access the Swagger UI. Once authenticated, you can explore every endpoint, inspect request/response schemas, and try calls directly in the browser.
How the API is organized¶
| Path prefix | Module |
|---|---|
/api/ct-log/ |
Certificate Transparency monitoring |
/api/dns-watcher/ |
DNS monitoring |
/api/rdap/ |
RDAP / WHOIS monitoring |
/api/cert-watcher/ |
Certificate deployment monitoring |
/api/admin/ |
User and permission management |
/api/api-tokens/ |
API token management |
/api/reports/ |
Security reports |
/api/dashboard/ |
Dashboard and score summaries |
Authentication¶
Every API call requires authentication. Programmatic access uses API tokens passed as a Bearer header. Browser-based requests use the session cookie set at login.
See Authentication for details.
HTTP status codes¶
| Code | Meaning |
|---|---|
200 |
Success |
201 |
Resource created |
400 |
Validation error — check the response body for details |
401 |
Not authenticated — missing or invalid token |
403 |
Authenticated but lacking the required permission |
404 |
Resource not found |
409 |
Conflict — e.g. duplicate resource |
422 |
Unprocessable entity — malformed JSON or missing required field |
429 |
Rate limited — slow down and retry |