# Using choice interface with pre-set options **URL:** \ **Category:** Uncategorized\ **Tags:** usage, front-end, solved\ **Created:** [April 24, 2018, 12:58pm UTC](https://support.prodi.gy/t/using-choice-interface-with-pre-set-options/508 "2018-04-24T12:58:34Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [April 24, 2018, 1:01pm UTC](https://support.prodi.gy/t/using-choice-interface-with-pre-set-options/508/2 "2018-04-24T13:01:33Z")
Yes, that's possible – see my answer here for details: > [@Pre-defined choice in Choice interface](https://support.prodi.gy/t/pre-defined-choice-in-choice-interface/474/4): > > Ah, okay, got it. In general, the best strategy to achieve these kinds of things in Prodigy is to just feed it input of the same format as the expected output. That’s also how it works for NER and other interfaces. For the choice interface, this means including an "accept" key with a list of accepted options, just like the annotation format you expect it to produce in the database. For example: "accept": [1, 4] The "choice" currently doesn’t “officially” support this, so it likely won’t update… As of Prodigy v1.4.2, it should also work as expected for the very first question! --- _[View the full topic](https://support.prodi.gy/t/using-choice-interface-with-pre-set-options/508)._