microsoft / microsoft/PowerPlatformConnectors
[BUG] Brave Search connector: UI Language dropdown does not follow Brave API Market Codes (e.g., missing ja-JP)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
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
- In Power Automate or Logic Apps, add the Brave Search – Search web action.
- Open the UI Language dropdown.
- 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
- Create a Power Automate flow (or Logic Apps standard/consumption workflow).
- Add the Brave Search – Search web action.
- Open the UI Language dropdown.
- Try to select
ja-JP(or other locale/market codes such asen-US,it-IT). - Observe that
ja-JPis not in the list and you must choose Custom value and typeja-JPmanually. - Run the action with
ui_lang=jpvsui_lang=ja-JPand 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-JPworks.
Additional context
- The dropdown currently shows values that look like language codes (e.g.,
en,ja,zh-hans) and omitsja-JP. This misleads users into believingui_langaccepts 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).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Brave Search connector's Search web action and compare the UI Language dropdown values with the linked Brave Market Codes documentation. Done means the dropdown uses locale codes such as ja-JP, or the connector documentation clearly explains how ui_lang, search_lang, and country differ and how to enter a custom value.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100