> ## Documentation Index > Fetch the complete documentation index at: https://docsy3.mile.app/llms.txt > Use this file to discover all available pages before exploring further. # Update location history by email & createdTime ## OpenAPI ````yaml /openapi/public/openapi-task.json put /location-history/ openapi: 3.0.0 info: title: API - Task version: 3.0.0 description: 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 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 the platform 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)** paths: /location-history/: put: tags: - Location History summary: Update location history by email & createdTime operationId: putLocationHistory requestBody: $ref: '#/components/requestBodies/putRequestLocHistory' responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/ApiResponse' examples: response: value: status: true message: Success location_history: email: example@example.com taskId: 634e98098ce69d29474a7e11 speed: 40 distance: 50 duration: 50 lat: -6.1771046 lon: 106.9240199 _id: >- 634e98098ce07d29474a7e22_example@example.com_1675224349343 time: 1675224349343 organizationId: 634e98098ce07d29474a7e22 createdTime: '2022-10-07 03:00:58' updatedTime: '2022-10-07 04:00:58' data: temperature: 31 anotherKey: anotherValue '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. '404': description: Data not found 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: Data not found '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@example.com. deprecated: false security: - bearerAuth: [] components: requestBodies: putRequestLocHistory: content: application/json: schema: $ref: '#/components/schemas/putRequestLocHistory' required: true schemas: ApiResponse: type: object properties: status: type: boolean description: Indicates whether the request was successful. code: type: integer description: HTTP status code. message: type: string description: A message providing additional information about the response. location_history: $ref: '#/components/schemas/LocationHistoryResponse' putRequestLocHistory: title: putRequestLocHistory example: email: example@example.com lat: -6.934837011379089 lon: 107.74135602107883 speed: 102 createdTime: '2023-07-07 16:00:10' distance: 10 duration: 1 createdFrom: GPS data: temp: 31 taskId: '' time: 1688720650331 type: object properties: email: type: string description: >- Required, User's email assigned to the monitored task. **Example:** `example@example.com` taskId: type: string description: >- Unique ID to identify the task. **Example:** `634e98098ce69d29474a7e11` speed: type: integer description: Vehicle speed in kilometers per hour. **Example:** `102` distance: type: integer description: Distance traveled from the previous location. **Example:** `10` duration: type: integer description: >- Time duration spent at this location in milliseconds. **Example:** `1` createdFrom: type: string description: >- Source identifier for the location history entry. System-generated entries default to `mileAppField`, override this value when integrating a custom device or external source. **Example:** `GPS` **Default:** `mileAppField` lat: type: string description: >- Required, Latitude coordinate position. **Example:** `-6.934837011379089` lon: type: string description: >- Required, Longitude coordinate position. **Example:** `107.74135602107883` data: type: object description: >- This is a free object that you can fill with any data in object format. Use it to store dynamic information that is not covered by the standard fields, such as fuel level or vehicle temperature. Any key you send is stored as-is and returned in the location history response. **Example:** `{'temp': 31}` additionalProperties: true required: - email - lat - lon LocationHistoryResponse: type: object properties: email: type: string description: User's email assigned to the monitored task. lat: type: number description: Latitude coordinate position. lon: type: number description: Longitude coordinate position. speed: type: integer description: Vehicle speed in kilometers per hour. distance: type: integer description: Distance traveled from the previous location. distanceToDest: type: number description: Distance estimated from the next location. duration: type: integer description: Time duration spent at this location in milliseconds. createdTime: type: string description: Time at which the location history was created. _id: type: string description: Unique identifier for the location history entry. taskId: type: string description: Unique ID to identify the task. time: type: integer description: A timestamp indicating the time of the location history entry. organizationId: type: string description: Unique identifier for the organization. eventName: type: string description: A flagging of location history with value otw, nearBy and done. isLatest: type: boolean description: Identifier for flagging the latest location history createdFrom: type: string description: >- Source identifier for the location history entry. System-generated entries default to `mileAppField`, override this value when integrating a custom device or external source. **Example:** `GPS` **Default:** `mileAppField` updatedBy: type: string description: Email of the user who last updated the location history entry. createdBy: type: string description: Email of the user who created the location history entry. updatedTime: type: string description: Time at which the location history entry was last updated. data: type: object description: >- Free object returned exactly as it was sent when the location history was created or updated. Contains any dynamic information that is not covered by the standard fields, such as fuel level or vehicle temperature. **Example:** `{'temperature': 31, 'anotherKey': 'anotherValue'}` additionalProperties: true securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: Use a valid Bearer token to authenticate. ````