Editing an Approved App

After an app is approved, the Settings tab lets you change most of what you submitted. Some changes apply immediately. A scope change goes through review again, and the app keeps serving merchants on its current scopes until that review finishes.

What You Can Change

Setting	Card	Review needed?
App logo, support email, app URL, privacy policy URL, terms of service URL, launch URL, "What does your app do?"	App details	No. The card says These save straight away — no review needed.
Redirect URIs	Redirect URIs	No. The card says These save straight away — no review needed.
Scopes, and the write scope justification	Scopes	Yes. A scope change needs a review before it goes live.
App name, provider id		Cannot be changed after approval.

Editing App Details

1. Open the app, then the Settings tab, card App details.
2. Change the fields. The same checks as the submit form apply: https:// URLs, a valid support email, and a description. App name is disabled.
3. Click Save details. You see App details updated.

Editing Redirect URIs

1. In the Redirect URIs card, edit, remove, or Add another redirect URI. The rules match submission: exact https:// URIs, no fragment, no wildcards, and http://localhost for development. http://127.0.0.1 is rejected.
2. Click Save redirect URIs. You see Redirect URIs updated.

🚧

Removing a Redirect URI Breaks Flows That Still Use It

An authorization request is accepted only for a redirect URI listed here. Add the new URI and deploy your change before you remove the old one.

Requesting a Scope Change

1. In the Scopes card, select or clear scopes. If any :write scope is selected, fill in Write scope justification. Adding a write scope shows: You are adding a write scope: write scopes let your app push data into merchants' Triple Whale accounts, so they get a closer look during review.
2. Click Submit change request. The button is enabled only when the scope list actually changed. You see Change request submitted for review.

While the request is open:

• The status badge reads In review. The detail page shows Waiting for review with a before/after diff of the scopes, plus your justification under Why you need write access.
• The alert explains that the app stays active on its current configuration and keeps serving merchants. You cannot submit another change until this one is approved or rejected. If it is rejected, the app keeps what it has today.
• The settings cards stay locked until the review finishes.

When the request is approved, the new scopes go live on your OAuth client. The decision and the diff are recorded on the Activity tab. Merchants who connected before the change keep the scopes they originally granted until they reconnect.

Who Can Edit

Owner and Admin can edit and submit change requests. A Member sees a read-only Submitted details summary instead of the editable cards. See Managing App Members.

Best Practices

• Batch scope changes. Only one change request can be open at a time.
• Update the privacy policy URL and support email as soon as they change. Merchants see them, and the save takes effect immediately.