Getting API access

Getting API access

These developer docs are public. Read them, evaluate the API, and plan an integration without an account. But issuing an API key is gated: programmatic access is granted to open-source developers and to enterprise customers. This page explains who qualifies and how to request it.

The public programmatic surface is /api/v1/*. Everything a third-party integration needs (upload, status polling, dashboards, and search) lives there.

Who qualifies

Open-source developers

If you maintain or contribute to an open-source project (an Android app, a ROM, a kernel, a device tree, a CI pipeline that produces logs), you can request access through the open-source developer program. This is the path for individual developers and community projects that want to script uploads and pull analysis results.

Enterprise customers

Enterprise accounts get programmatic access through the api_access capability on the enterprise. An admin enables it (or requests it from developer@logcat.ai); once set, API keys issued to users in that enterprise are accepted on /api/v1/*. Ask your administrator to turn it on.

The capability is required for every account, not just team accounts. If you’re not part of a team, it applies to you individually and is granted through the open-source developer program or on request. Without it you can’t generate a key, and any key you already hold is refused at authentication with a 403 saying API access isn’t enabled.

How to request access

  1. Open-source developers: apply to the open-source developer program from your account. Once approved, you can generate a key in the console.
  2. Enterprise customers: have an enterprise admin enable the api_access capability (or email developer@logcat.ai to request it). Members of the enterprise can then generate keys.

Once your account is eligible, generate a key in the Console and make your first call:

Next steps