Developer Portal
InsightsPurpleTRACMTIPodium
Other
Other
  • Weather
InsightsPurpleTRACMTIPodium
Other
Other
  • Weather
  1. Weather
  • Overview
  • Weather Authentication
  • Numerical Weather Prediction
  • Weather Parameters
  • Numerical Weather Prediction
    • Data at a point
      POST
    • Get Weather Parameter Details
      GET
    • Grid data as CSV
      GET
  • Schemas
    • GridCsvRequestBody
    • CoordinateSchema
    • DataAtAPointRequestBody
    • DataAtAPointResponseBody
    • GetWeatherParamsResponseBody
    • ParamValueSchema
    • PositionSchema
    • WeatherParams
  1. Weather

Weather Authentication

The numerical weather service takes a bearer token. You exchange client credentials for one, then send it on every call. This is the scheme the service launched with, and it will move to the Insights api-key header alongside the host migration in the future.

Getting a token#

Post your credentials as multipart/form-data. Your representative issues the client_id and client_secret by secure email.
FieldValue
client_idIssued to you
client_secretIssued to you
grant_typeclient_credentials
scoperead:weather
The response carries access_token, token_type, scope and expires_in.
The token endpoint is not under the weather path
Forecast calls go to https://aviso-api.stratumfive.com/api/numericalweather/, and the token call goes to https://aviso-api.stratumfive.com/api/identity/connect/token. The identity service sits beside the weather service, not inside it.

Using it#

How long it lasts#

expires_in comes back as 3600, so a token is good for one hour. No refresh token is issued: request a new one from the same endpoint when the old one runs out.
Cache until expiry
Requesting a token per call works and wastes a round trip on every forecast. Hold it for the hour, and a 401 narrows to the credentials.

Reading an error#

StatusMeansDo
400 on the token endpointThe client credentials were rejectedCheck client_id and client_secret
401 on a forecast callThe token is missing, malformed or past its hourRequest a new token and retry

The same credentials do not reach Podium#

Podium Metric I/O uses the same identity service and the same grant type. The scope differs, and so does the credential pair: your representative issues one pair per surface, and a token issued for one will not work on the other.
SurfaceScope
Weatherread:weather
Podium Metric I/Oextract-by-imo:metrics

Related#

Numerical Weather Prediction
The endpoints this token unlocks.
Weather
What the category covers.
Authentication
Every scheme in the portfolio.
Modified at 2026-10-02 12:30:32
Previous
Overview
Next
Numerical Weather Prediction
Built with