# Oauth 2.0 Password Grant Flow Capability **URL:** \ **Category:** Nextworld Platform\ **Tags:** Integrations\ **Created:** [September 24, 2025, 9:54pm UTC](https://community.nextw.com/t/oauth-2-0-password-grant-flow-capability/1242 "2025-09-24T21:54:26Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![brandon1](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/brandon1/32/333_2.png) [@brandon1](https://community.nextw.com/u/brandon1)\ **Post date:** [September 24, 2025, 9:54pm UTC](https://community.nextw.com/t/oauth-2-0-password-grant-flow-capability/1242/1 "2025-09-24T21:54:26Z")
Hello - We are working with a customer that required OAuth2.0 password grant flow (grantype=password) with the following fields (from docs): curl --request POST –url http://api\_url.com/api/token –header “Content-Type: application/x-www-form-urlencoded” –data grant\_type=password –data username=XXXXXX –data password=xxxxxxx –data domain=XXXX –data client\_id=XXXXX –data client\_secret=XXXXX (optional) Is there anyway in Nextworld to configure a token endpoint using grant\_type=password? We also tried setting the content-type to an endpoint as application/x-www-form-urlencoded and passing the form fields in the body of the request. But that seems to only send as a JSON? Thanks! ---
**Author:** ![ian.p](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/ian.p/32/427_2.png) [@ian.p](https://community.nextw.com/u/ian.p)\ **Post date:** [September 25, 2025, 2:10pm UTC](https://community.nextw.com/t/oauth-2-0-password-grant-flow-capability/1242/2 "2025-09-25T14:10:17Z")
I did some looking back to when this had previously come up in the past and to send a `application/x-www-form-urlencoded` request what I’ve seen is you specify those keys as query parameters instead of putting them in the request body, and leave the request body empty.