Errorbird Documentation

Errorbird is an API-first service that brings error tracking, log management and uptime/SSL/domain monitoring together in one platform. "API-first" is not a marketing label here but an architectural decision: every piece of data the dashboard shows is read from the same public API. If you want to build your own dashboard, you will not find an endpoint missing.

What can you do in three minutes?

Need	Where to go
Collect application errors	Ingest formats — no code changes if you use Serilog
Monitor a site, certificate or domain	Uptime, SSL and domains — no integration needed
Show the data in your own dashboard	Read API and SDKs
Give your customers ready-made components	Embed widget guide
Answer KVKK/audit questions	KVKK and the data processing agreement

Core concepts

An Organization is the billing and authorization boundary. A Project is the data boundary: every event and monitor belongs to a project. A ClientWorkspace exists only in agency organizations and isolates end customers from each other.

Every project has two keys:

Secret key (ebrd_secret_…) — for writing data from your servers. Never put it in a browser; if it leaks, fake data can be produced on behalf of the project.
Publishable key (ebrd_pub_…) — for reading data from the browser and sending browser errors. It is restricted to a list of domains, so it is safe to embed in client code.

An Issue is the grouped form of the same root error. Raw events are stored separately; grouping does not replace them. For the grouping rule, see Ingest formats.

Versioning and compatibility

The API path is versioned (/api/v1/…). Removing a field from an endpoint or changing what a field means is a breaking change and ships with a new version; adding a new field is not breaking — your clients should ignore fields they do not know.