You may need to update how you are using the SendHub API because of two important updates taking place on 02/09/2016 after 5:00p.m. PST. These updates are:
- Resources pulled from our API will no longer contain trailing slashes in their path (more details below)
- Total_count is going away from the "meta" attributes of all list endpoints
Resources pulled from our API will no longer contain trailing slashes in their path
For example, a contact resource will now look like:
Note: This only impacts the "resource_uri" property of the json that is returned, not the uri you use to send requests to.
This will impact all API endpoints that return any sort of resource uri in their body. This includes, but is not limited to, inbox, threads, contacts, groups, etc...
We encourage customers to change their code to parse resource_uri values with or without the trailing slash. Most mainstream languages have uri parsing capabilities built in. One example of functionality that most languages commonly provide would be to get the last path component of a resource_uri to parse out the resource id. Using common libraries is preferred as they will in general be less fragile when it comes to parsing the uri. Regardless of what you choose, please be sure to test your code to make sure it works with and without the slash for your use case.