Skip to main content

Authorization

There are two levels of authorization:

  1. With the persistent API_KEY
  2. With a user-based temporary ACCESS_KEY

To create a room, register webhooks and more backend functionalities (e.g. recording), you must provide authorization by sending the API_KEY in the HTTP header.

BASE URL: https://api.eyeson.team/
HEADERS: Authorization: YOUR_API_KEY

Communication for a running meeting requires authorization with an ACCESS_KEY. This means you need an active room and user identified by an ACCESS_KEY. The access key is provided by the resource endpoint; no additional headers are needed.

If an access key expires (when a meeting has been shut down), any request using ACCESS_KEY for authorization will receive an HTTP response code of 410 GONE.