> Seeing Invalid Redirect URL in RestoreCord? Add your bot's OAuth2 callback in the Discord Developer Portal, custom domain callbacks included, and verify again.

Source: https://restorecord.help/invalid-redirect-url

# Fixing Invalid Redirect URL on your RestoreCord bot

The bot card says Invalid Redirect URL and members hit an error after authorizing. One missing line in the Discord Developer Portal causes it, and here's exactly which one.

[Open Dashboard → Bots](https://restorecord.com/dashboard)[All setup fixes](https://restorecord.help/)

Short answer

Invalid Redirect URL means the callback shown on your bot's card in Dashboard → Bots isn't listed in your Discord application's OAuth2 redirects. Copy it from the card, add it under OAuth2 → Redirects in the Developer Portal and save. With a custom domain, the callback is your domain plus /api/callback.

## What the warning means

RestoreCord verification runs on Discord OAuth2\. A member clicks Verify, approves your bot on Discord's own screen, and Discord sends them back to a **redirect URL** with proof that they agreed. For safety, Discord only sends people back to addresses you've listed in your application's settings. If RestoreCord's callback isn't on that list, the member is stopped right after authorizing.

RestoreCord checks this for you and flags it on the bot card, which is why you can catch it before a single member complains.

## The fix

1. 1Open Dashboard → Bots and copy the callback shown on your bot's card.
2. 2Go to the Discord Developer Portal and select the application behind your bot.
3. 3Open the OAuth2 page and find the Redirects section.
4. 4Add the URL exactly as copied and save the changes.
5. 5Return to RestoreCord. The card should now read Valid Redirect URL.

## Which URL is the right one?

| Your setup                  | Callback to list in Discord                  |
| --------------------------- | -------------------------------------------- |
| Default RestoreCord address | https://restorecord.com/api/callback         |
| Custom or free domain       | Your domain followed by /api/callback        |
| Mid-switch between domains  | Both, until the new one is active and tested |

For a custom domain such as `verify.yourserver.gg`, the Redirects list ends up looking like this while you move over. Copying each line from the bot card is safer than typing it.

OAuth2 → Redirectstext

```
https://restorecord.com/api/callback
https://verify.yourserver.gg/api/callback
```

Small differences count. A trailing slash, http instead of https, or a space at the end makes Discord treat it as a different address.

## Moving to a new domain safely

Verify links already posted in your server point at the current address. When you move to a new domain, add the new callback in Discord **before** switching, and keep the old one listed until the new domain is active and you've tested it. Then republish your verification message with `/setup` so the Verify button uses the new domain.

## How it looks from a member's side

Members click Verify, approve your bot on Discord, and instead of landing back on your verify page they see a Discord error about the redirect. To them it looks like your server is broken, so most give up and leave without saying anything. That's why it's worth checking the bot card after any change to your bot, your domain or your Discord application, not only when someone complains.

## Setting up a new bot? Do it first

When you connect a new custom bot to RestoreCord, the setup shows the redirect URL to add alongside your token and client secret. Adding it there and then saves you from discovering the problem on the day your first members try to verify.

## While you're in the Developer Portal

* On the Bot page, check that Server Members Intent and Message Content Intent are enabled.
* If you regenerated the token or client secret, paste the new values into the bot's credentials in RestoreCord and save.
* After changing intents or credentials, use Restart Bot in Dashboard → Bots.

Members verifying but not getting a role is a separate problem with its own fix: [the bot's role position](https://restorecord.help/verified-role-not-given). If you also changed your domain, [republish the verification message](https://restorecord.help/verification-message-not-updating) so the button follows. Everything else is on the [RestoreCord Setup Help home page](https://restorecord.help/).

## List the callback in Discord

1. 1  
### Copy the callback  
Open Dashboard → Bots in RestoreCord and copy the redirect URL shown on your bot's card.
2. 2  
### Open your application  
In the Discord Developer Portal, select the application behind your bot and open OAuth2.
3. 3  
### Add it under Redirects  
Paste the URL exactly as shown, without extra slashes or spaces, and save the changes.
4. 4  
### Check the bot card  
Back in RestoreCord, the warning should change to Valid Redirect URL. Verify with a spare account to be sure.
[Bot management in the RestoreCord docs](https://restorecord.com/docs/guides/bot-management)

## Redirect URL questions

### 

### 

### 

## Callback listed, verification flowing

Once Discord knows where to send members back, RestoreCord takes care of roles, backups and protection on every verification.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
