Skip to main content

Calling the System One API

Choosing a model

Inspect the available models:
Select the model when constructing a client:
See the Models resource reference for details.

Retries

Pass a custom RetryPolicy as retry on the client or per call.

Error handling

Handle exceptions raised by the SDK:

Logging

The SDK logs to the typesafe_sdk logger. Configure it according to standard logging guide:
Or set TYPESAFE_LOG_LEVEL to one of debug, info, warning, error, or off before importing the SDK. info logs one summary line per request; debug also logs request and response headers and bodies. Secret headers — authorization, API keys, cookies, and any header whose name contains token or secret — are redacted from log output. Request and response bodies are not redacted.

Environment variables

The SDK reads and uses the following environment variables: See the constants reference for SDK defaults.

Forward compatibility

The SDK keeps working as the TypeSafe API evolves, so you can adopt new API features before an SDK release adds first-class support for them.

Extra request fields

Send request fields this SDK version predates with extra_body:

Raw question dictionaries

Pass a question as a plain dictionary to include fields this SDK version does not model yet:

Unknown answer kinds

The SDK logs a warning and skips unrecognized answer kinds. Use raw_http_response to inspect the complete API response, including those answers:

Unknown response fields

Unknown extra fields on recognized responses are ignored.