[BUG] Brave Search connector: UI Language dropdown does not follow Brave API Market Codes (e.g., missing ja-JP)

[kahara33]

Type of Connector

Independent Publisher Connector

Name of Connector

Brave Search (Independent Publisher)

Describe the bug

Summary
The "UI Language" parameter in the Search web action shows a dropdown that does not match Brave Web Search API's Market Codes. For example, "ja-JP" is not available and users must pick "Custom value" and type "ja-JP" manually.

Steps to Reproduce

1. In Power Automate or Logic Apps, add the Brave Search – Search web action.
2. Open the UI Language dropdown.
3. Try to select "ja-JP".

Actual Behavior

• The dropdown lists values that look like language codes (e.g., en, ja, zh-hans) and "ja-JP" is missing.
• Users have to select "Custom value" and type "ja-JP" to get the expected behavior.

Expected Behavior

• The UI Language dropdown should list Brave API Market Codes (locale), e.g., en-US, ja-JP, it-IT, ko-KR, etc., OR the doc should clearly instruct users to enter a valid Market Code.

Impact

• Misleads users into thinking ui_lang accepts language codes.
• Causes inconsistent requests and localization.

Proposed Fix

• Replace the dropdown items with Brave's Market Codes, or remove incorrect presets and document that ui_lang requires a Market Code.
• Clearly distinguish parameter types in docs:
  • ui_lang → market/locale code (e.g., en-US, ja-JP)
  • search_lang → language code (e.g., en, ja)
  • country → country code (e.g., US, JP)

References

• Microsoft Learn (Search web): https://learn.microsoft.com/en-us/connectors/bravesearch/#search-web
• Brave API Market Codes: https://api-dashboard.search.brave.com/app/documentation/web-search/codes#market-codes

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 3 - Minor issue

To Reproduce

1. Create a Power Automate flow (or Logic Apps standard/consumption workflow).
2. Add the Brave Search – Search web action.
3. Open the UI Language dropdown.
4. Try to select ja-JP (or other locale/market codes such as en-US, it-IT).
5. Observe that ja-JP is not in the list and you must choose Custom value and type ja-JP manually.
6. Run the action with ui_lang=jp vs ui_lang=ja-JP and compare results.

Expected behavior

• The UI Language dropdown should list Brave API Market Codes (locale) such as en-US, ja-JP, it-IT, ko-KR, etc., or the doc should clearly instruct users to enter a valid Market Code.

• Values offered in the dropdown must match (or be auto-validated against) Brave’s Market Codes list.

• Parameters should be clearly distinguished:

  • ui_lang → market/locale code (e.g., ja-JP)
  • search_lang → language code (e.g., ja)
  • country → country code (e.g., JP)

Environment summary

• Surface: Power Automate (cloud) / Azure Portal – Logic Apps
• Connector: Brave Search (Independent Publisher) → Search web action
• Region/tenant: e.g., Asia / Commercial tenant (replace if different)
• Browser: e.g., Chrome 129 (replace with yours)
• No CLI used; repro is fully in the UI.
• Workaround: selecting Custom value and entering ja-JP works.

Additional context

• The dropdown currently shows values that look like language codes (e.g., en, ja, zh-hans) and omits ja-JP. This misleads users into believing ui_lang accepts language codes.
• Brave documentation requires Market Codes for ui_lang:
  Codes → Market Codes: https://api-dashboard.search.brave.com/app/documentation/web-search/codes#market-codes
• Microsoft Learn page for reference (where users follow the parameter descriptions):
  https://learn.microsoft.com/en-us/connectors/bravesearch/#search-web
• Please align the dropdown with Brave’s Market Codes (or remove incorrect presets and document the requirement).

[troystaylor]

@kahara33 Thank you for reporting this bug. I have submitted an update PR: #4039
Feel free to make a custom connector with the updated Swagger until the update has been certified.
@vmanoharas Please close bug when PR is merged.

[vmanoharas]

Hi @troystaylor,

Thank you for notifying me. Request you to please submit the package zip file in the PR.