sander's dashboard

The numbers you gave seem to be seconds. You must send milliseconds: multiply your values by 1000.

In case the milliseconds do not work, please send the complete JSON to our support e-mail address and we shall look into it in more detail.

What exactly are you sending to the server?

This one works for me.

<?php // This will be where we test the api to Toggl

$target = "http://www.toggl.com";
$cookie_file = 'cookies.txt';

// Remove the current cookie file
unlink($cookie_file);

$send_data = array();
$send_data['start_date_ms'] = strtotime(date("m/d/Y 00:00:00")) * 1000;
$send_data['end_date_ms'] = strtotime(date("m/d/Y 00:00:00")) * 1000;
$send_data['version'] = '1.13.2';
$send_data['tzoffset'] = '0';
$send_data['user_login'] = "123";
$send_data['user_password'] = "123";

$login = curl_init();
curl_setopt($login, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($login, CURLOPT_HTTPHEADER, array('Accept: application/json', 'Content-Type: application/json'));
curl_setopt($login, CURLOPT_URL, $target.'/user/login');
curl_setopt($login, CURLOPT_POSTFIELDS, json_encode($send_data));

curl_setopt($login, CURLOPT_COOKIESESSION, TRUE);
curl_setopt($login, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($login, CURLOPT_COOKIEJAR, $cookie_file);

$login_details = json_decode(curl_exec($login));

curl_close($login); // This is moved up here (it was at the end)

$get_details = curl_init();
curl_setopt($get_details, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($get_details, CURLOPT_HTTPHEADER, array('Accept: application/json', 'Content-Type: application/json'));
curl_setopt($get_details, CURLOPT_URL, $target.'/task/list');
curl_setopt($get_details, CURLOPT_POSTFIELDS, json_encode($send_data));

curl_setopt($get_details, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($get_details, CURLOPT_COOKIEJAR, $cookie_file);

$list_details = json_decode(curl_exec($get_details));
curl_close($get_details);

$currentTime = 0;
$theEntries = array();

foreach($list_details?>content as $tmp_detail)
{
if($tmp_detail->duration > 0)
{
// Break down the number into .25 increments
$theAmount = number_format(((($tmp_detail->duration / 1000) / 60) / 15)) * .25;

$theEntries[$tmp_detail->description] = $theAmount;
$currentTime = $currentTime + $theAmount;
}else{
// This is the end all so it must equal 4 or 8 depending on when we run this.
$offset = 4 - $currentTime;
$theEntries[$tmp_detail->description] = $offset;
}
}

echo "

";

print_r($theEntries);

echo "

";
?>

What programming language are you using to connect? I'll try and post a working login sequence if you tell me the language.

You set the content type header to 'application/x-www-form-urlencoded' and use the /user/login url. This will not invoke the API. The server should respond to this request with a HTML page or a redirect to the /home url. If you want to use the API, set the content type to 'application/json' and use the url '/user/login.json'. In this case the server should respond with a JSON reply.

The post should be JSON, as in {"tzoffset":0, "user_login":"myuser", "user_password":"mypassword", "version":"1.13.2"}. Using x-www-form-urlencoded might work, but has never been tested. In any case use user_login and user_password instead of user-login and user-password (the hyphen is only used in the XML api).

Hope this helps

Hi Frank.

We finally managed to reproduce the bug over here. I believe we can deal with it ourselves from now on.

Thank you for your assistance.

You can download the debug version here:

http://download.toggl.com/widget/Togg...

Toggl Desktop is built with gcc on mingw. I enabled the -g option for compiling the .o files. The embedded static Qt libraries are release versions (as it would take us several days to build debug libraries on the build VM).

Let us know if you need anything else.

I investigated this matter and found that Toggl adds 24 hours to the end date ms. You can subtract 24 hours (24*3600000 ms) from end_date_ms to work around this unfortunate situation:

$send_data['end_date_ms'] = strtotime(date("m/d/Y 11:59:59")) * 1000 - 24 * 3600000;

You didn't handle cookies.

Toggl creates a _toggl_session cookie upon logging in, you need to pass that along to any subsequent requests.

Code here:

<?php // This will be where we test the api to Toggl

$target = "http://www.toggl.com";
$cookie_file = 'cookies.txt';

$send_data = array();
$send_data['start_date_ms'] = strtotime(date("m/d/Y 00:00:00")) * 1000;
$send_data['end_date_ms'] = strtotime(date("m/d/Y 23:59:59")) * 1000;
$send_data['version'] = '0.16.12';
$send_data['tzoffset'] = '0';
$send_data['user_login'] = {username or email};
$send_data['user_password'] = {password};

$login = curl_init();
curl_setopt($login, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($login, CURLOPT_HTTPHEADER, array('Accept: application/json', 'Content-Type: application/json'));
curl_setopt($login, CURLOPT_URL, $target.'/user/login');
curl_setopt($login, CURLOPT_POSTFIELDS, json_encode($send_data));

// This is added
curl_setopt($login, CURLOPT_COOKIESESSION, TRUE);
curl_setopt($login, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($login, CURLOPT_COOKIEJAR, $cookie_file);
// ***

$login_details = json_decode(curl_exec($login));

echo "<stron?>Login Details<br />";
echo "<pre>";
print_r($login_details);
echo "</pre>";

curl_close($login); // This is moved up here (it was at the end)

$get_details = curl_init();
curl_setopt($get_details, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($get_details, CURLOPT_HTTPHEADER, array('Accept: application/json', 'Content-Type: application/json'));
curl_setopt($get_details, CURLOPT_URL, $target.'/task/list');
curl_setopt($get_details, CURLOPT_POSTFIELDS, json_encode($send_data));

// This is added
curl_setopt($get_details, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($get_details, CURLOPT_COOKIEJAR, $cookie_file);
// ***

$list_details = json_decode(curl_exec($get_details));

echo "<strong>List Details</strong><br />";
echo "<pre>";
print_r($list_details);
echo "</pre>";

curl_close($get_details);

?>

In what view do you see the tasks on the wrong day? Are they in the timer (the box on the left), under the recent tasks tab or the reports tab?

Your dates in $a_data are in seconds. They have to be in milliseconds, so you have to multiply them by 1000.

Hi Ruben. Can you tell me what response you are get for the non-working requests?

I notice that you have not provided a tzoffset argument in the login request. If you do not want to bother with tzoffset then set it to 0; tzoffset is a required field.

is it possible that these tasks were not stopped at the end of the day?

There is an user neoPhillip with an email address containing ...programers.com (note one 'm'), and an user neoPhillipw with an email address containing ...programmers.com. Which account do you use, and should we delete the other account?

It appears that invitations were broken. They should be fixed now.

You can create a task now and later change its start time to yesterday. There is an edit link in Toggl Desktop and Toggl Timer, where you can edit the start date and time for the task.

Also, you can open the task up from the tasks report (by clicking on the task description) and edit the start time from there.

We had a serious technical failure, which is now resolved. Tasks registered during the failure (which lasted about 1 hour) may however be lost.

Sorry about this :(

We have made no planned changes to the API. It is possible that something has broken though.

What requests have you been making and what responses did you get?