Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix NetSuite MCP connector (ns_updateRecord) fails with HTTP 400 when account default language is Portuguese [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48784•Fetched 2026-04-16 06:51:03
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
vic-rpvic-rp
Participants
vic-rpvic-rp
Timeline (top)
labeled ×4

Error Message

Error: "Invalid language. REST web services currently only support the default company language, and do not support the language specified in your user preferences. Provide the Content-Language header with your default company language value 'pt'."

Fix Action

Fix / Workaround

The connector is not sending the required Content-Language: pt header in write requests (PUT/PATCH). Read operations (SuiteQL queries via ns_runCustomSuiteQL) work correctly. Only write operations fail.

The connector should include the Content-Language: pt header in all write requests (PUT/PATCH) to match the NetSuite account's default language, allowing ns_updateRecord and ns_createRecord to work correctly in non-English NetSuite accounts.

Code Example

Error:
"Invalid language. REST web services currently only support the default 
company language, and do not support the language specified in your user 
preferences. Provide the Content-Language header with your default company 
language value 'pt'."
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The NetSuite MCP connector (ns_updateRecord) fails with HTTP 400 when the NetSuite account's default language is set to Portuguese ('pt').

Error: "Invalid language. REST web services currently only support the default company language, and do not support the language specified in your user preferences. Provide the Content-Language header with your default company language value 'pt'."

The connector is not sending the required Content-Language: pt header in write requests (PUT/PATCH). Read operations (SuiteQL queries via ns_runCustomSuiteQL) work correctly. Only write operations fail.

What Should Happen?

The connector should include the Content-Language: pt header in all write requests (PUT/PATCH) to match the NetSuite account's default language, allowing ns_updateRecord and ns_createRecord to work correctly in non-English NetSuite accounts.

Error Messages/Logs

Error:
"Invalid language. REST web services currently only support the default 
company language, and do not support the language specified in your user 
preferences. Provide the Content-Language header with your default company 
language value 'pt'."

Steps to Reproduce

  1. Connect Claude to a NetSuite account whose default language is Portuguese ('pt')
  2. Call ns_updateRecord on any record type (e.g. account)
  3. Observe HTTP 400 error with Content-Language header error

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

1.2773.0

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This issue occurs specifically with the NetSuite MCP connector integrated in Claude Desktop. The connector authenticates with a NetSuite account whose company default language is Portuguese ('pt').

The MCP tool ns_runCustomSuiteQL (read) works correctly. The MCP tool ns_updateRecord (write) fails with HTTP 400 on every attempt.

The fix should be applied on the connector side: send Content-Language: pt in the HTTP headers of all write requests to the NetSuite REST API.

This affects any NetSuite account whose default language is not English.

extent analysis

TL;DR

The NetSuite MCP connector needs to include the Content-Language header with the default company language value in write requests to fix the HTTP 400 error.

Guidance

  • Verify that the NetSuite account's default language is set to Portuguese ('pt') and that the error message matches the one provided.
  • Check the connector's code to ensure it is not sending the Content-Language header in write requests (PUT/PATCH).
  • Modify the connector to include the Content-Language header with the default company language value ('pt') in all write requests to the NetSuite REST API.
  • Test the connector with a NetSuite account whose default language is Portuguese ('pt') to verify that the fix resolves the HTTP 400 error.

Example

No code snippet is provided as the issue does not include specific code details, but the fix should involve adding a header to the HTTP requests, e.g., Content-Language: pt.

Notes

This fix should be applied to the NetSuite MCP connector to ensure compatibility with NetSuite accounts whose default language is not English.

Recommendation

Apply workaround: Modify the connector to include the Content-Language header with the default company language value in all write requests to the NetSuite REST API, as this is a necessary change to ensure compatibility with non-English NetSuite accounts.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#LLM response#prompt template#agent execution#callback error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING