# Return all parameters from oauth2 authorization code response

**URL:** <https://community.fibery.io/t/return-all-parameters-from-oauth2-authorization-code-response/7853>\
**Category:** API & Programming\
**Created:** [November 25, 2024, 12:18am UTC](https://community.fibery.io/t/return-all-parameters-from-oauth2-authorization-code-response/7853 "2024-11-25T00:18:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tommy\_Hedley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tommy_hedley/32/6468_2.png) [@Tommy\_Hedley](https://community.fibery.io/u/Tommy_Hedley)\
**Post date:** [November 25, 2024, 12:18am UTC](https://community.fibery.io/t/return-all-parameters-from-oauth2-authorization-code-response/7853/1 "2024-11-25T00:18:30Z")

</div>

I’ve run into an issue while developing a Quickbooks Online integration using the Custom Integration API. Since the Quickbooks oauth2 flow allows for a range of companies to be selected in the web UI for authorization, the authorization code response contains the **realmId** (company id) of the particular company that the user selected.

**Example Authorization Code Response**

```auto
https://www.mydemoapp.com/oauth-redirect?
    code=4/P7q7W91a-oMsCeLvIaQm6bTrgtp7&
    state=security_token%3D138r5719ru3e1%26url%3Dhttps://www.mydemoapp.com/oauth-redirect&
    realmId=1231434565226279

```

Currently it seems that only the **code** and **state** are taken from the authorization code response and used for the token request body. Would it be possible to return the response parameters dynamically so that the **realmId** and other potential response values can be used?

---

<div class="post-metadata">

**Author:** ![Tommy\_Hedley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tommy_hedley/32/6468_2.png) [@Tommy\_Hedley](https://community.fibery.io/u/Tommy_Hedley)\
**Post date:** [November 25, 2024, 5:19pm UTC](https://community.fibery.io/t/return-all-parameters-from-oauth2-authorization-code-response/7853/2 "2024-11-25T17:19:46Z")

</div>

Fibery team managed to fix it in about 4 hours, absolutely the best!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 26, 2024, 7:36am UTC](https://community.fibery.io/t/return-all-parameters-from-oauth2-authorization-code-response/7853/3 "2024-11-26T07:36:24Z")

</div>


