Gmail API Credentials
New Campaign
Gmail API Connected
1 OAuth app(s) registered · 2 / 100 sender slots used
Registered OAuth Apps
New sender connections are auto-apportioned to the app with the most free slots
NameClient IDUsedLimit
Default 217859097084-046kq…tent.com 2 100
Safe to add/remove anytime. Existing senders store their own credentials and keep sending normally. Removing an app only stops it from being used for new connections.
How to Get Credentials
Google Cloud Console setup guide
1
Go to Google Cloud Console → APIs & Services → OAuth consent screen. Create or verify your app.
2
Go to Credentials → Create Credentials → OAuth client ID. Select Web application.
3
Under Authorised redirect URIs, add exactly: http://localhost:8080/oauth/callback
4
Click Download JSON. Upload that file here.
5
Enable the Gmail API in APIs & Services → Library for your project.
Add OAuth App
Upload a credentials.json from Google Cloud Console
Drop credentials.json here or click to browse
JSON file from Google Cloud Console
OR PASTE JSON
Apportioned automatically. Each connected Gmail account stores its own credentials independently. New senders are connected through whichever registered app has the most free slots.
← Back to Senders
Domain & SSL Setup
Point your domain to this VPS, then click Setup to install a free SSL certificate
HTTPS ACTIVE
Live App URL
https://mailengine.online
OAuth Redirect URI — add this in Google Cloud Console
https://mailengine.online/oauth/callback
After SSL is set up, update your Google Cloud Console Authorized Redirect URI from the HTTP to the HTTPS version.
Must already point to this server's IP
Used by Let's Encrypt for renewal notices