Projects and API keys

This page covers the two things you need before sending logs: a project and an API key.

ProjectsCopy Anchor Link

A project groups the logs of one application or service, with its own error groups, tickets, channels and notification settings. Admins and owners create projects under Projects in the organization, with New project. The number of projects depends on the plan (Plans and usage).

Deleting a project deletes its keys, channels, groups and tickets. It cannot be undone.

API keysCopy Anchor Link

Applications authenticate with a project API key:

Authorization: Bearer lgf_live_<key_id>_<secret>

Admins and owners create keys under API keys in the project, with Create API key. The full key is shown once, right after it is created; dlogify stores only a hash of the secret and cannot show it again. Keep it in an environment variable such as LOGIFY_API_KEY, never in source control.

Until the project receives its first log, the project's Overview shows ready-to-paste setup for curl and for OpenTelemetry, a button to create a key, and Waiting for the first log…. Once a log arrives, the setup folds away and the overview shows the project's recent tickets and error groups.

A key only sends logs to its own project. It cannot read data or call management endpoints.

Rotating a keyCopy Anchor Link

1. Create a new key.
2. Deploy it to your applications.
3. Once nothing uses the old key, revoke it on the same page.

A revoked key stops working within seconds. Requests that use it get 401 unauthorized.