Tasks Currenttask Completion

Mobile_API »Update Current Task Completion

Base URL

https://apimobile.callproof.com

Endpoint

/api/currenttask-completion

Purpose

Updates completion status for one or more current tasks in a single request. Each task can be marked completed (`1`) or not completed (`0`).

HTTP Method

PUT

Headers

Header	Required	Description
Authorization	Yes	Bearer access token

Security

• Yes – Requires Bearer Token authentication.

Parameters

Path Parameters

None.

Query Parameters

None.

Request Body

Parameter	Type	Required	Description
task_datas	string (JSON array)	Yes	JSON array of task completion updates. Each item must include task_id and task_status

task_datas[]

Parameter	Type	Required	Description
task_id	integer	Yes	Unique identifier of the task (follow-up) to update
task_status	integer	Yes	Completion status: 1 = completed, 0 = not completed

Example: [{"task_id":123,"task_status":1},{"task_id":456,"task_status":0}]

Successful Response (200)

Indicates that the task completion statuses were updated successfully.

Field	Type	Description
clientStatusCode	integer	Status indicator for the client (for example, 200)
user_id	integer	Identifier of the authenticated user
company_id	integer	Identifier of the authenticated user’s company
message	string	Confirmation message (for example, "Tasks updated Successfully.")
uri	string	Requested resource URI

Error Responses

Status Code	Meaning
200	Validation failed – response body uses clientStatusCode 401 with the first validation error message
400	Bad Request – task completion could not be updated
401	Unauthorized – missing, invalid, or expired Bearer token

• Validation (HTTP 200, clientStatusCode 401) – Missing or non-string task_datas.
• 400 – Invalid task ID ("Task Id is Invalid"), invalid task status ("Task Status Id is Invalid"), or another update error (for example, "Error while Updating Task Completion").
• 401 – Authentication failed or the access token is missing/expired.