Important changes to the FreeAgent API

Announcements
1

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server side
as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You should
check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.

2

thanks for your replyOn Fri, Feb 19, 2016 at 12:11 AM, vikaskhairnar@commusoft.co.uk wrote:

In your documentation you written that "For anyone using a reasonably
modern development stack then you should have no problems at all. " I
didn’t get this line what do you mean that? please let me know in details?

On Friday, 16 October 2015 14:40:57 UTC+5:30, David Jones wrote:

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server side
as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You
should check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.

–
You received this message because you are subscribed to the Google Groups
“FreeAgent API” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to freeagent_api+unsubscribe@googlegroups.com.
To post to this group, send email to freeagent_api@googlegroups.com.
Visit this group at https://groups.google.com/group/freeagent_api.
For more options, visit https://groups.google.com/d/optout.

3

my app name was Commusoft FreeAgent ApplicationOn Friday, 19 February 2016 18:05:17 UTC+5:30, vikask...@commusoft.co.uk wrote:

Hi ,

  • I am using php curl for calling freeagent API’s and I have generated
    accesstoken from sandbox account using url
    https://api.sandbox.freeagent.com/v2

  • My php code is like this :

       $acessToken = '1HSesQ_

TQWCDbTCxMuLlbCLk9PHMNhg5Ppy9zi5JN’;
$c = curl_init(‘https://api.sandbox.freeagent.com/v2/company’
);
curl_setopt($c, CURLOPT_HTTPHEADER, array(
‘Accept: application/json’,
‘Content-Type: application/json’,
'Authorization: Bearer '.$acessToken
));
curl_setopt($c, CURLOPT_USERAGENT, ‘Example app’);
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);
if ( $params != ‘’ ) {
curl_setopt($c, CURLOPT_POST, true);
curl_setopt($c, CURLOPT_POSTFIELDS, json_encode($params));
}
curl_setopt($c, CURLOPT_SSL_VERIFYPEER, false);

    $response = curl_exec($c);
    $body = json_decode($response);
    print_r($body);

  • I am getting following response please suggest what to do?

    stdClass Object
    (
    [errors] => stdClass Object
    (
    [error] => stdClass Object
    (
    [message] => Resource not found
    )

    )

)

On Friday, 16 October 2015 14:40:57 UTC+5:30, David Jones wrote:

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server side
as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You
should check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.

4

Hi there,

You appear to be posting to “api-sandbox” rather than “api*.*sandbox”, note
the “.” rather than “-”.
The correct hostname for our sandbox API is
“https://api.sandbox.freeagent.com”.

I hope this helps!
Dave JOn Monday, 25 July 2016 09:29:55 UTC+1, vevochat2015@gmail.com wrote:

Hello,
I use freeagent for api call, but when send request for this url
https://api-sandbox.freeagent.com/v2/bank_accounts then i get this error

HTTP/1.1 302 Found
X-request-id: 25f5a2ed-c5dd-4dc9-9eaa-a7826ad7d4d9
X-rev: 407b8c
X-content-type-options: nosniff
Transfer-encoding: chunked
Strict-transport-security: max-age=31536000;
Vary: Origin
X-runtime: 0.037820
Server: nginx
Connection: keep-alive
Location: https://www.freeagent.com/
Date: Mon, 25 Jul 2016 06:17:54 GMT
X-frame-options: SAMEORIGIN
Content-type: text/html; charset=utf-8
X-host: web5-ash

You are being redirected.

Please help me if any issue on this…

Thanks…

5

Hi ,

  • I am using php curl for calling freeagent API’s and I have generated
    accesstoken from sandbox account using url
    https://api.sandbox.freeagent.com/v2

  • My php code is like this :

       $acessToken = '1HSesQ_TQWCDbTCxMuLlbCLk9PHMNhg5Ppy9zi5JN';
    $c = curl_init('https://api.sandbox.freeagent.com/v2/company');
curl_setopt($c, CURLOPT_HTTPHEADER, array(
        'Accept: application/json',
        'Content-Type: application/json',
        'Authorization: Bearer '.$acessToken
    ));
