How Integrations Are Documented in LangChain Reference Docs

Integrations appear in LangChain Reference Docs as one of the covered areas of the LangChain ecosystem, alongside LangChain, LangGraph, DeepAgents, and LangSmith. The reference exposes the classes, functions, and types that make up those integrations, so you can look up an integration's API surface in the same place you look up core package APIs. It is an API reference, not a guide: for setup instructions, tutorials, or conceptual explanations, the docs point you to the main documentation site.

What "integrations" means in the reference

The site describes itself as unified API reference documentation for LangChain, LangGraph, Deep Agents, LangSmith, and integrations. That phrasing places integrations in the same catalog as the first-party products rather than in a separate section. Practically, this means an integration's API entries are documented as part of the LangChain ecosystem reference, not as an isolated third-party listing.

The reference is organized around browsing packages and exploring classes, functions, and types across the ecosystem. So the unit you navigate is the package, and within a package you drill into the specific class, function, or type you need.

What you can look up

For an integration, the reference is the place to check:

• The classes an integration package exposes.
• The functions and methods available on them.
• The types used in their signatures and return values.

This is the same granularity applied to the core products, which is useful when you are wiring an integration into a chain or graph and need to confirm an exact method name, argument, or type rather than a high-level workflow.

Language coverage

The reference covers Python, TypeScript, Java, and Go packages. The site's own summary emphasizes browsing Python and TypeScript packages, while the broader description names all four languages. If you work in Java or Go, treat language coverage as something to verify per package rather than assuming every integration is documented in every language.

How integration entries relate to the main LangChain packages

Integration APIs are documented as part of the same ecosystem reference as the core packages. That means:

• You use one reference site to move between core APIs and integration APIs.
• The relationship is by package and by the classes, functions, and types each package defines, not by a separate integration index described on the page.
• The reference does not, per the available description, explain how an integration is meant to be used in a workflow — that belongs to guides and conceptual docs.

When an integration isn't in the reference

If you can't find an integration entry, work through these checks in order:

1. Confirm you're on the reference site and not the main documentation site. The reference covers APIs; the main site covers guides, tutorials, and concepts.
2. Check the language. Coverage spans Python, TypeScript, Java, and Go, but not necessarily every integration in every language.
3. Search by package rather than by product name, since the reference is organized around browsing packages.
4. If it's still missing, the integration may not be documented in the reference at all — fall back to the main documentation site for guidance.

Reference vs. main documentation site

The reference tells you what exists and how it's typed. The main site tells you how to use it. For integration work, you'll typically move between the two: confirm the API in the reference, then follow the guide on the main site.