500 Error Returned from call to /bank_transaction_explanations

1

I’m posting with CURL to https://api.sandbox.freeagent.com/v2/bank_transaction_explanations
a payment on an invoice with the following data:

{

}

The code I’m using has been working up until today. Today as I’ve worked on
other parts of my code, this particular call began returning a 500 Error in
the response from the CURL call.

These are the headers returned:

HTTP/1.1 500 Internal Server Error Server: nginx/1.4.1 Date: Tue, 08 Oct
2013 22:42:59 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding:
chunked Connection: keep-alive Status: 500 Internal Server Error X-Request-Id:
2cd4ab417236b51e3ccfebbd3a597f10 X-Runtime: 2.496029 X-Rev: 9d7413c X-Host:
web1

Has something changed with this call? Or is there something wrong with the
API at the moment? All of my other calls, to get and update invoices and
contacts, which rely on the same CURL code seem to be working fine.

thanks,

jeremy

2

That did it. Did something change recently that would have broken this? It
definitely worked before.

3

I’m glad that worked!

I looked into it a bit and it doesn’t appear to be a recent change. In any
case, sorry about the bug!

BenOn Tuesday, 8 October 2013 15:56:13 UTC-7, Jeremy Gimbel wrote:

That did it. Did something change recently that would have broken this? It
definitely worked before.

4

Hi Jeremy,

I believe the issue is that the gross value is a number instead of a
string. Can you try again with:

gross_value: “1379.53”

and see if that works? We really should be accepting both (or at least
giving a much better error message!), but it will unblock you for now.

BenOn Tuesday, 8 October 2013 15:44:33 UTC-7, Jeremy Gimbel wrote:

I’m posting with CURL to
https://api.sandbox.freeagent.com/v2/bank_transaction_explanations a
payment on an invoice with the following data:

{

}

The code I’m using has been working up until today. Today as I’ve worked
on other parts of my code, this particular call began returning a 500 Error
in the response from the CURL call.

These are the headers returned:

HTTP/1.1 500 Internal Server Error Server: nginx/1.4.1 Date: Tue, 08 Oct
2013 22:42:59 GMT Content-Type: text/html; charset=utf-8 Transfer-Encoding:
chunked Connection: keep-alive Status: 500 Internal Server Error X-Request-Id:
2cd4ab417236b51e3ccfebbd3a597f10 X-Runtime: 2.496029 X-Rev: 9d7413c X-Host:
web1

Has something changed with this call? Or is there something wrong with the
API at the moment? All of my other calls, to get and update invoices and
contacts, which rely on the same CURL code seem to be working fine.

thanks,

jeremy