Connect Library 5.0.0 and Attachment Receiver 5.0.0 are now available at  https://github.com/tsanetgit/Connect_SDK/releases/tag/v5.0.0

New features include:

• End-to-end encryption (optional): the new connect-e2ee module encrypts and signs cases and notes at the member’s connector, and the platform holds no keys.
• V2 attachments: the client now follows the grant model in the Connect API spec, including multipart uploads to S3 and Azure. The V2 attachment endpoints are still marked alpha in the spec.
• Attachment controls: senders can restrict which companies receive their attachments, and receivers can configure their own S3 or Azure Blob storage.
• Server-defined note types: notes now use the types the server offers, and carry their type, company and direction when read.
• Clearer API errors: /v1/ failures now return problem details with the documented 4xx status.
• Safer diagnostics: credentials, tokens and partner-written text are redacted from SDK records’ toString() output.
• Resource cleanup: sessions can now be closed to release their connections.

End to End Encryption

TSANet Connect will add true end-to-end encryption for selected integrated member relationships so that case-specific content is encrypted in the sender’s environment and is decrypted only in the receiving member’s environment and in the sending member’s own environment.  E2EE uses established JOSE standards: the sender encrypts each protected field for the receiving member and for itself and signs a single manifest that binds the encrypted fields to the case, the sending member, and the profile version. Public keys are discoverable through member-controlled JWKS endpoints.

Move V2 attachments with confidence

The rebuilt V2 attachment client follows the grant model in the Connect OpenAPI specification. The result is a clearer, spec-aligned workflow from grant creation through upload and completion. Teams can use dedicated operations such as createGrant, singleUploadLink, s3PartLinks, azureBlockLinks, the mode-specific completion calls, and abandon—or choose convenience methods for upload, mode-aware complete, and send.

Get clearer API failures

Connect SDK 3.0.0 brings consistent problem-detail responses to failed /v1/ calls. Instead of frequently surfacing a generic 500, the library now carries the documented 4xx status together with type(), title(), and actionable detail. That means faster diagnosis, more reliable automation, and fewer ambiguous integration errors.

Turn case notes into smarter workflows

Server-defined note types give connected systems a shared vocabulary for routing, automation, and reporting. Clients can discover the codes available to them, send the appropriate code without translation, and read richer context on every note.

• Discover available types: listNoteTypes() returns the codes the client may send from GET /v1/note-types.
• Create with precision: createNote(…, type) sends the supplied code unchanged; unsupported codes receive 400 invalid-note-type.
• Stay flexible: a null type creates a note without a type.
• Gain more context: returned notes now include type, typeDisplayName, companyId, and direction.

Ready to build?

Learn more about this SDK and how to build integrations at the Developer Hub: https://developer.tsanet.org