2. When you hover the cursor over the account name, you have the option to edit the account name.
3. Add a new name account name, enter the remaining credentials and click **Next**.
The new account gets successfully added without overwriting the existing account.
## Credentials Pane
This pane contains fields for entering credentials to connect to your JSON No Code OAuth account. The following table describes what is needed for each field:
| Field | Description |
|---|---|
| JSON-OAUTH Account | You can enter an account name of your choice. |
| Client ID | Client ID for your OAuth authentication. |
| Client Secret | Client Secret for your OAuth authentication |
| OAuth Type | If your API does not specify the type of flow it uses, look for the 'grant\_type' parameter required by the API to determine which flow to be used. |
| Authorization URL | API authorization endpoint. This is the endpoint used for the first call in the OAuth handshake. |
| Additional parameters for the authorization url API call (optional) | Add additional parameters required by your API to be used with the authorization URL (optional). |
| Access Token Url | This endpoint will return the access token used to authenticate other API calls. |
Additional parameters for the access token url API call | Add additional parameters required by your API to be used with the access token URL (optional). |
| Authorization type | When you use the authorization code flow, rarely you need to pass the client id and secret in the header. |
| Refresh Token Url | For most API, the refresh token url and the access token url are the same. Leave the input blank if this is the case. |
| Scopes (optional) | Enter the scopes needed for this connection (optional). Scopes are usually separated by a space. |
| State Type | Select the type of state required by your Oauth. (Rarely you need to modify this selection) |
| State Location | Select if you want to send the state as a query parameter or in the path. |
| Response Type | Select the response type you want to use with the authorization url (Rarely you need to modify this selection). |
| Use redirect uri when refreshing access token | Select whether the redirect URI needs to be passed to the API when refreshing the access token (this is rare). |
| Force token refresh on every run | Select this option if you want to refresh the access token for every run of the connector. This may be necessary if your token is regularly invalidated outside Domo, but this is rare. |
Menu | Description |
|---|---|
| Choose the HTTP Method to use | Choose from either GET or POST as the HTTP method. |
| Enter the URL to your JSON file | Enter the URL of your JSON file. |
| How will you provide the certificate | Choose the method in which the certificate will be provided:
|
| Menu | Description |
|---|---|
| HTTPS Headers | Enter the Key and Value of the HTTPS Headers. |
| Query Parameters | Enter the Key and Value of the Query Parameters. Specify whether you want to encode query parameters. |
| Date Query Parameters | Select No Date Filter, Single Date, or Date Range as the Date Query Parameter. |
| JSON Settings | Specify whether your JSON text requires a line reader and if the backslash character should be escaped. |