LangSmith 403 batch ingest: EU endpoint is eu.api.smith.langchain.com
If LangSmith batch ingest returns 403, check your LANGCHAIN_ENDPOINT: EU users need https://eu.api.smith.langchain.com, not the value the dashboard suggests. Use this skill when the task matches the title above. Not for unrelated tools or errors; check the tool's own docs for those.
TL;DR
If LangSmith batch ingest returns 403, check your LANGCHAINENDPOINT: EU users need https://eu.api.smith.langchain.com, not the value the dashboard suggests. Also load your dotenv file before importing or initializing the langsmith client, otherwise the endpoint and key never get picked up. Community members tracked it down: the LangSmith dashboard told users to set LANGCHAINENDPOINT to https://eu.smith.langchain.com, but the correct endpoint value is https://eu.api.smith.langchain.com.
Fix
If LangSmith batch ingest returns 403, check your LANGCHAIN_ENDPOINT: EU users need https://eu.api.smith.langchain.com, not the value the dashboard suggests. Also load your dotenv file before importing or initializing the langsmith client, otherwise the endpoint and key never get picked up.
Context: LangSmith SDK issue #637 (closed): batch ingest failed with 403 Forbidden for users in the EU region. Community members tracked it down: the LangSmith dashboard told users to set LANGCHAIN_ENDPOINT to https://eu.smith.langchain.com, but the correct endpoint value is https://eu.api.smith.langchain.com. Users who corrected the endpoint resolved the 403. A related variant of the same failure came from loading the dotenv file after the langsmith client was already initialized, so the env vars never applied.
Matched source
Source: Published skill Original query: "LangSmith 403 batch ingest: EU endpoint is eu.api.smith.langchain.com" Key terms: batch, endpoint, ingest, langchain, langsmith, smith
When to use this
- Use this when your task, error, or question matches the title above and the setup in the Fix section.
When not to use this
- Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.
Compatibility
The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.