Sign-in

LiquidPlanner
30-day free trial
30-second sign-up

About our forums

Our forum platform uses a separate login to identify you; it's not the same as your LiquidPlanner application login.

>> Login to the forums now 

If you wish to post and subscribe to change notifications, you will need to create a forum account.

After you login, you can access your profile by clicking your name floating at the top of the page. Clicking your name will also allow you to subscribe to e-mail change notification messages for the section you are currently looking at. 

Note, the forums are a public area. Do not post any private workspace content.

Join the LiquidPlanner Developer Forum > Updating Tracking time

Examples say to add tracking time do something like this:
curl https://app.liquidplanner.com/api/workspaces/:id/tasks/:id/track_time \ -d '{ work: 4, low: "1.5d", high: "3d" }'

I have tried different versions of this:
"http://..../track_time -d '{ work: 4, member_id: 85969, activity_id=36473 }'"

But I have not gotten it to work. What am I doing wrong?

August 19, 2010 | Registered CommenterMichael Beland

From the requests I see in our logs, it appears you're running into trouble with quoting of arguments when you invoke curl. This results in a garbled request to the server -- it is receiving a URL like "/track_time -d ..." (that is, the URL has trailing junk that should instead be translated by curl into the POST body).

You shouldn't need any quotes around the URL, because it doesn't contain special characters such as ampersand or question mark.

You will need quotes around the POST data (the parameter value after the -d parameter) because it contains whitespace (as well as quoted strings, etc.).

curl also allows you to specify a filename prepended with the at symbol, like:

-d @my_data.txt

and it will read the contents of the file my_data.txt

You can try placing your JSON in such a text file, which will let you side-step any quoting issues at the command line.

If this general advice doesn't clear things up, please email me the exact command line you're using and I'll figure out what bit of punctuation isn't quite doing what we intend.

August 24, 2010 | Registered CommenterBrett Bender