We are using the old API to handle our invoicing (we are have kicked off
the project to move to the new version of the API, but it will take some
time) which is set to sunset on Dec 31 of this year.
When we went to run our periodic update process, we receive a 400 error
from the timeslips API. Do you have any idea what may be causing this?
java.io.IOException: Server returned HTTP response code: 400 for URL:
https://unlikelypear.freeagentcentral.com/timeslips
You’re right Akil, the maximum is 24 hours.On Tuesday, November 19, 2013 1:51:13 PM UTC, Akil F. wrote:
Thank you for your response. I think I may have found the issue. It looks
like we are attempting to create a timeslip that is 29 hours long, but I
believe the maximum is probably less than that (8 hours or something I
would assume). We’ll clean up our data and retry.On Tuesday, November 19, 2013 7:42:54 AM UTC-6, Olly H wrote:
Hi Akil
In order to understand this problem please can you give us a bit more
information about the API call you’re making please? For example, are you
making a POST request and are you passing in the required parameters
(seehttps://dev.freeagent.com/docs/api_v1#timeslips)?Olly
On Tuesday, November 19, 2013 1:38:05 PM UTC, Akil F. wrote:
We are using the old API to handle our invoicing (we are have kicked
off the project to move to the new version of the API, but it will take
some time) which is set to sunset on Dec 31 of this year.When we went to run our periodic update process, we receive a 400 error
from the timeslips API. Do you have any idea what may be causing this?
java.io.IOException: Server returned HTTP response code: 400 for URL:
Simple accounting software for UK small businesses - FreeAgent
Hi Akil
In order to understand this problem please can you give us a bit more
information about the API call you’re making please? For example, are you
making a POST request and are you passing in the required parameters
(seehttps://dev.freeagent.com/docs/api_v1#timeslips)?
OllyOn Tuesday, November 19, 2013 1:38:05 PM UTC, Akil F. wrote:
We are using the old API to handle our invoicing (we are have kicked
off the project to move to the new version of the API, but it will take
some time) which is set to sunset on Dec 31 of this year.When we went to run our periodic update process, we receive a 400 error
from the timeslips API. Do you have any idea what may be causing this?
java.io.IOException: Server returned HTTP response code: 400 for URL:
Simple accounting software for UK small businesses - FreeAgent
Thank you for your response. I think I may have found the issue. It looks
like we are attempting to create a timeslip that is 29 hours long, but I
believe the maximum is probably less than that (8 hours or something I
would assume). We’ll clean up our data and retry.On Tuesday, November 19, 2013 7:42:54 AM UTC-6, Olly H wrote:
Hi Akil
In order to understand this problem please can you give us a bit more
information about the API call you’re making please? For example, are you
making a POST request and are you passing in the required parameters
(seehttps://dev.freeagent.com/docs/api_v1#timeslips)?Olly
On Tuesday, November 19, 2013 1:38:05 PM UTC, Akil F. wrote:
We are using the old API to handle our invoicing (we are have kicked
off the project to move to the new version of the API, but it will take
some time) which is set to sunset on Dec 31 of this year.When we went to run our periodic update process, we receive a 400 error
from the timeslips API. Do you have any idea what may be causing this?
java.io.IOException: Server returned HTTP response code: 400 for URL:
Simple accounting software for UK small businesses - FreeAgent