Base URLs and Environments

base urls and environments each product has its own host and url conventions the most common cause of "my call returns 404" is hitting the wrong base url or prefix litmus edge single base url, multiple module paths module path prefix protocol auth /auth/v3/ rest devicehub /devicehub/v2 (graphql) and /devicehub/ (rest) graphql + rest digital twins /digitaltwins/v2 graphql datahub /datahub/ rest flows manager /flows/ rest analytics /analytics/ rest applications /apps/ rest integration /cc/v2 graphql opc ua /opcua/v2 graphql system / device management /dm/ rest in postman / environment files this is {{edgeurl}} litmus edge manager lem has three distinct host/path prefixes prefix used by roughly auth header {{lem url}}/api/v1/ main fleet api (projects, devices, alerts, backups, marketplace deploy) 158 endpoints x authtoken {{lem adminurl}}/admin/v1/ admin console (companies, users, lem level backups, instance alerts) 144 endpoints x authtoken {{lem url}}/mpcs/ marketplace catalog management 13 endpoints authorization (no bearer prefix) {{lem adminurl}} typically points to port 8446 on the lem host confirm with your admin common lem url variables variable frequency notes {{project id}} 99 lem project the device belongs to {{edge device id}} 48 target edge device {{company name}} 13 company (admin/v1 calls) {{marketplace catalog id}} 11 catalog under /mpcs/ {{marketplace catalog application id}} 10 app in a marketplace catalog litmus uns uns is graphql only all operations target a single endpoint post {{uns url}}/mqtt/gql the documented sections (dashboard / uns / security / mqtt / integrations / tools) are organizational groupings every request hits /mqtt/gql with a different graphql operation there is no rest surface environment file template for postman / scripts edgeurl = https //\<your edge host> lem url = https //\<your lem host> lem adminurl = https //\<your lem host> 8446 uns url = https //\<your uns host> client id = \<le client id> client secret = \<le client secret> lem adminapitoken = \<lem admin token>