This documentation is automatically synced from the Go SDK GitHub repository.
Installation
Requirements
This library requires Go 1.22+.Usage
The full API of this library can be found in api.md.Running the example
A complete working example is available inexamples/basic.go. To run it:
- Set up environment variables by creating a
.envfile in the repository root:
- Install dependencies:
- Run the example:
Request fields
The stagehand library uses theomitzero
semantics from the Go 1.24+ encoding/json release for request fields.
Required primitive fields (int64, string, etc.) feature the tag json:"...,required". These
fields are always serialized, even their zero values.
Optional primitive types are wrapped in a param.Opt[T]. These fields can be set with the provided constructors, stagehand.String(string), stagehand.Int(int64), etc.
Any param.Opt[T], map, slice, struct or string enum uses the
tag json:"...,omitzero". Its zero value is considered omitted.
The param.IsOmitted(any) function can confirm the presence of any omitzero field.
null instead of a param.Opt[T], use param.Null[T]().
To send null instead of a struct T, use param.NullStruct[T]().
.SetExtraFields(map[string]any) method which can send non-conforming
fields in the request body. Extra fields overwrite any struct fields with a matching
key. For security reasons, only use SetExtraFields with trusted data.
To send a custom value instead of a struct, use param.Override[T](https://github.com/browserbase/stagehand-go/blob/main/value).
Request unions
Unions are represented as a struct with fields prefixed by “Of” for each of its variants, only one field can be non-zero. The non-zero field will be serialized. Sub-properties of the union can be accessed via methods on the union struct. These methods return a mutable pointer to the underlying data, if present.Response objects
All fields in response structs are ordinary value types (not pointers or wrappers). Response structs also include a specialJSON field containing metadata about
each property.
.Valid() method on the JSON field.
.Valid() returns true if a field is not null, not present, or couldn’t be marshaled.
If .Valid() is false, the corresponding field will simply be its zero value.
.JSON structs also include an ExtraFields map containing
any properties in the json response that were not specified
in the struct. This can be useful for API features not yet
present in the SDK.
Response Unions
In responses, unions are represented by a flattened struct containing all possible fields from each of the object variants. To convert it to a variant use the.AsFooVariant() method or the .AsAny() method if present.
If a response value union contains primitive values, primitive fields will be alongside
the properties but prefixed with Of and feature the tag json:"...,inline".
RequestOptions
This library uses the functional options pattern. Functions defined in theoption package return a RequestOption, which is a closure that mutates a
RequestConfig. These options can be supplied to the client or at individual
requests. For example:
option.WithDebugLog(nil) may be helpful while debugging.
See the full list of request options.
Errors
When the API returns a non-success status code, we return an error with type*stagehand.Error. This contains the StatusCode, *http.Request, and
*http.Response values of the request, as well as the JSON of the error body
(much like other response objects in the SDK).
To handle errors, we recommend that you use the errors.As pattern:
*url.Error wrapping *net.OpError.
Timeouts
Requests do not time out by default; use context to configure a timeout for a request lifecycle. Note that if a request is retried, the context timeout does not start over. To set a per-retry timeout, useoption.WithRequestTimeout().
Retries
Certain errors will be automatically retried 2 times by default, with a short exponential backoff. We retry by default all connection errors, 408 Request Timeout, 409 Conflict, 429 Rate Limit, and >=500 Internal errors. You can use theWithMaxRetries option to configure or disable this:
Accessing raw response data (e.g. response headers)
You can access the raw HTTP response data by using theoption.WithResponseInto() request option. This is useful when
you need to examine response headers, status codes, or other details.
Making custom/undocumented requests
This library is typed for convenient access to the documented API. If you need to access undocumented endpoints, params, or response properties, the library can still be used.Undocumented endpoints
To make requests to undocumented endpoints, you can useclient.Get, client.Post, and other HTTP verbs.
RequestOptions on the client, such as retries, will be respected when making these requests.
Undocumented request params
To make requests using undocumented parameters, you may use either theoption.WithQuerySet()
or the option.WithJSONSet() methods.
Undocumented response properties
To access undocumented response properties, you may either access the raw JSON of the response as a string withresult.JSON.RawJSON(), or get the raw JSON of a particular field on the result with
result.JSON.Foo.Raw().
Any fields that are not present on the response struct will be saved and can be accessed by result.JSON.ExtraFields() which returns the extra fields as a map[string]Field.
Middleware
We provideoption.WithMiddleware which applies the given
middleware to requests.
option.WithMiddleware is given
multiple times, for example first in the client then the method, the
middleware in the client will run first and the middleware given in the method
will run next.
You may also replace the default http.Client with
option.WithHTTPClient(client). Only one http client is
accepted (this overwrites any previous client) and receives requests after any
middleware has been applied.
Semantic versioning
This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:- Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
- Changes that we do not expect to impact the vast majority of users in practice.

