# Webapp, API and Playground Different Results

**URL:** <https://community.openai.com/t/webapp-api-and-playground-different-results/767343>\
**Category:** API\
**Created:** [May 20, 2024, 4:16pm UTC](https://community.openai.com/t/webapp-api-and-playground-different-results/767343 "2024-05-20T16:16:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![\_j](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/_j/32/766292_2.png) [@\_j](https://community.openai.com/u/_j)\
**Post date:** [May 20, 2024, 4:30pm UTC](https://community.openai.com/t/webapp-api-and-playground-different-results/767343/3 "2024-05-20T16:30:55Z")

</div>

I can demonstrate basically getting the same results, yesterday:

> [@Incomplete Output of 4o through API](https://community.openai.com/t/incomplete-output-of-4o-through-api/764250/2):
>
> First, you can press the ‘view code’ button to ensure you have the correct parameters. Then despite those, crank the max\_tokens value you can receive as output way up. You can see my truncation at 128 tokens. Then look at the finish\_reason in the response. If it is “stop”, the AI just decided to stop writing. Another oddity about this model is that specifying temperature and top\_p values too low is not just a setting to zero, it a setting to “useless”. The parsing of negati…

You are sending to the same AI model. The only thing that might be different is the parameters you set, or the natural variation between responses when not constraining the outputs with temperature or top\_p.

You are not the only one not using the API the same way as the playground sends.

---

_[View the full topic](https://community.openai.com/t/webapp-api-and-playground-different-results/767343)._