Dismiss Tasks - Revision history

Ashley DeBon: /* Successful Response (200) */

2026-07-20T08:32:02Z

‎Successful Response (200)

Ashley DeBon: /* Close Task Popup */

2026-07-20T08:31:25Z

‎Close Task Popup

Ashley DeBon at 08:30, 20 July 2026

2026-07-20T08:30:44Z

Ashley DeBon: /* Successful Response (200) */

2026-07-20T08:24:25Z

‎Successful Response (200)

Ashley DeBon: /* Update Current Task Completion */

2026-07-20T08:23:13Z

‎Update Current Task Completion

Ashley DeBon: Created page with "== Update Current Task Completion == === Base URL === https://apimobile.callproof.com === Endpoint === /api/currenttask-completion === Purpose === Updates the completion st..."

2026-07-20T08:22:45Z

Created page with "== Update Current Task Completion == === Base URL === https://apimobile.callproof.com === Endpoint === /api/currenttask-completion === Purpose === Updates the completion st..."

New page

== Update Current Task Completion ==

=== Base URL ===
https://apimobile.callproof.com

=== Endpoint ===
/api/currenttask-completion

=== Purpose ===
Updates the completion status of one or more current tasks. Accepts a JSON list of tasks with their new status values (`0` or `1`) and applies each update for the authenticated user’s company.

=== HTTP Method ===
PUT

=== Headers ===
{| class="wikitable"
! Header !! Required !! Description
|-
| Authorization || Yes || Bearer access token
|}

=== Security ===
* '''Yes''' – Requires Bearer Token authentication.

=== Parameters ===

==== Path Parameters ====
None.

==== Query Parameters ====
None.

==== Request Body ====
{| class="wikitable"
! Parameter !! Type !! Required !! Description
|-
| task_datas || string (JSON array) || Yes || JSON array of task completion updates (see below)
|}

==== task_datas[] ====
{| class="wikitable"
! Parameter !! Type !! Required !! Description
|-
| task_id || integer || Yes || Unique identifier of the task (follow-up) to update
|-
| task_status || integer || Yes || Completion status: <code>0</code> = not completed, <code>1</code> = completed
|}

=== Successful Response (200) ===
Indicates that the task completion statuses were updated successfully.

{| class="wikitable"
! 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 ===
{| class="wikitable"
! Status Code !! Meaning
|-
| 200 || Validation failed – response body uses <code>clientStatusCode</code> 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 <code>task_datas</code>.
* '''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.

← Older revision		Revision as of 08:31, 20 July 2026
Line 1:		Line 1:
−	== Close Task Popup ==	+	== [[Mobile_API]] »Close Task Popup ==

	=== Base URL ===		=== Base URL ===

← Older revision		Revision as of 08:23, 20 July 2026
Line 1:		Line 1:
−	== Update Current Task Completion ==	+	== [[Mobile_API]] »Update Current Task Completion ==

	=== Base URL ===		=== Base URL ===

@@ Line 33: / Line 33: @@
 ==== Request Body ====
 None.
 === Successful Response (200) ===

@@ Line 1: / Line 1: @@
-== [[Mobile_API]] &#187;Update Current Task Completion ==
+== Close Task Popup ==
 === Base URL ===
@@ Line 5: / Line 5: @@
 === Endpoint ===
-/api/currenttask-completion
+/api/close-taskpopup
 === Purpose ===
-Updates the completion status of one or more current tasks. Accepts a JSON list of tasks with their new status values (`0` or `1`) and applies each update for the authenticated user’s company.
+Dismisses the current-tasks popup for the authenticated user for the day by turning off the user’s “show task popup” flag.
 === HTTP Method ===
@@ Line 32: / Line 32: @@
 ==== Request Body ====
-{| class="wikitable"
+None.
 === Successful Response (200) ===
-Indicates that the task completion statuses were updated successfully.
+Indicates that the task popup was dismissed successfully.
 {| class="wikitable"
@@ Line 67: / Line 46: @@
 | company_id || integer || Identifier of the authenticated user’s company
 |-
-| message || string || Confirmation message (for example, "Tasks updated Successfully.")
+| message || string || Confirmation message (for example, "Tasks dismissed for the day.")
 |-
 | uri || string || Requested resource URI
@@ Line 76: / Line 55: @@
 ! Status Code !! Meaning
 |-
-| 200 || Validation failed – response body uses <code>clientStatusCode</code> 401 with the first validation error message
+| 400 || Bad Request – the task popup could not be dismissed
 |-
 | 401 || Unauthorized – missing, invalid, or expired Bearer token
 |}
-* '''Validation (HTTP 200, clientStatusCode 401)''' – Missing or non-string <code>task_datas</code>.
+* '''400''' – An error occurred while dismissing the popup (for example, "Error while Dismiss the task details").
 * '''401''' – Authentication failed or the access token is missing/expired.

@@ Line 46: / Line 46: @@
 | task_status || integer || Yes || Completion status: <code>0</code> = not completed, <code>1</code> = completed
 |}
 === Successful Response (200) ===