James Adam's dashboard

A comment on the problem "Drop down list selection doesn't work in Chrome" in FreeAgent Central:

Works great for me. I'm curious - what was the underlying issue? – James Adam, on February 18, 2010 17:29

James Adam marked one of Olly's replies in FreeAgent Central as useful. Olly replied to the problem "POSTing to timeslip API always returning 400".

James Adam replied on January 29, 2010 18:53 to the problem "POSTing to timeslip API always returning 400" in FreeAgent Central:

I thought I'd tried that too, but clearly not. It's working now. Thanks!

A comment on the problem "POSTing to timeslip API always returning 400" in FreeAgent Central:

Urgh, the 'code' formatting has message up my XML. I'll try again with the request:

POST /timeslips HTTP/1.1
Accept: */*; q=0.5, application/xml
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip, deflate
Authorization: Basic amFtZXNAbGF6eWF0b20uY29tOndhbTN3eW9yZDlpYg==
Content-Length: 319
Host: lazyatom.freeagentcentral.com

<?xml version="1.0" encoding="UTF-8"?>
<timeslip>
<dated-on type="datetime">2010-01-29T15:42:23+00:00</dated-on>
<hours type="float">1.0</hours>
<task-id type="integer">22532</task-id>
<comment>Hello</comment>
<project-id type="integer">27407</project-id>
<user-id type="integer">2602</user-id>
</timeslip> – James Adam, on January 29, 2010 16:19

James Adam replied on January 29, 2010 16:17 to the problem "POSTing to timeslip API always returning 400" in FreeAgent Central:

I'm seeing this again (although I can still post via my Dashboard widget). Here's my raw request (made at 29/01/10 15:42:23):


POST /timeslips HTTP/1.1
Accept: */*; q=0.5, application/xml
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip, deflate
Authorization: Basic ivealterestthisbutitreallyisthereandotherrequestswork==
Content-Length: 319
Host: lazyatom.freeagentcentral.com

<?xml version="1.0" encoding="UTF-8"?>

2010-01-29T15:42:23+00:00
1.0
22532
Hello
27407
2602



And here's the response:

HTTP/1.1 400 Bad Request
Date: Fri, 29 Jan 2010 15:42:23 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 2.2.9
X-Runtime: 9
Cache-Control: no-cache
Set-Cookie: _session_id=fc90e7354838f7d9748bf764b674d7bd; domain=.freeagentcentral.com; path=/; HttpOnly
Status: 400
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 21
Connection: close
Content-Type: application/xml; charset=utf-8


James Adam started following the problem "Problem accessing timeslips via API" in FreeAgent Central.

James Adam started following the question "Explanations for newly uploaded transactions in a VAT locked period" in FreeAgent Central.

James Adam replied on January 29, 2010 12:30 to the question "Correcting Expense Explanation" in FreeAgent Central:

We have some entries that were not explained, but I now cannot set the explanation because they fall within a VAT-locked period. Is there any way to resolve this?

James Adam started following the question "Correcting Expense Explanation" in FreeAgent Central.

James Adam replied on January 29, 2010 09:17 to the problem "Drop down list selection doesn't work in Chrome" in FreeAgent Central:

I have this problem on Chrome 4.0.302.2 (dev channel)

James Adam started following the problem "Drop down list selection doesn't work in Chrome" in FreeAgent Central.

James Adam replied on January 25, 2010 14:47 to the idea "Return new project when creating via the API" in FreeAgent Central:

Silly me - that's fine.

James Adam shared an idea in FreeAgent Central on January 25, 2010 12:56:

Return new project when creating via the API

When creating a project using the API, it'd be great to get the new project back in the response body, so we can use the ID.

At the moment, it looks like we get a 201 status, but an empty body, which means another request to find out what the ID of the new project is.