Back to All

Frontend product that allows seeing routes sent in with /v1/fleet/dispatch/routes call

I work for a software development company that has had a Samsara integration for 3 years. Up until now, we've been connecting to accounts that were already using dispatch routing in Samsara independently. And our calls to the dispatch API calls went right through, and the users could see them in their Samara account portal.

But, we just had one customer purchase Samsara to use with our software, and they've been able to setup API keys, and our service calls go through successfully. (The call is a POST to /v1/fleet/dispatch/routes?access_token=samsara_api_xxxxxxxxxxx) BUT, the routes don't appear to show up in the Samsara portal. They have a set of software for "GPS and dashcams for safety" but I don't know specific package names.

I'm assuming there is something they haven't purchased, but I don't know what piece is missing. The portal I used when I coded this has some extra icons on the dashboard, that this customer doesn't have. In particular there is one that looks like 2 map "pins" that has a submenu with "Dispatch","Routes","Recurring Routes","Planned vs Actual" which is where my test account would show the routes I sent through the API.

So, the question is, what is the minimum piece they need to see these routes in their portal, or through their Samsara android app? What can I tell them to tell their salesperson that they need?