We are developing a Geotab Add-In where certain vehicle data is processed externally, and the prediction results are then fetched from an external system but displayed inside the Add-In. Since this requires authenticated API calls, what is the recommended best practice in the Geotab ecosystem for authentication?Should an Add-In rely on API keys or implement OAuth2 for secure access?If API keys are used, what is the recommended way to provision and deliver them to customers in a secure and user-friendly manner?I haven't been able to find documentation that clearly explains which approach is preferred.

How to Properly Handle Data Access and Authentication in a Geotab Add-In

page-user page-user-john-luan-2076 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

<p>We are developing a Geotab Add-In where certain vehicle data is processed externally, and the prediction results are then fetched from an external system but displayed inside the Add-In. Since this requires authenticated API calls, what is the recommended best practice in the Geotab ecosystem for authentication?</p><ul><li>Should an Add-In rely on API keys or implement OAuth2 for secure access?</li><li>If API keys are used, what is the recommended way to provision and deliver them to customers in a secure and user-friendly manner?</li></ul><p>I haven't been able to find documentation that clearly explains which approach is preferred.</p>

Viimeaikaiset toiminnot

How to Properly Handle Data Access and Authentication in a Geotab Add-In