I am trying to figure out where to setup my vendor token - sometimes it works on the command line but not all the time.
Heads up, your vendor token will be useful for interacting with Exosite’s Provisioning API, but it will not be treated and valid authentication by the RPC API.
If you want to change the state of serial numbers, or modify the client models your account owns, then the vendor token is the authentication to use.
I also cannot find documentation for the .exolinerc file format - otherwise where do I put my credentials?
I am not sure if the file format for the Windows .exolinerc need be different than the OSX or Linux .exoline config files. I’ll need to take some time to figure out what needs to be done here.
However, what do I do if I want to get a list of CIKs from my portal?
Without already having procured a parent CIK, the easiest way to do this is to use the Portals API. This way you can you your Portals admin credentials to get information about One Platform clients.
For Example, you can get the CIK of a portal and a list of its aliased children using the Get-portal endpoint. This way you will be able to exchange your Portals credentials for a CIK that can be used to authenticate RPC API requests.
Finding a portal’s ID in Portals can be tricky at first. You can always find the ID of a portal using the Portals API, your domain’s /admin/portallist(if you have admin access) page, or by loading the portal in your browser.
For clarity, there are two different services that your Exosite based business application is running on. Your devices typically talk to Exosite’s One Platform, while what you interact with in your Browser is a web application called Portals. This is called the Portals/One Platform stack. Each have their own APIs and different goals they mean to accomplish. It is possible to use a single API to get things done in Exosite, but you may find tasks easier by being familiar with both.
One important feature is that you do not need to posses the CIK of each and every ‘thing’ in your One Platform hierarchy. If you posses a parent CIK, you have permission to read, write, and edit each resource that the client owns, and each resource that each child owns – ad infinitum.
For details on how to use the RPC API to do this you will want to look at the following sections of documentation:
A short guide on which API to use:
Want to interact with a device and its data? Reading/Writing/Editing – Use the RPC API.
Doing an operation often or desire the best performance? Use the RPC API.
Want to interact with a user, portal, or dashboard? Use the Portals API.
Additional helpful links on Portals and the One Platform.
Start of theOne Platform Reference
Articles on the Portals and One Platform stack
Hopefully this helps,