Collection API is how our customers can share their daily routes and stops with our system. One of the other functions it offers is allowing us at 3rd Eye to associate our services with this information and send it back to the customer. A route is a scheduled or predetermined path that a driver is set to follow from a starting point to a destination. This is typically uploaded by the drivers every day to stay informed of what services needs to be done for that day. A stop is a location within a route in which services needs to be performed. When our services are being used, we can associate the data gathered from our products to the information provided by our customers.

For example: A customer purchases our 3rd Eye Verif-Eye product for service verification. With service verification, we can identify the location in which the operator collected the trash can and capture the collection being performed. We can use the route and stops provided by the customer to associate with the location of the service. 3rd Eye then identifies and send this back to the customer as proof that the service was completed. 

Our customers benefit from Collection API because they do not have to log in and log off to gather information. For example, if our customers are trying to get data without the API, they would have to manually transfer information between both systems. This data is shared within seconds between systems which makes it easy for our customers to follow up if there are any issues with their customers and the services provided. 

There are three major controllers for this API we share with our customers:

Schedule: This controls the collections tab in our portal. This section is where our customers share their routes with us. They share their routes in our system so we can identify when routes are completed. Below is an image of where we can see the status of route and detail information.

Stop: This controls the Collection Stop button in the Administration tab. This section shows our customers clients information such as names and addresses as stops. Once service is performed, our system gathers GPS data on the service address and associates it with the stop data. Below is an image of where collection stops can be accessed on our portal.

Reviewer: This control is designed to give you information back from reviews performed in 3rd Eye. Reviewers go through the events captured to see if there are any abnormalities that matches the customers definition such as Bulks and Overloads. When these are discovered, the reviewers highlight the event, which triggers the API to send this information back to our customers. For more information on bulk and overloaded containers, please reference our Verif-Eye service Bureau guide. Below is an image of one of the ways event reviews can be accessed on our portal.