Developer Portal
InsightsPurpleTRACMTIPodium
Other
Other
  • Weather
InsightsPurpleTRACMTIPodium
Other
Other
  • Weather
  1. Podium
  • Overview
  • Podium Authentication
  • Podium Metric I/O
  • Extract Timeline Fields
    POST
  • Timeline Info for All
    GET
  • Timeline Info by IMO
    GET
  • Schemas
    • GlueExtractResponseBody
    • TimelineInfoAllResponseBody
    • TimelineInfoByIMOResponseBody
  1. Podium

Podium Authentication

Podium exchanges client credentials for a bearer token, which you then send on every call. An Insights API key does not work here.
This scheme predates the api-key header Insights uses. We are migrating everything to API keys.

Getting a token#

Post your client credentials as multipart/form-data to the identity service. Your representative issues the client_id and client_secret by secure email.
FieldValue
client_idIssued to you
client_secretIssued to you
grant_typeclient_credentials
scopeextract-by-imo:metrics
The response carries access_token, token_type, scope and expires_in.

Using it#

Send the token as a bearer token on every call.

How long it lasts#

expires_in comes back as 3600, so a token is good for one hour. There is no refresh token: when one expires, request another from the same endpoint with the same credentials.
Request a token on expiry, not on every call
The identity service issues a fresh token each time you ask. Cache the one you hold until expires_in runs out, and a 401 then points at the credentials instead of the clock.

Reading a 401#

A 401 means the credential was missing, malformed or expired.
CheckWhy
Whether the token is older than an hourTokens expire on the hour and there is no refresh token. Request a new one and retry before looking anywhere else
Whether scope was extract-by-imo:metricsA token issued on a different scope authenticates and then fails authorisation
A 400 from the token endpoint means the client credentials were rejected. Check the client_id and client_secret rather than the scope.

How this compares with the rest of the portfolio#

ProductSchemeWhere it goes
InsightsAPI keyapi-key header
WeatherOAuth 2.0 Token (1 hour)Legacy
PodiumOAuth 2.0 Token (1 hour)Legacy
PurpleTRACUsername and API keyQuery string
MTIOAuth 2.0 client credentialsAuthorization: Bearer header
We inherited these schemes and we are migrating all of them to API keys. Authentication holds the current matrix.

Related#

Podium
What the Podium surface covers and where it sits.
Podium Metric I/O
The endpoints this token unlocks.
Vessel & Voyage
The rest of the category this sits in.
Modified at 2026-10-02 08:42:17
Previous
Overview
Next
Podium Metric I/O
Built with