HTTP 429).requests to >=2.0.0 to prevent pulling in versions with known vulnerabilities.TokenManagerBase now uses a lock with double-checked locking so the initial token is fetched exactly once, and a new refresh_auth_token(used_token) deduplicates concurrent renewals by only fetching when the stale token still matches the cached one.HTTPTransport now prepares and authenticates requests in request(), so the new send_request(request_data) receives an already-prepared HttpRequest and acts as a pure I/O primitive, simplifying subclassing.HTTPTransport.send(endpoint) is deprecated in favour of send_request(request_data); the legacy method still works for backward compatibility, but will be removed in 3.0.TokenManagerBase.invalidate_expired_token() and handle_invalid_token() (and the TokenState.EXPIRED value) are deprecated and will be removed in 3.0, as token renewal now goes through refresh_auth_token().BaseModelConfiguration classes into three shared base classes in sinch.core.models.internal (BaseConfigModel, SnakeCaseExtrasModel, CamelCaseDumpModel).create, list, get, update, replace, delete, and list_members operations, with full model, endpoint, and unit test coverage (see MIGRATION_GUIDE.md).get and list operations, with full model, endpoint, and unit test coverage (see MIGRATION_GUIDE.md).MOTextSinchEvent, MOBinarySinchEvent, MOMediaSinchEvent, MediaBody, and MediaItem removed from sinch_events; use InboundMessage (and its variants) from sinch.domains.sms.models.v1.types instead (see MIGRATION_GUIDE.md).NumberSinchEvent synchronized with the Numbers OAS spec: new internal_failure_code field, additional status values (IN_REVIEW, BLOCKED, COMPLETED, REJECTED, EXPIRED), a new NUMBER_ORDER_PROCESSING event type, and corrected event type DEPROVISIONING_FROM_VOICE_PLATFORM (previously DEPROVISIONING_TO_VOICE_PLATFORM).Meeting Developer needs are important to Sinch. You have an opportunity to provide your honest feedback about your experience onboarding and using our SDK's through a short survey.T
There are fewer than 10 questions and the survey shouldn't take more than a few minutes to complete. All answers are anonymous unless you choose to add your name, email address and company name at the end of the survey.
Our goal is to provide an easy and frictionless experience. Thank you in advance for your time and feedback!
Access the link to complete the survey: Developer Feedback Survey