Skip to main content


Optimizely CMS: Content Delivery API – The Case of the Duplicate API Refresh Token

A man and woman collaborating and discussing work on a computer

A couple of weeks ago I came across an interesting case where a mobile app was calling into the Content Delivery API to retrieve some data, but the calls would fail with a 406 HTTP Status Code.  After some investigation, we found that the duplicate refresh tokens were being added to the system.  Revoking the tokens would temporarily fix the issue. But often we would need to revoke the tokens again a couple of hours later.

Read my blog article on BuildOptimizely to see the final solution





David Lewis, Director - Optimizely CMS

More from this Author

Follow Us