For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Overview
    • Introduction
    • How it works
    • Quickstart
    • Customer showcase
  • Working with SDKs
    • Project structure
    • Adding custom code
    • Migrating to Replay
    • Capabilities
  • Generators
      • Generating an SDK
      • Publishing to PyPI
      • Configuration
      • Adding custom code
      • Dynamic authentication
      • aiohttp support
      • Changelog
      • Customer showcase
  • Reference
    • generators.yml
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
GeneratorsPython

Changelog

February 10, 2026
February 10, 2026
Was this page helpful?
Edit this page
Previous

February 11, 2026

Next

February 9, 2026

4.58.0

(feat): Add support for logging to the generated SDK. Users can configure the logger by passing in a logging parameter to the client constructor.

1from acme import AcmeClient
2from acme.core import ConsoleLogger
3
4client = AcmeClient(
5 token="YOUR_TOKEN",
6 logging={
7 "level": "debug", # "info" is the default
8 "logger": ConsoleLogger(), # ConsoleLogger is the default
9 "silent": False, # True is the default, set to False to enable logging
10 }
11)

The logging parameter accepts a LogConfig dict with the following properties:

  • level: The log level to use. Defaults to "info".
  • logger: The logger to use. Defaults to ConsoleLogger.
  • silent: Whether to silence the logger. Defaults to True.

The level property can be one of the following values:

  • "debug"
  • "info"
  • "warn"
  • "error"

To provide a custom logger, pass an object implementing the ILogger protocol with debug, info, warn, and error methods.

Sensitive headers (authorization, x-api-key, cookie, etc.) are automatically redacted in logs.