All HTTP endpoints require authentication using a webtask token. The webtask token can be provided either using the Authorization request header, or via the key URL query parameter. Using the Authorization header is recommended as this prevents certain cases where your token can be cached by intermediate HTTP processors.

Unauthenticated requests will result in 403 responses.

Webtask token can be presented with the Authorization: Bearer {token} HTTP request header.

Webtask token can also be presented with the key={token} URL query parameter