Public API

Use the NeatLogs Public API to query traces, inspect detections, work with evaluations, and manage project resources from your applications and automation. Requests use HTTPS, explicit context, and scoped credentials.

https://app.neatlogs.com/api/v1/public

For an EU deployment, use https://eu.app.neatlogs.com/api/v1/public with an EU credential. EU access requires the public API to be deployed and enabled in that region; a working dashboard or SDK ingest endpoint alone does not establish API availability.

Make your first API call

Create a service account, select a project, and read recent traces with cURL.

Use the CLI

Authentication and scopes

Choose credentials and understand project roles and permissions.

Endpoint reference

Explore methods, parameters, request bodies, responses, and scopes for every published operation.

Request and response format

Send a Bearer token and the UUID of an authorized project. Project-scoped requests use the x-project-id header; discovery and organization operations declare their own context in the reference.

GET /api/v1/public/project
Authorization: Bearer <service-account-token>
x-project-id: <project-uuid>

JSON success responses contain success: true, a server-generated requestId, and data. Errors use application/problem+json with a stable code and requestId. Lists use cursor pagination.

Choose the interface

Goal	Start here
Inspect a project as a person	CLI browser login
Run CI, scripts, or an AI agent	Service-account quickstart
Send traces from an application	SDK setup
Import schemas or generate a client	Download OpenAPI JSON

The endpoint reference describes the published contract. Some operations require deployment capabilities or plan access; review operation availability before building a workflow around them. The Public API and CLI support NeatLogs cloud deployments; self-hosted deployments are currently unsupported.