> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Tracer v4 integration and authentication

> Tracer v4 guidance clarifies its deployment boundary, reservation integration, and executable quick-start authentication examples.

<Badge stroke icon="calendar-days" iconType="regular">September 3, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams deploying Tracer with Midaz v4 or using the Tracer HTTP API.

## What changed

***

Tracer is documented as a separately deployed, ELv2 source-available component in the Midaz v4 release. Its public HTTP API remains `/v1`; the internal reservation transport is distinct. Ledger `/v2` can opt in to the reservation integration, while Ledger `/v1` does not invoke it.

The integration guide now describes the default gRPC transport, the REST fallback, tenant propagation, and the required security posture. The API quick-start examples now use executable API-key and JWT header placeholders.

## Impact

***

**Classification: Review recommended.**

## What you need to do

***

Review Tracer deployment and reservation settings before adopting Midaz v4, and use the corrected authentication examples when testing the HTTP API.