REST and webhooks

Your product decides when a session exists. Vasl exposes that as a REST API and as webhooks. The server starts the stream when your app says so.

​

What you call

• Create a stream for a session your product already knows
• Rotate publish and play keys
• Hear a webhook when a recording is finished

Keys are the same JWTs described in Security. A short lifetime is the default shape: the key covers the appointment, then it stops working.

​

What you still wire yourself

The API reference, with paths and payloads, lands here when the contract is frozen. Until that page exists, build against the interface you received with the license, and ask contact@vasl.sh when a call does not match what you were given.