If you see 403 errors from your Track PMS integration, this does not automatically mean your API credentials have expired or been revoked.
Why this happens. When credentials are actually invalid, every sync request fails and your property data stops updating entirely. If only specific requests return 403 errors while your properties continue to sync and update successfully, the cause is usually a per-resource permission problem rather than a credential failure. For example, Track may return a 403 for a specific unit it marks as unavailable, or for a particular data endpoint that requires additional permissions on that listing.
What this means for you. In these cases, the integration is still working correctly and no credential update is needed. Support checks the specific error details and your sync status to confirm the actual cause before recommending any action.