When you push a timer, CorbaTime POSTs action=push_timer with the tracked seconds, the client_id and the description to your server. Your server stores it and replies with {"success":"..."} or {"error":"..."}, and the app shows that message.
Last updated: 15 October 2026
When a timer is paused, and a client is selected, a "push" button will appear. When clicked, the information of the timer will be POSTed to your webserver.
After checking the login details (supplied depending on the method chosen in Step 1), read the POST parameter action. For a timer pushed from the app, the action is called push_timer.
The complete POST variables will be:
action=push_timer
seconds=1550
client_id=17
description=02-11 Worked hours| Field | Type | Meaning |
|---|---|---|
action | string | Always push_timer for this request. |
seconds | integer | The total tracked time of the timer in seconds. |
client_id | integer | The internal_id of the client, as returned by your server in Step 2. |
description | string | The name/description of the timer, with any date placeholder already filled in. |
The example above is a timer that has run for 25 minutes and 50 seconds (00:25:50). You can further process all the data on your server as you like; for example round the 1550 seconds to quarters or minutes however you like.
The app expects to receive a JSON encoded result. On success:
{"success":"Saved successfully"}The text of the success key is shown as a notification in the app, so keep it short.
If something went wrong, reply with a status outside the 2xx range and a short error message:
{"error":"Invalid client selected"}The error message is shown in the app. Until a success parameter is returned, the timer remains 'unpushed', meaning it can be started again. When a success parameter is returned, the timer can only be deleted or archived (archived timers are shown in the charts section).
Other instructions:
Step 1: Login methods explanation
Step 2: Load a list of clients
Step 3: Process a pushed timer