Provides an HTTP Transport that implements the `RoundTripper` interface and can be used as a built in replacement for the standard library's, providing: * connection timeouts * request timeouts This is a thin wrapper around `http.Transport` that sets dial timeouts and uses Go's internal timer scheduler to call the Go 1.1+ `CancelRequest()` API.
Package cert contains certificate tools for Google API clients.
Package dca contains utils for implementing Device Certificate Authentication according to https://google.aip.dev/auth/4114
Package otel provides global access to the OpenTelemetry API. The subpackages of the otel package provide an implementation of the OpenTelemetry API. The provided API is used to instrument code and measure data about that code's performance and operation. The measured data, by default, is not processed or transmitted anywhere. An implementation of the OpenTelemetry SDK, like the default SDK implementation (go.opentelemetry.io/otel/sdk), and associated exporters are used to process and transport this data. To read the getting started guide, see https://opentelemetry.io/docs/languages/go/getting-started/. To read more about tracing, see go.opentelemetry.io/otel/trace. To read more about metrics, see go.opentelemetry.io/otel/metric. To read more about logs, see go.opentelemetry.io/otel/log. To read more about propagation, see go.opentelemetry.io/otel/propagation and go.opentelemetry.io/otel/baggage.
Package client is the sock API client shared by sock-cli and sock-mcp: config validation, an authenticated Connect transport, retries and error text.
Package ai is go-ai's model client: one transport over the protocol, in the wire format its constructor is given, with Go primitives over the inference engines' native APIs and no vendor SDK.
Package response provides transport-independent API response models and constructors.
Package client is the sock API client shared by sock-cli and sock-mcp: config validation, an authenticated Connect transport, retries and error text.
Package dosjson provides primitives for working with the Decred JSON-RPC API. When communicating via the JSON-RPC protocol, all of the commands need to be marshalled to and from the the wire in the appropriate format. This package provides data structures and primitives to ease this process. In addition, it also provides some additional features such as custom command registration, command categorization, and reflection-based help generation. This information is not necessary in order to use this package, but it does provide some intuition into what the marshalling and unmarshalling that is discussed below is doing under the hood. As defined by the JSON-RPC spec, there are effectively two forms of messages on the wire: Request Objects {"jsonrpc":"1.0","id":"SOMEID","method":"SOMEMETHOD","params":[SOMEPARAMS]} NOTE: Notifications are the same format except the id field is null. Response Objects {"result":SOMETHING,"error":null,"id":"SOMEID"} {"result":null,"error":{"code":SOMEINT,"message":SOMESTRING},"id":"SOMEID"} For requests, the params field can vary in what it contains depending on the method (a.k.a. command) being sent. Each parameter can be as simple as an int or a complex structure containing many nested fields. The id field is used to identify a request and will be included in the associated response. When working with asynchronous transports, such as websockets, spontaneous notifications are also possible. As indicated, they are the same as a request object, except they have the id field set to null. Therefore, servers will ignore requests with the id field set to null, while clients can choose to consume or ignore them. Unfortunately, the original Bitcoin JSON-RPC API (and hence anything compatible with it) doesn't always follow the spec and will sometimes return an error string in the result field with a null error for certain commands. However, for the most part, the error field will be set as described on failure. Based upon the discussion above, it should be easy to see how the types of this package map into the required parts of the protocol To simplify the marshalling of the requests and responses, the MarshalCmd and MarshalResponse functions are provided. They return the raw bytes ready to be sent across the wire. Unmarshalling a received Request object is a two step process: This approach is used since it provides the caller with access to the additional fields in the request that are not part of the command such as the ID. Unmarshalling a received Response object is also a two step process: As above, this approach is used since it provides the caller with access to the fields in the response such as the ID and Error. This package provides two approaches for creating a new command. This first, and preferred, method is to use one of the New<Foo>Cmd functions. This allows static compile-time checking to help ensure the parameters stay in sync with the struct definitions. The second approach is the NewCmd function which takes a method (command) name and variable arguments. The function includes full checking to ensure the parameters are accurate according to provided method, however these checks are, obviously, run-time which means any mistakes won't be found until the code is actually executed. However, it is quite useful for user-supplied commands that are intentionally dynamic. The command handling of this package is built around the concept of registered commands. This is true for the wide variety of commands already provided by the package, but it also means caller can easily provide custom commands with all of the same functionality as the built-in commands. Use the RegisterCmd function for this purpose. A list of all registered methods can be obtained with the RegisteredCmdMethods function. All registered commands are registered with flags that identify information such as whether the command applies to a chain server, wallet server, or is a notification along with the method name to use. These flags can be obtained with the MethodUsageFlags flags, and the method can be obtained with the CmdMethod function. To facilitate providing consistent help to users of the RPC server, this package exposes the GenerateHelp and function which uses reflection on registered commands or notifications, as well as the provided expected result types, to generate the final help text. In addition, the MethodUsageText function is provided to generate consistent one-line usage for registered commands and notifications using reflection. There are 2 distinct type of errors supported by this package: The first category of errors (type Error) typically indicates a programmer error and can be avoided by properly using the API. Errors of this type will be returned from the various functions available in this package. They identify issues such as unsupported field types, attempts to register malformed commands, and attempting to create a new command with an improper number of parameters. The specific reason for the error can be detected by type asserting it to a *dosjson.Error and accessing the ErrorCode field. The second category of errors (type RPCError), on the other hand, are useful for returning errors to RPC clients. Consequently, they are used in the previously described Response type. This example demonstrates how to unmarshal a JSON-RPC response and then unmarshal the result field in the response to a concrete type.
Package apiquery compiles declared API query capabilities into immutable, transport-neutral plans.
Package postmark is the Postmark plugin: a transport that sends the mailer package's emails with Postmark's API (https://postmarkapp.com), and webhooks that keep a list of the addresses Postmark stopped sending to (Plugin).
Package notify provides a generic, provider-agnostic notification delivery API: a shared Message type, a uniform Sender interface, and a family of provider packages (Discord, Slack, Gotify, Pushover, Ntfy, Telegram, generic webhook, and email) that each implement Sender on top of a shared, SSRF-safe HTTP transport (see the transport package).
Package control is the listener for a daemon's gRPC admin (control-plane) API: the port an operator's CLI talks to, as opposed to the one the daemon's users talk to.
Package apiquery compiles declared API query capabilities into immutable, transport-neutral plans.
Package apiquery compiles declared API query capabilities into immutable, transport-neutral plans.
Package statesync provides authoritative rooms and a transport-independent game API.
Package mihari provides a structured log collection and transport library that ships log entries to the Mihari HTTP API.
Package transport owns the HTTP, SSE, WebSocket and gRPC wire boundary.
Package wecom exposes the WeCom CGI API set: a shared authenticated transport plus one client per API namespace.
Package etcdhttp implements HTTP transportation layer for etcdserver.
Package transport implements the redesigned transport API for go-git.
Package http implements the HTTP and HTTPS transport for the transport API.
Package file implements the file transport for the new transport API.
Package ssh implements the SSH transport for the new transport API.
Package git implements the Git TCP transport for the new transport API.
Package rafthttp implements HTTP transportation layer for etcd/raft pkg.
Package etcdhttp implements HTTP transportation layer for etcdserver.
Package capydbclient is the shared HTTP transport for the CapyDB control-plane API clients - the CLI and the Terraform provider.
Package betterstack sends log entries to Better Stack's log management platform via their HTTP intake API.
Package newrelic sends log entries to the New Relic Logs HTTP intake API.
Package loglayer is a transport-agnostic structured logger with a fluent builder API.
Package httpstream contains compatibility wrappers for streaming transport APIs.
Package transport provides utility methods for creating authenticated transports to Google's HTTP and gRPC APIs.
Package datadog sends log entries to the Datadog Logs HTTP intake API.
Package otel provides global access to the OpenTelemetry API. The subpackages of the otel package provide an implementation of the OpenTelemetry API. The provided API is used to instrument code and measure data about that code's performance and operation. The measured data, by default, is not processed or transmitted anywhere. An implementation of the OpenTelemetry SDK, like the default SDK implementation (go.opentelemetry.io/otel/sdk), and associated exporters are used to process and transport this data. To read the getting started guide, see https://opentelemetry.io/docs/languages/go/getting-started/. To read more about tracing, see go.opentelemetry.io/otel/trace. To read more about metrics, see go.opentelemetry.io/otel/metric. To read more about logs, see go.opentelemetry.io/otel/log. To read more about propagation, see go.opentelemetry.io/otel/propagation and go.opentelemetry.io/otel/baggage.
Package elasticsearch provides a Go client for Elasticsearch. Create the client with the NewDefaultClient function: The ELASTICSEARCH_URL environment variable is used instead of the default URL, when set. Use a comma to separate multiple URLs. To configure the client, pass a Config object to the NewClient function: When using the Elastic Service (https://elastic.co/cloud), you can use CloudID instead of Addresses. When either Addresses or CloudID is set, the ELASTICSEARCH_URL environment variable is ignored. See the elasticsearch_integration_test.go file and the _examples folder for more information. Call the Elasticsearch APIs by invoking the corresponding methods on the client: See the github.com/elastic/go-elasticsearch/esapi package for more information about using the API. See the github.com/elastic/go-elasticsearch/estransport package for more information about configuring the transport.
Package elasticsearch provides a Go client for Elasticsearch. Create the client with the NewDefaultClient function: The ELASTICSEARCH_URL environment variable is used instead of the default URL, when set. Use a comma to separate multiple URLs. To configure the client, pass a Config object to the NewClient function: When using the Elastic Service (https://elastic.co/cloud), you can use CloudID instead of Addresses. When either Addresses or CloudID is set, the ELASTICSEARCH_URL environment variable is ignored. See the elasticsearch_integration_test.go file and the _examples folder for more information. Call the Elasticsearch APIs by invoking the corresponding methods on the client: See the github.com/elastic/go-elasticsearch/esapi package for more information about using the API. See the github.com/elastic/go-elasticsearch/estransport package for more information about configuring the transport.
Package elasticsearch provides a Go client for Elasticsearch. Create the client with the NewDefaultClient function: The ELASTICSEARCH_URL environment variable is used instead of the default URL, when set. Use a comma to separate multiple URLs. To configure the client, pass a Config object to the NewClient function: When using the Elastic Service (https://elastic.co/cloud), you can use CloudID instead of Addresses. When either Addresses or CloudID is set, the ELASTICSEARCH_URL environment variable is ignored. See the elasticsearch_integration_test.go file and the _examples folder for more information. Call the Elasticsearch APIs by invoking the corresponding methods on the client: See the github.com/elastic/go-elasticsearch/esapi package for more information about using the API. See the github.com/elastic/elastic-transport-go package for more information about configuring the transport.
Package micro is a pluggable framework for microservices
Package notify provides a generic, provider-agnostic notification delivery API: a shared Message type, a uniform Sender interface, and a family of provider packages (Discord, Slack, Gotify, Pushover, Ntfy, Telegram, generic webhook, and email) that each implement Sender on top of a shared, SSRF-safe HTTP transport (see the transport package).
Package ptv is a client for the Public Transport Victoria Timetable API v3.
Package bankingcircle is a production-grade Go client for the Banking Circle Connect API (https://docs.bankingcircleconnect.com): cross-border payments (single & bulk), accounts, virtual accounts (VIBANs), FX (market order / RFQ / held-rate trading, plus WebSocket quote streaming), reporting, case management (RFI / recall), direct debit collections, ISO20022 message transport, and webhooks (subscription management + AES-256-GCM payload verification).
Package agentpass provides backend OAuth, identity, usage, and embed clients plus transport helpers for provider-native AI APIs.
Package openai implements a provider.LanguageModel backed by the OpenAI Responses API (POST /v1/responses) using the official github.com/openai/openai-go/v3 SDK for transport, request params, and SSE event types.
Package apiquery compiles declared API query capabilities into immutable, transport-neutral plans.
Package tinvest is a read-only Go client for the T-Bank Invest gRPC API, wrapping the same broker and transport layers the tinvest CLI uses over one shared connection with the full interceptor stack: Bearer auth, per-call deadlines, call-phase and x-tracking-id capture, the idempotency-aware retry policy, and client-side rate limiting.
Package monobank is the base HTTP transport for every monobank API surface.