Jump to Content
Developers | SamsaraFeedbackNewsletterSupportBecome a partner
GuidesRecipesAPI ReferenceChangelogDiscussions
FeedbackNewsletterSupportBecome a partnerDevelopers | Samsara
GuidesRecipesAPI ReferenceChangelogDiscussions

Discussions

Ask a Question
ANSWERED

Question about Oauth2 implementation details

Hi, Currently I am using Samsara Legacy API. The authorization logic atm is using the api key. But I saw, that there is oaut2 mention. We prefer to use oauth2 based authorizations, to add additional level of security - using static api key is not as secure as oaut2. So, for Oauth2 related info I see in the docs: https://www.samsara.com/api-legacy#section/Authentication/OAuth2 just that table. From where can we get more info, about: - how it must be implemented - do we need to create app, which will be installed per client, with permissions .. etc - what are the possible scopes - possible examples, for: - authorization, eg initiall "install" request - refresh /get new token pairs/
oauth2
Posted by Mihail Krastev about 2 years ago
  • Recent
  • Popular
  • Unanswered
addressesalertsassetsattributescamerascorscsvdevicesdocumentsdriver-assignmentsdriver-workflowdvirsefficiencyequipmenterror-codesfuelgpshosiftamaintenancemileagemobile-sdkoauth2routesroutingsafetysandboxsensorsspeedspeedingtelematicstrailerstripsunpowered assetsvehicle-assignmentswebhooks