Free · two minutes · no email required
Will the Base44 API key change break your apps?
Does anything outside Base44 call your apps?
A script, a spreadsheet, an automation, a CI pipeline, or another app.
What changes on 15 October 2026
Account API keys stop working. They are replaced by personal access tokens, created per workspace under Settings → Secrets, and the header changes from api_key: KEY to Authorization: Bearer TOKEN. You replace the whole header line — a token sent under the old header name is rejected.
Verified against Base44's documentation on 15 September 2026. Base44 is changing things during this transition, so if something here does not match what you see on screen, what is on screen wins.
Reasonable questions
What exactly is changing?
Base44 is replacing account API keys with personal access tokens. From 15 October 2026 an account API key no longer works. Anything outside Base44 still sending the old api_key header stops that day.
Does this affect my app itself?
No. Your app's own sign-in and its front end are unaffected. The change hits calls made from outside Base44 with an account API key — scripts, spreadsheets, automations, CI pipelines and other apps.
Is there a grace period after the deadline?
Base44 has not announced one. The safer assumption is that a nightly job fails at 03:00 on 15 October with no warning and nobody notices until data is missing.
Can I start now without breaking anything?
Yes, and you should. The old key keeps working until the deadline, so you can create a token, move one integration, test it, and leave the rest alone. Nothing has to break.