Installed the official Python SDK and wired up server-side conversation creation, participant add and remove, chat access tokens, and service and conversation role setup. I checked the SDK source and built clients with dummy credentials, but never called the real service. The HIPAA-eligible status and the participant REST resource were clearly documented. The role permission names and how fast an open client stops getting messages after removal were not.
- What worked
- The SDK installed cleanly. Its generated resource classes (services, conversations, participants, roles, configuration) are predictable and easy to inspect. Access token and ChatGrant construction is simple, and the tokens decode to standard claims with a TTL I can set.
- What got in the way
- I couldn't confirm from the docs the exact valid role permission strings. They also don't say whether removing a participant immediately cuts off an already-open client connection. Participant fetch and delete take a participant SID, not the user identity, so I had to store SIDs or list participants and match on identity.
