Where to Find Your Base44 App ID

How to find your Base44 App ID (and what it's for)

Every Base44 project has a unique App ID. Here's exactly where to find it — in the dashboard, in the URL, and in code — and what you'll need it for.

Your Base44 App ID is the unique identifier assigned to each project. Find it in your project dashboard under General Settings, or copy it from the workspace URL in your browser's address bar — it's the segment that identifies your app.

Last updated September 3, 2026

What the Base44 App ID is

Every project you create on Base44 is assigned a unique alphanumeric App ID at creation time. It never changes for the life of the project, and it is how Base44's systems — the builder, the hosting layer, the API, and support tooling — refer to your application internally. You will be asked for it when wiring up integrations, mapping a custom domain, talking to support about a deployment problem, or calling Base44-facing APIs from your own code. Think of it as your project's license plate: not a secret, but unique and stable.

Finding it in the dashboard

The most reliable place to find your App ID is the project dashboard. Open your project in the Base44 builder, then navigate to General Settings. The App ID is listed alongside the project name and creation date, with a copy button next to it. This is the canonical source — if a URL ever looks ambiguous, the value shown in General Settings is the one to trust.

Finding it in the project URL

When your project is open in the builder, look at the browser address bar. The workspace URL contains your App ID as an identifying segment, so you can copy it straight from the URL without opening settings at all. The same identifier also appears in your app's preview and production URLs once deployed. This is the fastest method when you just need to paste the ID into an integration form — but double-check you've copied the app segment and not a route or file path.

Using the App ID in code and environment variables

Generated apps sometimes need to know their own App ID — for example when calling a Base44 API endpoint or tagging analytics events. The recommended pattern is to store it as a runtime environment variable in the project's secrets or config panel and read it at runtime, rather than hardcoding the value into source files. That keeps the ID out of prompt history and makes it trivial to reuse the same codebase pattern across multiple projects. Never confuse the App ID with an API key: the App ID identifies your app, while API credentials authenticate requests — credentials belong in the secrets panel, always.

Custom domains and support requests

Two situations where you'll definitely be asked for the App ID. First, custom domain setup: when mapping your own domain, Base44's verification flow ties the DNS records to a specific App ID, so having it handy speeds up troubleshooting when TLS provisioning stalls. Second, support: if a deploy is stuck or an app is misbehaving, including the App ID in your first message to support skips an entire round-trip of 'which project is this?'.

Verifying app health with the App ID

When something looks wrong, use the App ID to scope your diagnosis. Check whether your specific app is reachable, then cross-reference platform-level status on status.base44.com or the live dashboard here on base44.health to tell a project-specific issue apart from a platform-wide incident. If the platform is green but your app is not, the problem is almost always in your project's generated code or its DNS configuration — and the App ID is the handle you'll use to dig further.

FAQ

Where do I find my Base44 App ID?

Open your project in the Base44 builder and check General Settings in the dashboard — the App ID is listed there with a copy button. You can also read it directly from the workspace URL in your browser's address bar.

Is the App ID the same as an API key?

No. The App ID identifies your project and is safe to share with support or paste into integration forms. API keys and tokens authenticate requests and are secrets — they belong in the per-project secrets panel and should never be shared or committed to code.

Does the App ID ever change?

No. The App ID is assigned when the project is created and stays constant for the life of the project, across renames, redeploys, and domain changes. If you duplicate a project, the copy gets its own new App ID.

Can I find the App ID without opening the builder?

Yes. It appears in your project's workspace URL, and in the preview and production URLs once the app is deployed. If you have the project bookmarked, the ID is in the bookmark.

Why does support keep asking for my App ID?

Because it's the fastest way to identify your exact project among everything on your account. Including the App ID in your first support message — along with a description of the issue — typically saves a full round-trip.

Do I need the App ID to connect a custom domain?

Not usually — the domain flow in Project Settings handles the association automatically. But if DNS or TLS verification stalls, support and troubleshooting docs will reference your App ID, so keep it nearby during setup.

Is the App ID secret?

No. It appears in URLs and is safe to share with collaborators and support. It grants no access by itself — authentication is handled separately by your account session and API credentials.

How do I check whether my app is down or the whole platform is?

First load your app's URL directly. Then check status.base44.com and the live dashboard on base44.health — if the platform checks are green but your app is unreachable, the issue is project-specific (generated code or DNS), and you'll troubleshoot it using your App ID.