Getting Started

prerequisites before using the eai, you will need an active teleskope tenant with a company subdomain (e g , yourcompany teleskope io ) eai credentials (username and password/client secret) provisioned by your teleskope account manager setup steps obtain credentials — contact your teleskope account manager to request eai credentials for your tenant configure permissions — your account manager will set up the appropriate permissions for the endpoints you need access to optionally configure ip whitelisting — restrict api access to specific ip addresses or cidr ranges for additional security authenticate — use either oauth2 bearer tokens or http basic auth to authenticate your requests start integrating — call the api endpoints as documented in the api reference base url all endpoints are accessed via your company subdomain https //{subdomain} teleskope io/1/eai/ replace {subdomain} with your organization's teleskope subdomain (provided by your account manager) endpoint routing (graph api) the graph api uses query parameter based routing each operation is triggered by a specific query parameter on /1/eai/graph php for example, to list zones get https //yourcompany teleskope io/1/eai/graph php?listzonesofapptype=affinities response format all graph api endpoints return json with a consistent structure { "status" true, "message" "description of result", "data" \[ ] } field type description status boolean true for successful requests, false for errors message string human readable description of the result data array or object response payload, or null on error id encoding all resource ids returned by the api are encoded you must use the encoded ids exactly as returned when passing them as parameters to other endpoints never attempt to decode or construct ids manually