[PR #1201] [MERGED] docs: clarify Bright Data API key setup instructions #1370

Closed
opened 2026-02-17 17:22:15 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/1201
Author: @meirk-brd
Created: 10/30/2025
Status: Merged
Merged: 10/30/2025
Merged by: @mdrxy

Base: mainHead: docs/improve-brightdata-setup-instructions


📝 Commits (1)

  • a5d785d add api key claim instructions

📊 Changes

1 file changed (+2 additions, -0 deletions)

View changed files

📝 src/oss/python/integrations/providers/brightdata.mdx (+2 -0)

📄 Description

Overview

Added clearer instructions on how to get API key's from Bright Data.

Type of change

Type: Update existing documentation

Related issues/PRs

  • GitHub issue: N/A
  • Feature PR: N/A
  • Linear issue: N/A
  • Slack thread: N/A

Checklist

Additional notes

This change improves the setup instructions by providing a concrete Python code example for setting the API key environment variable, making it easier for users to get started with langchain-brightdata.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/1201 **Author:** [@meirk-brd](https://github.com/meirk-brd) **Created:** 10/30/2025 **Status:** ✅ Merged **Merged:** 10/30/2025 **Merged by:** [@mdrxy](https://github.com/mdrxy) **Base:** `main` ← **Head:** `docs/improve-brightdata-setup-instructions` --- ### 📝 Commits (1) - [`a5d785d`](https://github.com/langchain-ai/docs/commit/a5d785da088ac53244e153273164b31cac2e338f) add api key claim instructions ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/oss/python/integrations/providers/brightdata.mdx` (+2 -0) </details> ### 📄 Description ## Overview Added clearer instructions on how to get API key's from Bright Data. ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: N/A - Feature PR: N/A <!-- For LangChain employees, if applicable: --> - Linear issue: N/A - Slack thread: N/A ## Checklist <!-- Put an 'x' in all boxes that apply --> - [X] I have read the [[contributing guidelines](README.md) - [X] I have tested my changes locally using `docs dev` - [X] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [[Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes This change improves the setup instructions by providing a concrete Python code example for setting the API key environment variable, making it easier for users to get started with langchain-brightdata. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-17 17:22:15 -05:00
yindo closed this issue 2026-02-17 17:22:15 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#1370