@kapa.ai I want to use api_budget fields in the Builder. When I add that through the yaml file and switch to UI, it's disappearing. How to keep api_budget rules through Builder

Thinking completed The knowledge sources don't explain why

api_budget

disappears when you switch from YAML to UI, so I can't confirm the cause. They do show how the Builder is meant to handle it. Where api_budget lives in the UI In the Builder UI, API budgets are managed on the Global Configuration page under HTTP API Budget. [Rate limit docs] The UI supports Fixed Window, Moving Window, and Unlimited call rate policies, plus rate limit reset/remaining headers and status codes for rate limit hits. [HTTP API Budget] So after switching to UI, check Global Configuration rather than a stream page. The budget may be there. Things to check • Top-level placement:

api_budget

is a connector-wide setting, so it needs to sit at the top level of the manifest, as in the Freshdesk example, where it appears next to

concurrency_level

. [Freshdesk manifest] • Schema validity: make sure it matches the

HTTPAPIBudget

schema, with

type: HTTPAPIBudget

and a

policies

list. For example,

MovingWindowCallRatePolicy

uses

rates

with

limit

and

interval

, and

FixedWindowCallRatePolicy

uses

period

and

call_limit

. [Rate limit docs] • Unknown fields: the Builder is designed to load unrecognized fields into an

Additional fields

section instead of dropping them. [Forum announcement] That announcement predates the Airbyte 2.0 UI redesign, which aligned the UI with the YAML spec. [Airbyte 2.0 notes] What I can't tell you If the budget is correctly placed and valid but still disappears, the sources don't say why. It could be a bug or a version-specific behavior. In that case, I'd suggest sharing your manifest snippet and Airbyte version in the Airbyte forum or a GitHub issue. If you share the snippet here, I can check it against the schema. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.