Hi everyone,
I’m looking into the “Log Export API” feature mentioned in the June 3, 2026 release notes:
“Higher tier plans can now poll for and download app log files directly via secure, time-limited download links — no cloud storage setup required — making it easier to monitor activity and troubleshoot issues programmatically.”
I am interested in using this for programmatic monitoring and troubleshooting, but I’m having trouble locating where this is configured or how to access the API endpoint.
Could anyone clarify:
-
Where can this feature be accessed within the editor or API settings?
-
Is this strictly limited to specific tiers ? I want to make sure I’m not missing it due to my current plan level.
Any documentation links or pointers on how to get started would be greatly appreciated. Thanks in advance for your help!
This isn’t public yet (I think it’s in the release notes by mistake) but I’m under the impression it’ll be available on Growth plan and above.
You’d need to set up your own ingestion flow which can be a bit tricky, but if your priority is to connect to your Bubble logs more efficiently, then Buildprint might be useful
It gives you the logs / observability you’re looking for as well as monitors which alert you to log events!
Thanks for the quick reply Georges!
I’m actually already using Buildprint and it’s a fantastic tool for me as a professional Bubble developer managing multiple client apps.
However, for this specific use case, I’m looking for something a bit different. I’d like to surface specific audit logs directly within my client’s admin interface. For example, they want to be able to see: “Which user updated this specific field, and when?”
I’ve considered building a custom logging system using a dedicated data type, but that gets time-consuming and heavy to maintain across multiple modules. My goal was to leverage Bubble’s native logs directly via this API to feed that data into their dashboard without having to manually log every single field change. If this API becomes available, it would be a huge time-saver for these types of audit requirements.
I’ll keep an eye out for any official documentation once it’s released. Thanks again for your insights!
For this, you’d need to manually track those with a log data type. Whenever a user does something you want to track, in the workflow, Create a new Log, probably with content, User, date, and Type fields.
Exactly, that’s the ‘classic’ way I would have handled it as well. However, when I saw that mention in the June 3rd release notes about programmatic access to app logs, I was really hoping there might be a way to bypass that manual ‘custom logging’ setup.
Implementing a custom log data type for every single field update across multiple tables is quite resource-intensive, so I was optimistic that the new API could provide a more native and scalable way to surface that audit trail directly to the end-user.
I’ll keep waiting for the official documentation!
