Skip to main content
Quick answers to the questions that come up most while you set up and run a white label integration. Each answer links to the page with the full details.

​
Plans and access

White label is open to workspaces on the Builder plan and above, and everything on Builder runs on a personal access token alone. Some features need the Enterprise plan:
No. On the Builder plan and above, White label is already in your workspace settings.
The White Label Terms, on top of the Base44 Terms of Service. You accept them when you turn on white label, in the app or with the API.
A workspace owner or admin. The Admin role is only available on Enterprise, so on other plans the workspace owner makes these changes. See roles and their limits.
Yes. Paste this message into the AI chat of the app you’re adding app building to, such as in the Base44 app editor, or into a coding agent such as Claude Code, Cursor, or Codex, opened on your platform’s project: Set up Base44 white label in my app so my users can build apps under my brand. Use this guide: https://docs.base44.com/developers/white-label/setup/SKILL.md The agent works through every step, from credentials to a tested integration, and checks each one before moving on. A chat assistant that can’t edit code can’t run it. You can also copy the prompt, with your workspace ID already in it, from White label → Settings in your workspace settings. See use a coding agent.

​
Credentials

A personal access token for the account your integration builds as. It works on every plan, and authenticates every Apps API call, including the ones that sign end users in to an embedded app and open live build updates. If your plan includes workspace API keys, you can use one instead for embedding and live updates. See tenancy and credentials.
The workspace your integration builds in, not the account’s personal workspace. A token only reaches the workspace it was created in, so a token from the personal workspace misses your design system, skills, and plan. Give it All apps and Superagents access and Full access permission.
No. From October 15, 2026, account API keys no longer work, and personal access tokens replace them. Create a token, then send it as Authorization: Bearer <token> instead of api_key: <key>. See moving from account API keys.
Open the workspace in Base44, then open the workspace menu at the bottom left and click Settings. The workspace ID is the string of characters after /workspace/ in the browser’s address bar. The main Apps page address doesn’t include it. You can also run base44 workspace list in the Base44 CLI.
No. Every call to Base44 goes through your own backend. Keep tokens and keys in your server’s environment, and never send them to the browser or show them to your builders.

​
Builders and their apps

No. One Base44 account sits behind your whole integration and owns every app your builders create. Your builders sign in to your platform, not to Base44. See who owns the apps.
Base44 sees one account behind every build, so it can’t tell your builders apart. Record which builder created each app in your own database, and check it before every call that names an app. See tenancy and credentials.
No. Set custom_instructions when you call Create app. Only the first 10,000 characters are sent to the agent. See custom instructions.

​
Brand and system prompt

Yes. With a personal access token from a workspace owner or admin, or a workspace API key if your plan includes them, you can turn white label on, set your brand and agent names, and turn on Use design system with the white label settings endpoint. On Enterprise, the same endpoint sets your own system prompt. You can also set up your design system and your workspace skills with the API.
Every app built or edited in your workspace, once white label is on. New apps follow them from the first build, and existing apps from their next build turn. When you turn white label off, apps go back to Base44 from the next message. See set your brand.
No. To put your name on the agent, set your brand. Writing your own system prompt is optional, needs Enterprise, and replaces the guidance the agent uses to build with Base44’s database, sign-in, and backend functions.
While white label is on, apps use your default design system only when Use design system is also on, in the Design system card of your white label settings. See set your design system.
From the next build turn, including the next turn in a conversation that’s already under way.

​
Builds

The agent may be waiting on a question. It can stop and wait indefinitely for an answer, and nothing else moves until you send one. Check the transcript for a tool call whose status is waiting_for_user_input. See the build turn.
A build turn takes from around thirty seconds to several minutes, so a 30-second client timeout cuts working builds off. Allow at least 120 seconds for Create app, Send chat message, Submit tool-call input, and Deploy an app. Before retrying, check whether the app or message already exists.
App creation is capped at 5 requests per minute. Queue bursts instead of sending them in parallel.
Yes. Every build turn draws on your workspace’s credits. Send the same X-Request-ID when you retry a request, so a retry isn’t charged twice.

​
Embedding

Check your workspace’s embedding policy. If it’s set to Only these sites, add your platform’s website to the list. With No one, no website can embed your apps.
The email belongs to the app’s owner, an editor, or a service account, including the account your integration builds as. Sign-in tokens are for end users only. See embed the app.
Only for apps that ask people to sign in. An app set to Public (no login) loads directly, without a token. See deciding whether you need a token.