API access and project keys
Choose the correct ErrorDock project key for server, browser and distributed applications, and see the ingestion endpoints, request and rate limits, and the read-only API.
Project keys connect telemetry to an ErrorDock project. Telemetry goes to https://api.errordock.com; the dashboard is at https://app.errordock.com.
Choose the correct key
| Prefix | Intended use |
|---|---|
ed_live_ |
Server applications and trusted environments. Keep it secret. With the artifacts:write scope it also uploads source maps. |
ed_pub_ |
Browser applications. Designed to appear in a client bundle, and accepted only from the exact origins you allow. |
ed_app_ |
Distributed mobile and desktop applications. Treat it as public. |
Telemetry keys can only send data; they cannot read anything back. That is what makes an ingest key write-only: a key copied out of a client bundle lets someone send events to your project, not read your issues.
Use the smallest set of scopes needed. A telemetry ingestion key is not a general-purpose user credential and does not grant dashboard access. Administrative integrations must use the authentication and scopes required by the specific endpoint.
Send telemetry
The SDK handles batching and delivery. Authenticate with the project key in the Authorization header.
| Endpoint | Accepts |
|---|---|
POST /api/v1/events |
Individual events, as JSON |
POST /api/v1/envelope |
Batches, as NDJSON; gzip is allowed |
POST /api/v1/spans |
Spans in ErrorDock's native format |
POST /api/v1/traces |
OpenTelemetry over OTLP/HTTP with the JSON encoding. Protobuf and gRPC are not accepted. |
POST /v1/artifacts?release=<release>&name=<file name> |
A source map, with an ed_live_ key that has the artifacts:write scope. Maps up to 60 MB. |
An accepted event still needs background processing before it appears in queries. During the beta, source-map upload is enabled per organisation.
Limits
| Limit | Value |
|---|---|
| Request size | 1 MiB compressed, 10 MiB decompressed |
| Items per envelope | 500 |
| Spans per request | 1,000 |
Rate, secret key (ed_live_) |
100 requests per second |
| Rate, browser and app keys | 50 requests per second, per key and IP address |
Handle rate-limit and quota responses rather than treating every response as acceptance. On a 429 or 503, wait as long as the Retry-After header says before trying again.
Read API
A read-only API exists for your own tooling. It uses personal access tokens (ed_pat_) with the scopes issues:read and analytics:read, and covers projects, issues, issue events, releases and analytics. There is no public reference yet: ask us for the reference.
Keep environments explicit
Configure the API endpoint, project key and release identifier for the intended environment. Verify the first test event before deploying instrumentation more widely.
Customer email delivery
The previous customer email sending API has been removed. Use your own email provider. ErrorDock's own alert notifications are separate.
See SDK documentation, capturing errors and data handling.
Last updated October 20, 2026