1. Create an errors project
From the realuptime errors dashboard, create a project for each app or service. Each project has its own ingest key.
2. Add the ingest key to your app
The key ships inside your client bundle by design; it can do exactly one thing: submit error events for that project. Rotating it in settings revokes the old key, which then refuses loudly (RU-4002) so old deploys log it once and stop.
3. Send events in batches
The SDK batches events to POST /api/errors/v1/ingest/<key>. A malformed batch is refused whole (RU-4004) and counted, never partially accepted: partial acceptance would fabricate data.
4. Watch quota and drops on the dashboard
Every drop (rate-limited RU-4003, over-quota RU-4001, malformed, or client-side) is counted and shown on the dashboard. Nothing disappears silently.
Go deeper
The full reference lives in the docs: Getting started documentation. Error codes named above are each explained in the error-code reference.