# 422 Unprocessable Entity when doing put to required\_configuration **URL:** \ **Category:** Extensions\ **Created:** [September 12, 2017, 12:12pm UTC](https://staging-discuss.dev.twitch.com/t/422-unprocessable-entity-when-doing-put-to-required-configuration/11938 "2017-09-12T12:12:51Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [September 12, 2017, 12:32pm UTC](https://staging-discuss.dev.twitch.com/t/422-unprocessable-entity-when-doing-put-to-required-configuration/11938/6 "2017-09-12T12:32:29Z")
Your payload is not: ``` '{"required_configuration": "A STRING"}' ``` Your payload is a bad object. You shouldn’t be storing the configuration like this… You need to store the configuration in your EBS and just store a “yay/nay” string in the PUT See also: > [@Explanation of how configuration works?](https://staging-discuss.dev.twitch.com/t/explanation-of-how-configuration-works/11860/4): > > Nah you can do it now, that trello card is about storing the configuration in question twitch side. You can store the configuration you want in your EBS, provide a form in a config panel that collects SteamID and store wthat with the channel ID. When you have both then you tell Twitch Extension API all is good. For example: Results in: So Casters goes to config, which Posts back to your EBS. Then you do use: And call: PUT [https://api.twitch.tv/extensions/](https://api.twitch.tv/extensions/)//required… --- _[View the full topic](https://staging-discuss.dev.twitch.com/t/422-unprocessable-entity-when-doing-put-to-required-configuration/11938)._