# Support PATCH on Environment API

**URL:** <https://community.postman.com/t/support-patch-on-environment-api/1516>\
**Category:** Help Hub\
**Created:** [May 2, 2018, 12:43am UTC](https://community.postman.com/t/support-patch-on-environment-api/1516 "2018-05-02T00:43:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![garethj](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/garethj/32/576_2.png) [@garethj](https://community.postman.com/u/garethj)\
**Post date:** [May 2, 2018, 12:43am UTC](https://community.postman.com/t/support-patch-on-environment-api/1516/1 "2018-05-02T00:43:23Z")

</div>

Using PUT is really tedious on the Postman API as I have to pull the entire object, modify it in script in the json, then compose a PUT and do an asynchronous PUT back,

All of this when I just wanted to update one property (An OAUTH REFRESH token in an environment).

I so often feel like I’m jumping through hoops building infrastructure with postman where you guys don’t prioritize usability for complex cases but are satisfied when something becomes just about possible.

I really just want pm.environment.Update() in script and have you guys do all this work behind the scenes, but PATCH and explicit \_\_id properties on the pm.environment object would at least make it less custom setup and code.

---

<div class="post-metadata">

**Author:** ![danny-dainton](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/danny-dainton/32/29401_2.png) [@danny-dainton](https://community.postman.com/u/danny-dainton)\
**Post date:** [April 29, 2025, 3:54pm UTC](https://community.postman.com/t/support-patch-on-environment-api/1516/2 "2025-04-29T15:54:11Z")

</div>

Closed on April 29, 2025, 3:54pm UTC


