Authentication

the eai supports two authentication methods both are fully supported — choose the method that best fits your integration architecture oauth2 bearer token use the oauth2 client credentials grant to obtain a time limited access token step 1 request a token call the token endpoint with http basic auth using your eai username and client secret curl x post https //yourcompany teleskope io/eai/oauth2/token php \\ u "your username\ your client secret" \\ h "content type application/x www form urlencoded" \\ d "scope=graph" scope values graph — access to the graph api endpoints uploader — access to the uploader endpoint step 2 use the token include the token in subsequent requests via the authorization header curl x get "https //yourcompany teleskope io/eai/graph php?listzonesofapptype=affinities" \\ h "authorization bearer eyjhbgcioiji " token response { "access token" "eyjhbgcioiji ", "token type" "bearer", "expires in" 86400, "scope" "graph" } token limits tokens expire after 24 hours (86,400 seconds) a maximum of 10 active tokens are allowed per account when the limit is reached, you must wait for existing tokens to expire before generating new ones http basic auth send your eai username and password directly via http basic auth on each request no token management is required curl x get "https //yourcompany teleskope io/eai/graph php?listzonesofapptype=affinities" \\ u "your username\ your password" obtaining credentials eai credentials (username and password/client secret) are provisioned by your teleskope account manager each eai account is scoped to a specific module (graph or uploader) and company tenant important do not share credentials across environments or systems store credentials securely (e g , in a secrets manager or environment variables) rotate credentials periodically through your account manager