Announcements & Changes

We continue to enhance the Capsule API and add additional resources, parameters and elements into responses, etc. Please ensure that your app is designed to handle additional elements that may be added to responses. We’ll always try to avoid breaking changes to existing resources on the API without notice.

31 May 2017

Starting on the 15 June 2017 we’ll be updating our SSL certificate as it is due to expire. As part of this change we’ll be changing our SSL certificate supplier to “Starfield” which means you’ll be using a different root certificate when connecting to Capsule.

Our new provider is widely supported so it’s unlikely that you’ll need to make any changes to your code or configuration. If you would like to test your code we have updated https://developer.capsulecrm.com with the new configuration and created a endpoint you can use to test your environment if you have any concerns.

Call the following URI using your code:

https://developer.capsulecrm.com/encryption-test.json

For example if were using CURL use the following command:

curl https://developer.capsulecrm.com/encryption-test.json

If successful you should see the following in the response from our servers.

{"test":"everything is ok"}

At the same we will be updating our cipher suite configuration based on the latest version of Mozilla’s Intermediate compatibility recommendation. We’ve made an additional tweak to remove support for older versions of Internet Explorer. We’ve monitored our logs and these dropped ciphers have not been used by integrations in the last 30 days.

10 April 2017

Updated Field Value Model docs to clarify the type of the value field.

27 January 2017

Updated developer console:

9 January 2017

On Monday 16 January we’ll be releasing an API update to prevent duplicate named organisations being created or being created by updating the name of an existing organisation using the API. This brings the API inline with the behavior of the Capsule web app. When a duplicate is caught you will get an HTTP/1.1 422 Unprocessable Entity error response like this:

HTTP/1.1 422 Unprocessable Entity
{
  "message": "Validation Failed",
  "errors": [
    {
      "message": "name must be unique",
      "resource": "party",
      "field": "name"
    }
  ]
}

When updating an existing organisation which is already a duplicate and you are not changing the contact’s name, the update will be applied successfully. If this creates an issue for your integration please contact us on support for help.

18 September 2015

Enabled rate limiting. We’ve ensured the new rate limits are set high enough to avoid breaking any existing integrations.