Requesting changes to Oauth credentials
Requesting credential changes.
Changes to the credentials can be requested by the credentials owner. The possible changes that can be requested are:
- Scopes. Add new scopes, change the access level of existing scopes, or remove scopes.
- Redirect URLs. Replace the existing redirect URLs, or add new ones to the existing URLs.
- Application name.
- Application author (the company name displayed during authentication).
Changes to the contact person are not part of the form. If the contact person has changed, reach out to [email protected].
Only validated contact persons on the credentials can request changes. The contact e-mail entered in the form must belong to the contact person saved on the credentials. All requests from non-valid people will be denied, and the requester will be notified by e-mail.
Sending the request.
To request a change to existing credentials, use the form below:
Select the correct environment.Make sure the environment you select matches the environment of your client ID. If the environment does not match, the change request will be denied and you will be notified by e-mail.
How to fill out the form.
- Your information. Enter your name, your contact e-mail, the client ID of the integration and the environment it belongs to. The client ID is 32 characters long.
- What to change. Select everything that applies. You will only be asked about the changes you select.
- Application name or author. Fill in only the values that should change. Leave a field empty to keep the current value.
- Redirect URLs. Choose whether the URLs you enter should replace all existing redirect URLs, or be added to them. You can enter up to five URLs. Parameters are not supported in redirect URLs, but sub-URLs are.
- Scopes. For every resource, choose the access you want the application to have afterwards. You do not need to know what the application has today.
- Review and submit. Check the summary of your requested changes, use Edit to go back and change something, and submit the request.
Changing scopes.
For each resource, one of the following can be selected:
| Choice | Result |
|---|---|
| No change | The resource is left as it is. This is the default. |
| READ only | The application gets read access to the resource. |
| FULL | The application gets full access to the resource, including read. |
| Remove access | The application loses access to the resource. |
The same choices are used whether you are adding a new scope, upgrading or downgrading an existing one, or removing it. For example, selecting FULL for a resource gives the application full access, regardless of what it had before.
Some resources share underlying permissions, so a change to one resource can affect another. If you are unsure what a change will mean for your application, mention it when contacting support.
Updated 2 days ago