We’ve just rebranded and updated the Tempest API docs:
The most significant change is a shift from the “API key” concept to the “access token” concept for authentication. The API key concept still exists, but only for Enterprise apps (which are a tiny minority of all apps) - the vast majority of apps out there do not need an API key.
The preferred authentication approach for third-party apps is Oauth2, which is now publicly documented here with the personal access token as an option for apps that can’t support Oauth2. The “developer API key” will continue to operate through the end of 2020, but if you are using it, please migrate to one of the “access token” methods as soon as possible.
The Remote Data Access Policy has been updated a bit as well, and includes a description of how forecast data fits in with that policy. The forecast API endpoints have not been documented yet, but that is coming soon.