curl_setopt($c, CURLOPT_USERAGENT, 'Example app');
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);
if ( $params != '' ) {
    curl_setopt($c, CURLOPT_POST, true);
    curl_setopt($c, CURLOPT_POSTFIELDS, json_encode($params));
}
curl_setopt($c, CURLOPT_SSL_VERIFYPEER, false);

$response = curl_exec($c);
$body = json_decode($response);
print_r($body);

  • I am getting following response please suggest what to do?

    stdClass Object
    (
    [errors] => stdClass Object
    (
    [error] => stdClass Object
    (
    [message] => Resource not found
    )

    )

)

6

Hi ,

  • I am using php curl for calling freeagent API’s and I have generated
    accesstoken from sandbox account using url
    https://api.sandbox.freeagent.com/v2

  • My php code is like this :

       $acessToken = '1HSesQ_

TQWCDbTCxMuLlbCLk9PHMNhg5Ppy9zi5JN’;
$c = curl_init(‘https://api.sandbox.freeagent.com/v2/company’);
curl_setopt($c, CURLOPT_HTTPHEADER, array(
‘Accept: application/json’,
‘Content-Type: application/json’,
'Authorization: Bearer '.$acessToken
));
curl_setopt($c, CURLOPT_USERAGENT, ‘Example app’);
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);
if ( $params != ‘’ ) {
curl_setopt($c, CURLOPT_POST, true);
curl_setopt($c, CURLOPT_POSTFIELDS, json_encode($params));
}
curl_setopt($c, CURLOPT_SSL_VERIFYPEER, false);

    $response = curl_exec($c);
    $body = json_decode($response);
    print_r($body);

  • I am getting following response please suggest what to do?

    stdClass Object
    (
    [errors] => stdClass Object
    (
    [error] => stdClass Object
    (
    [message] => Resource not found
    )

    )

)On Friday, 16 October 2015 14:40:57 UTC+5:30, David Jones wrote:

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server side
as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You
should check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.

7

I am using php and curl to call Freeagent’s API’s should I need to change
anything?On Friday, 16 October 2015 14:40:57 UTC+5:30, David Jones wrote:

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server side
as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You
should check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.

8

Hello,
I use freeagent for api call, but when send request for this url
https://api-sandbox.freeagent.com/v2/bank_accounts then i get this error

HTTP/1.1 302 Found
X-request-id: 25f5a2ed-c5dd-4dc9-9eaa-a7826ad7d4d9
X-rev: 407b8c
X-content-type-options: nosniff
Transfer-encoding: chunked
Strict-transport-security: max-age=31536000;
Vary: Origin
X-runtime: 0.037820
Server: nginx
Connection: keep-alive
Location: https://www.freeagent.com/
X-frame-options: SAMEORIGIN
Content-type: text/html; charset=utf-8
X-host: web5-ash

You are being redirected.

Please help me if any issue on this…

Thanks…

9

My API’s are working GET(company) and POST(create customer) by access token
I have generated using these steps
https://dev.freeagent.com/docs/quick_start, means my app is ready for
“Important changes to the FreeAgent API” ? also when it will be Live on 22
feb should my old access tokens will work as it is? or need to refresh?On Friday, 19 February 2016 18:39:21 UTC+5:30, vikask...@commusoft.co.uk wrote:

if from my steps I have given if it’s working for me for GET and POST
api’s create customer and get company, is this mean no need to do anything
from my side?

On Friday, 19 February 2016 18:17:36 UTC+5:30, vikask...@commusoft.co.uk wrote:

my app name was Commusoft FreeAgent Application

On Friday, 19 February 2016 18:05:17 UTC+5:30, vikask...@commusoft.co.uk wrote:

Hi ,

  • I am using php curl for calling freeagent API’s and I have generated
    accesstoken from sandbox account using url
    https://api.sandbox.freeagent.com/v2

  • My php code is like this :

       $acessToken = '1HSesQ_

TQWCDbTCxMuLlbCLk9PHMNhg5Ppy9zi5JN’;
$c = curl_init(’
https://api.sandbox.freeagent.com/v2/company’);
curl_setopt($c, CURLOPT_HTTPHEADER, array(
‘Accept: application/json’,
‘Content-Type: application/json’,
'Authorization: Bearer '.$acessToken
));
curl_setopt($c, CURLOPT_USERAGENT, ‘Example app’);
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);
if ( $params != ‘’ ) {
curl_setopt($c, CURLOPT_POST, true);
curl_setopt($c, CURLOPT_POSTFIELDS, json_encode($params));
}
curl_setopt($c, CURLOPT_SSL_VERIFYPEER, false);

    $response = curl_exec($c);
    $body = json_decode($response);
    print_r($body);

  • I am getting following response please suggest what to do?

    stdClass Object
    (
    [errors] => stdClass Object
    (
    [error] => stdClass Object
    (
    [message] => Resource not found
    )

    )

)

