> ## Documentation Index > Fetch the complete documentation index at: https://docs.mileapp.dev/llms.txt > Use this file to discover all available pages before exploring further. # Read location history by token ## OpenAPI ````yaml /openapi/public/openapi-task.json get /location-history/tracking/{token} openapi: 3.0.0 info: title: MileApp API - Task version: 3.0.0 description: MileApp API Documentation - RESTful API for field operations management. servers: - url: https://apiweb.mile.app/api/v3 security: - bearerAuth: [] tags: - name: Task description: >- A task is an item of work intended for completion by an assignee. It can embody activities like pickups, deliveries, planning, inspections, sales visits, or other work-related actions within your organization. Tasks encompass essential attributes, including IDs, flow, time, status indicators, assignee information, order index, and other pertinent data. The content of a task is configurable based on your specified flow settings. For instance, tasks can serve as visits during the route optimization process, functioning as pivotal elements. The task can also represent a visit in route optimization, please follow [this link](#tag/Routing) to read more detail. **To see the details of task object, please follow [this link](#tag/task_model)** - name: Location History description: >- Location history is data that stores the user's location points that are sent periodically from the MileApp mobile application if the user activates the tracking feature. However, this endpoint can also be useful for integration into the user's IoT devices such as GPS or other mobile trackers. All location data sent can be visualized in MileApp in real time and makes it easier for users to monitor field activities more accurately. **Related Guide:** [Start Finish Feature](/configuration/start-trip-end-trip-feature) - name: Task Schedule description: >- Task Schedule is a mechanism to generate tasks according to the schedule that is set by you. The task schedule attributes consist of IDs, repetition period data (daily, weekly, etc.), flow structure, task content, and time of the schedule's start & end. This schedule could help you to set a task that will be repeated at a certain period. **To see the details of task schedule object, please follow [this link](#tag/task_schedule_model)** - name: Activity description: >- An Activity is a multi-step task group created from a Workflow template. When you create an Activity, MileApp automatically creates one parent task (with `taskType = activityMaster`) plus one child task (with `taskType = activityChild`) per Workflow step, and copies field values forward between steps according to the Workflow's field mappings. Activities are stored alongside regular tasks — the parent's `_id` is also the Activity ID, and its `subId` array lists every child task in Workflow-step order. After creation, retrieve, update, or delete an Activity through the standard Task endpoints using the Activity master task's ID. **To see the details of Activity object, please follow [this link](#tag/activity_model)** paths: /location-history/tracking/{token}: get: tags: - Location History summary: Read location history by token operationId: getLocationHistorybytoken parameters: - name: token in: path required: true description: >- Tracking token generated from [POST /location-history/generate-token API](#tag/Location-History/operation/generateTokenLocationHistory) **Example**: `eyJkYXRhIjoiZXlKcGRpSTZJa1JQYkhKTVFraGtNMFpKV21SRmQxZHFkSEZWTkVFOVBTSXNJblpoYkhWbElqb2lheXRMVVc5aFEzRTJNR28zWjJ0UE1rbFdRa1pUYVU0eU9VbElTa2huVFZOT05WUTVMMko0UkZSVVVWQXlSbXRUVGxOcWJWWmpVVTA1SzBSS1FqTm5SRkppYWl0MWMzSXlWMEZSYVZCbFMydHdlbE15TlhwUVkyeExSa053ZUhoUk5FNTFlWFZIYzNwWVJtWjFNVWRKWm1WSmRWUmliRWs0Tm1KSGFWSXpRVTFpUkZwMWNqRlpNVWNyYVZkNmNXUkhkMU5GTVRaRVIzTlJlakZPTkd0amNFOTRhbEZxTVVKallXWTBQU0lzSW0xaFl5STZJamczTXpBeE9UVTFNalUzTkRGbFlUbGlOMkZsT0dOaU1EWXhZVEkzTWpVek9EQXdObVU0WW1FMU5HTXhOelJrWkdFMk1tSXlZV1JqT1RZeFptUXpPR0lpTENKMFlXY2lPaUlpZlE9PSIsImV4cGlyYXRpb24iOiIyMDI0LTAyLTI3VDA5OjU5OjMzLjA1OTA0OVoifQ==` schema: type: string responses: '200': description: Success content: application/json: schema: type: object title: NetworkCreateResponse properties: status: type: boolean description: Status of response. message: description: Message of API response. type: string tasks: description: Detail of object location history. type: object additionalProperties: true example: status: true message: Success tasks: current_page: 1 data: - _id: 64a696536d01ea0d503db772 email: example@mile.app lat: -6.23239438813826 lon: 106.82152618097032 speed: 0 distance: 0 duration: 0 startTime: '2023-07-06 10:23:00' notes: null createdTime: '2023-07-06 10:24:19' taskId: '' time: 1688639059872 organizationId: 6488344e8db84c3a511f62b2 finish: lat: -6.296958793290206 lon: 106.7858189729966 finishTime: '2023-07-06 11:23:00' notes: null totalDuration: 60 totalDistance: 24 updatedTime: '2023-07-06 10:53:36' trackedTime: 60 first_page_url: >- http://apiweb.mile.app/api/location-histories?limit=20&fields=email%2CtaskId%2Clon%2Clat&email=example%40mile.app&sortBy=createdTime&sortOrder=desc&page=1 from: 1 last_page: 1 last_page_url: >- http://apiweb.mile.app/api/location-histories?limit=20&fields=email%2CtaskId%2Clon%2Clat&email=example%40mile.app&&sortBy=createdTime&sortOrder=desc&page=1 links: - url: null label: '« Previous' active: false - url: >- http://apiweb.mile.app/api/location-histories?limit=20&fields=email%2CtaskId%2Clon%2Clat&email=example%40mile.app&&sortBy=createdTime&sortOrder=desc&page=1 label: '1' active: true - url: null label: Next » active: false next_page_url: null path: http://apiweb.mile.app/api/location-histories per_page: 20 prev_page_url: null to: 2 total: 2 '400': description: Bad Request content: application/json: schema: type: object properties: status: type: boolean description: Shows if the request was successful. message: type: string description: A short message explaining what went wrong. example: status: false message: Bad request - invalid parameters provided. '401': description: Tracking Token Expired content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: response: value: status: false message: Your tracking token has expired '500': description: Server error content: application/json: schema: type: object properties: status: type: boolean description: Shows if the request was successful. message: type: string description: A short message explaining what went wrong. example: status: false message: Internal server error, please contact support@mile.app. deprecated: false components: schemas: ErrorResponse: title: ErrorResponse type: object description: Standard error response structure properties: status: type: boolean description: Always false for error responses message: type: string description: Human-readable error message failedCode: type: string description: Error code for debugging and error tracking required: - status - message securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: Use a valid Bearer token to authenticate. ````