Authentication
the ingest api typically uses a two tier token authentication model, access is controlled through two token types api key (long lived) a persistent credential and is used solely to request short lived access tokens api keys should be stored securely and never exposed in client side code access token (short lived) a temporary bearer token obtained by authenticating with your api key this token is included in the authorization header of all subsequent api requests access tokens have a configurable expiry time, after which a new token must be requested using your api key additionally, specifically scoped (to event level or ingest api levels are available) authentication flow call the token endpoint with your api key to obtain an access token include the access token as a bearer token in all api requests when the access token expires, request a new one using your api key authorization bearer \<access token> endpoint /updates/api/auth headers the following headers should be included in every request accept application/json content type application/json authorization bearer \<access token> example request request post /updates/api/auth authorization bearer eyjh(long lived token)} content type application/json accept application/json response { 	"success" true, 	"data" "ey " }