On Friday, 16 October 2015 14:40:57 UTC+5:30, David Jones wrote:

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server
side as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You
should check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.

10

if from my steps I have given if it’s working for me for GET and POST api’s
create customer and get company, is this mean no need to do anything from
my side?On Friday, 19 February 2016 18:17:36 UTC+5:30, vikask...@commusoft.co.uk wrote:

my app name was Commusoft FreeAgent Application

On Friday, 19 February 2016 18:05:17 UTC+5:30, vikask...@commusoft.co.uk wrote:

Hi ,

  • I am using php curl for calling freeagent API’s and I have generated
    accesstoken from sandbox account using url
    https://api.sandbox.freeagent.com/v2

  • My php code is like this :

       $acessToken = '1HSesQ_

TQWCDbTCxMuLlbCLk9PHMNhg5Ppy9zi5JN’;
$c = curl_init(‘https://api.sandbox.freeagent.com/v2/company’
);
curl_setopt($c, CURLOPT_HTTPHEADER, array(
‘Accept: application/json’,
‘Content-Type: application/json’,
'Authorization: Bearer '.$acessToken
));
curl_setopt($c, CURLOPT_USERAGENT, ‘Example app’);
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);
if ( $params != ‘’ ) {
curl_setopt($c, CURLOPT_POST, true);
curl_setopt($c, CURLOPT_POSTFIELDS, json_encode($params));
}
curl_setopt($c, CURLOPT_SSL_VERIFYPEER, false);

    $response = curl_exec($c);
    $body = json_decode($response);
    print_r($body);

  • I am getting following response please suggest what to do?

    stdClass Object
    (
    [errors] => stdClass Object
    (
    [error] => stdClass Object
    (
    [message] => Resource not found
    )

    )

)

On Friday, 16 October 2015 14:40:57 UTC+5:30, David Jones wrote:

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server
side as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You
should check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.

11

In your documentation you written that "For anyone using a reasonably
modern development stack then you should have no problems at all. " I
didn’t get this line what do you mean that? please let me know in details?On Friday, 16 October 2015 14:40:57 UTC+5:30, David Jones wrote:

Hi Developers,

We’re making some changes to our SSL configuration that you need to be
aware of, to ensure there’s no disruption to yourself or your end-users.

What is changing?

We’re adjusting the way our server negotiates encryption keys when
establishing a secure (TLS) connection with your client(s).

The prime number (often called dh_param) that is used for Diff-Helleman
(DH) key exchange is being increased from 1024 bits to 2048 bits in line
with security best practices.

Please see the FreeAgent engineering blog
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=5147b05598f8412f9d7e3f688cb39f43
for further information on why we are making this change.

Please note that we are not vulnerable to the “logjam” attack server side
as we do not support export grade ciphers.

When will it happen?

The change will occur on the morning of Monday 22 February 2016.

What should I do ?

Please make sure that your application stack can support one of the
ciphersuites listed under Mozilla’s Intermediate Compatibility list
http://s485235934.t.en25.com/e/er?s=485235934&lid=1333&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=9779605c968740eba4b2a4b418a5bccb
.

We’ve already rolled out this change to our sandbox environment. You
should check that your application can negotiate a TLS connection to:*
https://api.sandbox.freeagent.com https://api.sandbox.freeagent.com.*

My application does not work!

All modern client platforms should be compatible with the supported
ciphersuites.

Please read our blog post
http://s485235934.t.en25.com/e/er?s=485235934&lid=1332&elq=99e5598a31c04ec580447b100f4f1aa2&elqaid=1547&elqat=1&elqTrackId=96958346d752490f9097749ee673509e
for more details, especially if you are using a Java based stack.

Wait, I have some questions?

Feel free to post your questions in the thread below, we’ll be happy to
help.