Regenerated on the latest Fern toolchain — Fern CLI 0.83.0 → 5.58.0 and the fern-typescript-node-sdk generator 3.64.1 → 3.73.4. The HTTP API surface (endpoints, request/response schemas) is unchanged; openapi.json changes are limited to info metadata and the auth security scheme (now modeled as an API key).
Renamed (breaking)
- The root client and its companion exports drop the
Apiinfix (via the generator'snaming.namespaceconfig):LatitudeApiClient→LatitudeClient,LatitudeApiError→LatitudeError,LatitudeApiTimeoutError→LatitudeTimeoutError,LatitudeApiEnvironment→LatitudeEnvironment, and the wildcard namespace exportLatitudeApi→Latitude(import * as LatitudeApi→import * as Latitude). Update imports andnew LatitudeApiClient(...)tonew LatitudeClient(...). - The client auth option is renamed
token→apiKey(the credential is an organization-scoped API key, sent asAuthorization: Bearer <key>). Updatenew LatitudeClient({ token })tonew LatitudeClient({ apiKey }).
Removed (breaking)
- Some standalone query-parameter enum types are no longer exported as named types — they're now inlined as literal unions. Affected names include
DatasetsListRequestSortBy/SortDirection,DatasetsListColumnsRequestIncludeRemoved,DatasetsListRowsRequestSortDirection,IncidentsListRequestSeveritiesItem/SourceType,SavedSearchesListTracesRequestSortBy/SortDirection,SignalsListRequestLifecycleGroup/SortBy/SortDirection, theTools*Request*andUsers*Request*parameter enums, andFilterConditionValueItem. If you imported any by name, use the literal value inline instead.
Added
- The
apiKeyoption now falls back to theLATITUDE_API_KEYenvironment variable when omitted (via the OpenAPI spec'sx-fern-bearerextension), sonew LatitudeClient()works when that env var is set. An explicitly passedapiKeytakes precedence. - The generator emits additional fine-grained union-member/enum types and some internal module restructuring. No new endpoints or methods.