Members and Technology Partners looking to automate multi-vendor support now have a central engineering home: the TSANet Connect Developer Hub. Built and maintained by TSANet, it brings together connectors, gateways, the REST API and the platform’s design documents to help teams integrate support collaboration into the systems they already use.
Whether you’re building an integration, installing a connector or building something of your own, the hub brings the guidance and tools together—and makes clear what is available today, what requires onboarding and what is still taking shape.
Tools for Building Integrations
The hub collects the resources you need throughout development. Each entry explains what the tool is for, how to get it and what access it requires.
Environments, Reference and Postman
Begin development in the Beta test environment. Request a Beta account and credentials from membership@tsanet.org. If your integration uses OAuth client credentials, TSANet must also provision the service principal—the application identity used for authentication—before you can use those credentials.
The Connect API reference supplies request and response schemas, parameters and status codes, while the Postman collection gives you requests to exercise against Beta.
SDK, console and demo
Alongside the Java library reference and upgrade guidance, the hub describes the Console App and Web Demo. The console provides commands for collaboration lifecycle actions, attachments and webhooks. Its source is public, but building it requires access to the private specification; a built jar is available from TSANet at onboarding.
The Web Demo showcases SDK workflows, including partner search, live partner forms and webhook management.
Test suites and agent skills
Gateway adapter developers can access the Gateway Conformance Harness through onboarding. It exercises failure modes such as timeouts, ambiguous submissions and duplicate inbound deliveries. Run it from the start of development, not only at the end.
TSANet’s Connector Test Harness remains internal. For members, Beta with test-flagged submissions is the available test bed, with failing connector cases routed to the relevant issue tracker.
The hub also documents assistant-ready skills. Agentic Usage with TSANet Connect explains what each skill includes and how to load it. The hub’s own question-answering assistant will be added in the future.
Community Discussions
Join the Organization Discussions on GitHub, a single discussion space shared by every TSANet repository. There is no separate discussion platform or additional platform-specific account. Choose the category that matches your question or contribution.
Q&A: Ask an implementation question – Auth, process forms, lifecycle transitions, webhook delivery
Troubleshooting: Something isn’t working, Silent failures, signature mismatches, sync that stopped
Show and tell: Share what you built, Custom integrations, translation services, platform findings
Technology Committee: Propose a change to the API, Gaps, paper cuts, roadmap input, and behavior that surprised you
Wish List: Which connector next? Tell us the platform your team runs on
Membership: Early access & onboarding, Credentials, pilot instances, connector early-access programs