Authorization

There are two levels of authorization: team-based via api-key and user-based temporary access-key. To create a room and to register webhooks (for any rooms) you have to provide a team-based authorization sending the API key in the HTTP header.

https://api.eyeson.team/<path>
HEADERS:
  - Authorization: <YOUR_API_KEY>

Any other communication with the API requires user-based authorization. Meaning: an active room and user identified by an access_key. The access key is provided by the resource endpoint, no additional headers are needed.

An expired access key - meeting has been shutdown - will result in a HTTP response code of 410 GONE for any request that uses the access key for authorization.