Input Parameters

Parameter	Type	Required	Description
`id_task`	Integer	Yes	Task identifier
`id_tasks_todo:`	Integer	Optional	Pending task identifier
`id_item`	Integer	Optional	Asset identifier
`page`	Integer	Optional	Page number to query (1-based) for paginated results. Used together with limit (default 100). Ignored if start is provided. Example: page=2&limit=100 returns records 101–200.
`start`	Integer	Optional	Record number where the query will start. Default is 0. All queries are limited to 100 records, when there are more than that amount this parameter should be used for pagination.
`limit`	Integer	Optional	Maximum number of records per page. Default and maximum value: 100.
`since`	Text	Optional	Start date of the range to filter event_date (inclusive). Recommended format: ISO 8601 (YYYY-MM-DD or YYYY-MM-DDThh:mm:ssZ). Examples: since=2025-10-01 or since=2025-10-01T00:00:00Z.
`until`	Text	Optional	End date of the range to filter event_date (inclusive). Recommended format: ISO 8601 (YYYY-MM-DD or YYYY-MM-DDThh:mm:ssZ). Examples: until=2025-10-31 or until=2025-10-31T23:59:59Z.

Output Parameters

Parameter	Type	Description
`id`	Integer	Unique identifier of the rescheduling record.
`id_company`	Integer	Identifier of the company to which the record belongs.
`id_tasks_todo`	Integer	Identifier of the pending task associated with maintenance.
`date_maintenance_last`	Text	Date and time of the last maintenance scheduling before rescheduling.
`date_maintenance_new`	Text	New date and time assigned for maintenance after rescheduling.
`event_date`	Text	Date and time when the rescheduling event was recorded.
`note`	Text	Observations or comments associated with the rescheduling (e.g., validation reasons or follow-up).
`id_reschedule_cause`	Integer	Identifier of the rescheduling reason (reference to a causes table).
`id_task`	Integer	Identifier of the main task related to maintenance.
`id_item`	Integer	Identifier of the item or asset on which the maintenance task is performed.
`name`	Text	Name of the responsible person, technician, or user associated with the event.
`reschedule_causes_description`	Text	Textual description of the rescheduling reason (e.g., "INSPECTION AND CONTROL OF SPACES FAILED")

Example:

Request: (GET) https://develop.fracttal.com/api/tasks_todo_log/?id_task=16443679

{
  "success": true,
  "message": "200",
  "data": [
    {
        "id": 756259,
        "id_company": 1190,
        "id_tasks_todo": 3922904,
        "date_maintenance_last": "2025-10-18T18:20:14.632+00:00",
        "date_maintenance_new": "2025-10-27T14:21:56.960+00:00",
        "event_date": "2025-10-27T14:22:28.152363+00:00",
        "note": "Validation of rescheduling for QA consultation.",
        "id_reschedule_cause": 3177,
        "id_task": 16443679,
        "id_item": 35730250,
        "name": "MIR LONDOÑO",
        "reschedule_causes_description": "INSPECTION AND CONTROL OF SPACES FAILED"	
	}
  ],
  "total": 1
}