sinch.core.clients.sinch_client_sync module

class sinch.core.clients.sinch_client_sync.SinchClient(
key_id: str = None,
key_secret: str = None,
project_id: str = None,
logger_name: str = None,
logger: Logger = None,
service_plan_id: str = None,
sms_api_token: str = None,
sms_region: str = None,
conversation_region: str = None,
voice_region: VoiceRegionEnum | str = VoiceRegionEnum.GLOBAL,
transform_kwargs_casing: bool = True,
retry_configuration: RetryConfiguration = None,
)[source]

Bases: object

Synchronous implementation of the Sinch Client By default this implementation uses HTTPTransportRequests based on Requests library Custom Sync HTTPTransport implementation can be provided via transport argument

Parameters:

  • transform_kwargs_casing (bool) –

    When True (default), extra fields on request/response models are auto-converted to the api convention snake_case or camelCase, same as before 2.2.0. When False, extra fields pass through unchanged in both directions.

    Deprecated since version 2.2: This flag is transitional and will be removed in 3.0, when extra fields will always pass through unchanged.

  • key_id (str)

  • key_secret (str)

  • project_id (str)

  • logger_name (str)

  • logger (Logger)

  • service_plan_id (str)

  • sms_api_token (str)

  • sms_region (str)

  • conversation_region (str)

  • voice_region (VoiceRegionEnum | str)

  • retry_configuration (RetryConfiguration)