Go Team Launches Official pkg.go.dev API, Replacing Years of Web Scraping Workarounds
The Go team published a formal REST API for pkg.go.dev on May 21, giving tool authors and IDE integrations a stable, versioned interface to module metadata, documentation, symbols, and vulnerability data.
Overview
The Go team on May 21, 2026 published a formal API for pkg.go.dev, the official home for Go package documentation and module discovery. The announcement, authored by Ethan Lee, Hana Kim, and Jonathan Amsterdam, introduces a stable, machine-readable interface that fills a long-standing gap in the Go tooling ecosystem: until now, developers who needed programmatic access to package metadata had no sanctioned path.
“Developers building tools, IDE integrations, and automated workflows have historically relied on fragile workarounds like web scraping to access this data,” the Go team wrote. The team cites the rise of AI-assisted coding as making the need more acute: “Tools can now access the specific, high-fidelity context needed to reason about the Go ecosystem with greater precision.”
Eight Endpoints Under /v1beta
The API ships under a /v1beta path, signaling that the team intends to collect community feedback before committing to a formal v1. All eight endpoint families are documented in the API specification, and a machine-readable contract is published as an OpenAPI YAML file at pkg.go.dev/v1beta/openapi.yaml.
The endpoints cover the core operations developers need when building Go tooling:
/v1beta/package/{path}— package metadata, documentation, imports, and examples/v1beta/module/{path}— module-level information including repository URL and redistribution status/v1beta/versions/{path}— tagged versions and recent pseudo-versions, with pagination/v1beta/packages/{path}— all packages contained in a module/v1beta/search?q={query}— full-text search across package paths and synopses/v1beta/symbols/{path}— declared symbols for a package, filterable by name/v1beta/imported-by/{path}— packages that import a given package/v1beta/vulns/{path}— known vulnerabilities sourced from the Go vulnerability database atvuln.go.dev
All requests are GET-only and the API is stateless, a design the team chose to keep integrations simple and responses highly cacheable, per the API documentation.
Precision Over Convenience
A key design choice distinguishes the new API from the pkg.go.dev web interface. “One design principle for this API is ‘precision over convenience,’” the Go team explained. Because a Go import path like a/b/c could belong to packages in either module a/b or module a, the web interface silently applies a longest-match heuristic. The API instead returns an error alongside a candidates field listing the ambiguous matches, requiring the caller to supply an explicit module query parameter to proceed.
The version parameter supports semantic versions (?version=v1.2.3), branch names (?version=master or ?version=main — which resolve automatically to the corresponding pseudo-version), or can be omitted entirely to receive the latest tagged release.
A Reference Client: pkgsite-cli
Alongside the API, the Go team released pkgsite-cli, a command-line reference implementation installable via:
go install golang.org/x/pkgsite/cmd/internal/pkgsite-cli@latestThe CLI is not positioned as a production tool — the announcement notes its interface is not yet stable — but rather as a practical demonstration of the API’s capabilities. It supports search, package inspection, imported-by queries, symbol listing, and combined module version and package output.
Backward Compatibility Commitment
The Go team committed to stability for integrations built on the new API. “While we plan to expand the interface’s capabilities over time, we are committed to maintaining backward compatibility so that existing integrations continue to function seamlessly,” the team wrote.
What We Don’t Know
The team has not announced a timeline for the transition from /v1beta to a stable /v1 path. Rate limiting behavior, authentication requirements for high-volume use, and any SLA commitments are not addressed in the launch post. The pkgsite-cli CLI interface remains explicitly unstable and is subject to change without notice.
Also open: a concurrent proposal from Alan Donovan of the Go team to discontinue gccgo support, the Go frontend for GCC, was filed around the same time and is actively being discussed in the community. The proposal is unrelated to the API but reflects broader ongoing work to streamline the Go toolchain.