# Old spark.io API calls generating error

**URL:** <https://community.particle.io/t/old-spark-io-api-calls-generating-error/30487>\
**Category:** Cloud\
**Created:** [March 14, 2017, 4:01am UTC](https://community.particle.io/t/old-spark-io-api-calls-generating-error/30487 "2017-03-14T04:01:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrickcentral](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/patrickcentral/32/3723_2.png) [@patrickcentral](https://community.particle.io/u/patrickcentral)\
**Post date:** [March 14, 2017, 4:01am UTC](https://community.particle.io/t/old-spark-io-api-calls-generating-error/30487/1 "2017-03-14T04:01:14Z")

</div>

The right solution to this, of course, was for me to go update a bunch of webapps to **not** use a deprecated URL…HOWEVER 😄

In case anyone else is getting ERR\_INSECURE\_RESPONSE errors on some of their older projects, it seems the cert has expired on [spark.io](http://spark.io). Changing it to [particle.io](http://particle.io) worked great, but required digging up some code I haven’t touched in a while.

Particle folks, dunno what your end of life plan for that domain is, but I guess this could also be a heads up for you.

---

<div class="post-metadata">

**Author:** ![kennethlimcp](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kennethlimcp](https://community.particle.io/u/kennethlimcp)\
**Post date:** [March 14, 2017, 5:03am UTC](https://community.particle.io/t/old-spark-io-api-calls-generating-error/30487/2 "2017-03-14T05:03:48Z")

</div>

@jgoggins