Why is my carrier's HOS data returning a 403 "insufficient_scope" error?
Resolve HOS permission errors caused by missing TSP account scopes.
This error on the HOS endpoints (hos_logs, hos_availabilities, etc.) means the API token used when the carrier connected does not have the scopes needed to read HOS data. This is similar to the Isaac issue above but can occur with other TSPs too.
The carrier needs to reconnect using a TSP account that has the required permissions. Simply re-entering the same credentials will not help if the underlying account lacks the right scopes. The carrier should work with their TSP administrator to ensure the account has appropriate access before reconnecting.