Overview
PulseGrid is not limited to Node.js and Python. The platform is built on HTTP and WebSocket protocols, so other server languages can integrate without waiting for a dedicated package.
Current status:
- JavaScript / TypeScript: official SDK
- Python: official SDK
- Go, Java, C#, PHP, Ruby, Dart/Flutter and others: protocol integration today; dedicated SDKs may be added later
This distinction keeps the documentation honest while leaving the platform open to any language with HTTPS and WebSocket support.
Setup
Trusted server operations:
1. Send HTTPS requests to the PulseGrid API.
2. Include X-PulseGrid-Public-Key and X-PulseGrid-Secret-Key.
3. Include project_id where required.
4. Parse the JSON response and handle non-2xx errors.
Realtime client operations:
1. Have a trusted backend create a short-lived client token.
2. Open the project's channel WebSocket using that token.
3. Send JSON with event, data and meta.
4. Handle event, presence and pong messages.
Never place the project secret inside Flutter, mobile, desktop or browser code distributed to end users.
Code example
POST https://www.altrancconnect.com/api/client-tokens/create/
Content-Type: application/json
X-PulseGrid-Public-Key: pk_...
X-PulseGrid-Secret-Key: sk_...
{
"project_id": "YOUR_PROJECT_UUID",
"identifier_id": "user_123",
"identifier_label": "Customer 123",
"allowed_channels": ["support"],
"expires_in": 3600
}
Realtime URL after receiving a client token:
wss://www.altrancconnect.com/ws/channels/<project-id>/<channel-slug>/?token=<client-token>
Example WebSocket event:
{
"event": "message",
"data": {"text": "Hello"},
"meta": {"source": "custom_client"}
}Notes
Raw protocol support does not mean every language-specific edge case has been tested by the PulseGrid team. Use normal production practices for timeouts, retries, TLS, JSON validation and reconnect handling.
When a dedicated SDK is released for another language, prefer it because it can standardize errors, retries, heartbeat and authentication handling.