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

# Set sub-5-minute export automation intervals via API

export const plans_0 = "Any"

export const deployments_0 = "Any"

export const data_plane_version_0 = undefined

export const use_case_0 = "Use case - Configuring export automation intervals below the 5-minute UI minimum using the API"

<Note>
  **Applies to:**

  * Plan - {plans_0}
  * Deployment - {deployments_0}
  * {data_plane_version_0}
  * {use_case_0}
</Note>

## Summary

**Goal:** Configure export automation intervals below the 5-minute UI minimum using the API.

**Features:** Data export automations, `interval_seconds` parameter, cloud storage export.

## Configuration steps

### Step 1: Understand the UI vs. API interval limits

The UI enforces a 5-minute minimum interval. The API allows `interval_seconds` as low as 1 second. Configs created via API with sub-5-minute values are valid but may not render cleanly in the UI edit form.

### Step 2: Set a custom interval via the API

Pass `interval_seconds` within the `config` object when creating or updating an export automation.

```json theme={"theme":{"light":"github-light","dark":"github-dark-dimmed"}}
{
  "config": {
    "interval_seconds": 60
  }
}
```

Replace `60` with your desired cadence in seconds.

### Step 3: Understand interval behavior

The interval is a **start-to-start cadence**, not a fixed schedule. Each run advances the export cursor. If a run is still in progress when the next interval fires, behavior follows standard scheduling logic.

### Step 4: Monitor export performance

With shorter intervals:

* Exports run more frequently and advance the cursor each run
* If catching up on a large backlog, exports may run nearly continuously
* Monitor export run history and bucket volume after reducing the interval

## Notes

* Sub-5-minute intervals are supported and will not break exports
* Use shorter intervals when ingesting data quickly and low latency exports are needed