> ## 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: spending limit documentation update

> The public Tracer documentation now explains the full spending limit model, including periods, scheduling fields, amount format, and validation timing.

<Badge stroke icon="calendar-days" iconType="regular">May 14, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="green" size="lg" stroke icon="circle-check" iconType="regular">No migration required</Badge>

## Affects

***

Customers and teams reading the public Tracer documentation to configure spending limits or understand validation responses.

This update applies to the public documentation portal. It does not change the runtime API behavior.

<Note>
  The public documentation portal is the customer-facing reference. Repository source files should not be treated as integration artifacts or downloaded API specifications for client use.
</Note>

## What changed

***

### Spending limit periods

The public documentation now shows the full set of supported spending limit periods:

| Value             | Description                            |
| ----------------- | -------------------------------------- |
| `PER_TRANSACTION` | Applies to each individual transaction |
| `DAILY`           | Applies over a daily period            |
| `WEEKLY`          | Applies over a weekly period           |
| `MONTHLY`         | Applies over a monthly period          |
| `CUSTOM`          | Applies over a custom date range       |

### Scheduling fields

The documentation now explains the optional scheduling fields used to control when a limit applies:

| Field             | Description                                                   |
| ----------------- | ------------------------------------------------------------- |
| `activeTimeStart` | Time of day when the limit starts applying, in `HH:mm` format |
| `activeTimeEnd`   | Time of day when the limit stops applying, in `HH:mm` format  |
| `customStartDate` | Start date for a custom-period limit                          |
| `customEndDate`   | End date for a custom-period limit                            |

<Note>
  For `CUSTOM` limits, provide both `customStartDate` and `customEndDate`.
</Note>

### Limit amount

The documentation now makes the amount format explicit.

For spending limits, send `maxAmount` as a decimal string:

**Before**

```json theme={null}
{
  "limitType": "DAILY",
  "maxAmount": 100000
}
```

**After**

```json theme={null}
{
  "limitType": "DAILY",
  "maxAmount": "1000.00"
}
```

For a custom-period limit:

```json theme={null}
{
  "limitType": "CUSTOM",
  "maxAmount": "5000.00",
  "customStartDate": "2026-06-01T00:00:00Z",
  "customEndDate": "2026-06-30T23:59:59Z"
}
```

### Validation response timing

Validation response timing fields now allow decimal values because processing time may include fractions of a millisecond.

## Impact

***

This is a documentation update. It clarifies the public documentation portal for Tracer limits.

No migration is required if your current Tracer integration is already working. Use the updated documentation when configuring new limits or reviewing existing ones.

## What you need to do

***

<Steps>
  <Step>
    Use one of the documented limit periods: `PER_TRANSACTION`, `DAILY`, `WEEKLY`, `MONTHLY`, or `CUSTOM`.
  </Step>

  <Step>
    Send `maxAmount` as a decimal string, such as `"1000.00"`.
  </Step>

  <Step>
    Use `activeTimeStart` and `activeTimeEnd` in `HH:mm` format when a limit applies only during part of the day.
  </Step>

  <Step>
    Include both `customStartDate` and `customEndDate` for `CUSTOM` limits.
  </Step>

  <Step>
    Keep transaction amounts and usage counters in the smallest currency unit where the documentation says those fields are integer values.
  </Step>

  <Step>
    Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.
  </Step>
</Steps>

### Deadline

None.

### Why

The previous documentation did not show the full Tracer limit model. This update prevents readers from implementing limits from incomplete examples.

## Resources

***

* [Create limit](/en/reference/tracer/create-limit)
* [Spending limits guide](/en/tracer/spending-limits)
* [Tracer API quick start](/en/reference/tracer/tracer-api-quick-start)