Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Amy Preci](https://secure.gravatar.com/avatar/a0431d0e8e302b85e3fd2cc65aba247b?s=96&d=https%3A%2F%2Fecs-static.teamtreehouse.com%2Fassets%2Fcontent%2Fdefault_avatar-445fbbabfc8dc9188fb5967fe43322ee0c3e0dd1e10f378bf8343784af5a13eb.webp&r=pg)
Amy Preci
6,247 PointsWhy didn't we need to use async/await in this workshop at all? I often see it used with fetch.
Just wondering! I often get confused as to when async/await is needed and not needed when fetching external data like from an API.
1 Answer
![Steven Parker](https://uploads.teamtreehouse.com/production/profile-photos/969492/micro_tool_chess_set_2.jpg)
Steven Parker
230,688 PointsLike many things in programming, there is often more than one way to accomplish the same thing. Since fetch is asynchronous by nature and returns a Promise, you can chain then methods to run at the moment of resolution instead of using await and coding the response in a separate statement. Both approaches are perfectly valid.
Another reason that await might have been avoided in this workshop is so it can be used by students who have not yet taken the Asynchronous Programming course.