Skip to main content

February 2026 Update – The Integrators

Navigatr February 2026 release: Personal Access Tokens for API auth, marketing consent for learners, analytics improvements, and bug fixes for integrators.

Written by Support Desk
Updated this week

This update introduces Personal Access Tokens for API authentication and marketing consent controls for learners.


Key Features

Personal Access Tokens

API users and integrators can now generate Personal Access Tokens (PATs) to authenticate with the Navigatr API. PATs replace the previous username/password Bearer token approach. Unlike the previous method, PATs do not expire and require no refresh logic — once generated, a token works until you revoke it. Account holders can also generate tokens for personal API access.

How to access: User Settings → Personal Access Token. For a step-by-step guide, see Personal Access Tokens for API and Integrations.


Marketing Consent

A marketing consent option is now available during registration and in account settings, giving learners control over whether they receive marketing communications.

How to access: User Settings → Email & Communications


Changes

  • Analytics engagement tab labels updated for consistency

  • Analytics charts reordered for improved visual hierarchy

  • The select-all checkbox in list views is disabled until content has fully loaded, preventing premature selection

  • The “see all following” link on badge pages now navigates to the correct destination

  • Print layouts updated with improved page-break handling


Bug Fixes

  • Activity turnout rates displaying incorrect figures

  • Analytics date labels not reflecting the correct timezone

  • Duplicate element IDs in analytics pages causing rendering inconsistencies

  • Analytics date range validation now returns specific error messages instead of a generic failure

  • Badge claim failing silently when no recipient identifier was provided

  • Public badge lists now load correctly for unauthenticated visitors


API & Compliance

  • Personal Access Tokens are now the primary authentication method for the API.

  • 401 and 403 status codes are now returned consistently across all endpoints — 401 for unauthenticated requests, 403 for unauthorised ones

  • New url field added to pathway, activity, provider, and community resources

  • Error response schemas added to all endpoints


What This Means for You

  • API users and integrators – You can now authenticate with a Personal Access Token instead of username and password. Create and manage named, revocable tokens from User Settings → Personal Access Token. See Personal Access Tokens for API and Integrations to get started.

  • Learners – You now have control over marketing communications. Your preference can be set during registration or updated at any time from User Settings → Email & Communications.

  • Community admins – Analytics labels and chart ordering have been updated for clarity. The select-all checkbox in list views now waits until content is fully loaded before becoming active.


Need Help?

If you have any questions about this release or need assistance with Personal Access Tokens, please contact us at [email protected].

Did this answer your question?