Issues with cdn.api.twitter.com

bfgigya · 2015-09-24T22:02:07.168Z

We’ve had a number of users reporting issues with latency when loading https://cdn.api.twitter.com/1/urls/count.json. It appears to no longer be happening but were there any known issues with the cdn.api.twitter.com domain today?

niall · 2015-09-25T00:42:56.316Z

The path you mention, /urls/count.json, is not a supported API product.

Twitter REST APIs are available at api.twitter.com. All APIs use authentication and the /1.1/ base path with the exception of the embedded Tweet oEmbed endpoint available without authentication at /1/statuses/oembed.

andypiper · 2015-09-28T10:01:29.281Z

No third party code should be calling any endpoints at urls.api.twitter.com or cdn.api.twitter.com - these have never been part of the supported public API and will shut down shortly. We are unable to help you with latency or any other questions related to those URLs.

For documentation on the public REST API see dev.twitter.com.

andypiper · 2015-09-28T10:01:33.093Z