Admin and regional API differences
Admin API
Calling admin API
The URL, systemKey, and token this endpoint requires are obtained differently than others. To get those, do the following:
Click the Select project drop-down at the top of the IoT Core UI.
Click the Edit icon (pencil) next to the desired project.
Go to the SERVICE ACCOUNTS tab.
If a service account already exists, select it and choose DOWNLOAD CREDENTIALS. If a service account does not exist, create it and select DOWNLOAD CREDENTIALS.
A JSON file will be downloaded to your local machine. Open the file with an editor. Use the systemKey, token, and URL from the file as needed below.
Admin APIs
projects.locations.registries
policy
miscellaneous
Regional API
Calling regional API
You can find the URL, SystemKey, and token required in the call by clicking API Keys (key icon) at the top-right of the Registry Details page:

The URL, System Key and Token* for calling Regional APIs are found in the Registry API Keys section:

Regional APIs
projects.locations.registries
projects.locations.registries.devices
projects.locations.registries.devices.configVersions
projects.locations.registries.devices.states
projects.locations.registries.devices: cloudiotdevice
*The marked APIs are ones called by devices rather than users. For those, note the following:
In IoT Core Enterprise the token shown under API Keys CANNOT be used to call those APIs. Instead, the value of the ClearBlade-UserToken header MUST be a JWT generated as shown here. Pay attention to the claims required for HTTP calls when generating the JWT.
In IoT Core Standard the value of the ClearBlade-UserToken header can EITHER be the JWT or the token found under API Keys. The JWT is recommended for security.