Lodgify Login — step-by-step
Signing into Blastnes is the same OAuth-style dance you use to sign into any modern app with your Google or Apple account, except the identity provider is Lodgify. The whole process takes under a minute the first time and is transparent thereafter. This guide walks through it and covers the five most common problems.
1. Click "Sign in with Lodgify"
From any page on Blastnes, click the Lodgify Login link in the top-right of the header. You'll be redirected to a Lodgify-hosted page at lodgify.com. This page is not on our domain — check the URL bar; it must show lodgify.com. If it doesn't, you are being phished; close the tab and start over from the Blastnes header link.
2. Enter your Lodgify email and password
Use the same email and password you use every day for your Lodgify site. If you don't remember the password, use Lodgify's own "Forgot password" link on that same page — do not come back to Blastnes for that; we do not manage your Lodgify credentials. If you have 2FA enabled on Lodgify (highly recommended), you'll then be prompted for the six-digit code from your authenticator app or SMS.
3. Review the consent screen
Lodgify will show a consent screen listing the API endpoints Blastnes wants to reach on your behalf. This list is derived from the modules you have added to your cart or already installed. Typical items: Bookings (read), Rates (read/write), Availability (read/write), Guests (read), Channels (read). Read them carefully — this is the moment you decide what Blastnes can and can't do on your Lodgify site.
4. Approve and be redirected back
Click Authorise and Lodgify sends you back to Blastnes with a scoped, revocable, 30-day rotating token. You never see the token itself — it's exchanged directly between the two systems. From that moment your modules are live.
5. (Optional) Enable 2FA on Blastnes itself
By default your Blastnes session lasts 30 days. If you want an extra layer, enable 2FA in your account under Security. This is independent from Lodgify's 2FA and adds a second challenge before sensitive actions like changing a payment method.
Five problems we hear most
Problem 1 — "Nothing happens when I click Sign in with Lodgify"
Almost always a browser popup blocker or an ad-blocker. Whitelist blastnes.org and lodgify.com in your extension settings and reload. Safari's Cross-Site Tracking Prevention sometimes interferes; try disabling it briefly for these two domains.
Problem 2 — "Lodgify says my API access is disabled"
Your Lodgify plan may not include Public API access. Starter, Professional, Ultimate and Enterprise all include it; a few legacy plans do not. Upgrade in Lodgify (Settings → Subscription) or contact Lodgify support to enable API access on your current plan.
Problem 3 — "Consent screen shows an endpoint I don't want to authorise"
You can decline that specific endpoint on the Lodgify consent screen. Blastnes will then flag the corresponding module as "insufficient permissions" and skip it. Everything else continues to work. If you want the module but only for a subset of your properties, contact support@blastnes.org — we can scope tokens per Lodgify unit ID on request.
Problem 4 — "I can't find the 2FA code"
That's a Lodgify-side recovery, not a Blastnes one. Follow Lodgify's own 2FA recovery flow on their help centre. Once you're back in on lodgify.com, come back to Blastnes and try again.
Problem 5 — "The colleague who set this up left the company"
If your ex-colleague's Lodgify account is still the one authorising Blastnes, revoke it from Lodgify (Settings → Integrations → Blastnes → Revoke) and re-authorise with a current employee's Lodgify account. Your Blastnes subscription, modules and billing history transfer automatically — nothing is lost. Alternatively, use the reset access form to send an activation link to a new email.