# Exporting automations, app sources and whiteboards via API
**URL:** https://community.fibery.io/t/exporting-automations-app-sources-and-whiteboards-via-api/11241
**Category:** Get Help
**Created:** [September 2, 2026, 1:31pm UTC](https://community.fibery.io/t/exporting-automations-app-sources-and-whiteboards-via-api/11241 "2026-09-02T13:31:08Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@ID.000](https://community.fibery.io/u/ID.000)
#### Post date: [September 2, 2026, 1:31pm UTC](https://community.fibery.io/t/exporting-automations-app-sources-and-whiteboards-via-api/11241/1 "2026-09-02T13:31:08Z")
Hi Fibery Team 🙂 ,
We’re setting up a scheduled backup of our workspace to storage outside Fibery. The idea is simple: if we ever lose access to Fibery for any reason, we still have our own copy.
The HTTP API covers most of what we need — schema, entities, views, files and history all work well. The history endpoint is especially good, it gives old and new values for every change.
Three things we can’t get:
**1. Automations.** Rules, buttons and validation rules don’t seem to be available in the HTTP API. We can read them through the MCP server, but that needs a person in the loop, so it can’t run on a schedule. Is there an endpoint for this, documented or not? Or is it planned?
**2. Custom App sources.** The `get-source-files` endpoint works nicely, but the dev token only comes from the MCP tool and is short-lived. Is there a REST way to get that token, so a scheduled job could pull app sources on its own?
**3. Whiteboards.** We couldn’t find any way to export whiteboard content. Saving a board as a template helps inside Fibery, but not for an external copy. Is there a way to get the content out?
We know automations now have version history and that apps are included in Space Templates — both are very welcome. But those live inside Fibery, and we’re specifically covering the case where Fibery itself is unavailable.
If some of these aren’t possible today, that’s a useful answer too — we’d just like to know so we can plan around it.
Thanks!
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [September 2, 2026, 1:41pm UTC](https://community.fibery.io/t/exporting-automations-app-sources-and-whiteboards-via-api/11241/2 "2026-09-02T13:41:15Z")
> [@ID.000](#):
>
> Rules, buttons and validation rules don’t seem to be available in the HTTP API. We can read them through the MCP server, but that needs a person in the loop, so it can’t run on a schedule. Is there an endpoint for this, documented or not? Or is it planned?
If you inspect the network when navigating to an automation on the UI, you will see various http calls where the response includes details about the automations, e.g.
`https://myworkspace.fibery.io/api/automations/auto-rules/for-type/83db18f5-b335-410e-ab11-6824ec18ad97`
Of course, it’s not official, and comes with no guarantees
---
### Author:  [@ID.000](https://community.fibery.io/u/ID.000)
#### Post date: [September 2, 2026, 1:51pm UTC](https://community.fibery.io/t/exporting-automations-app-sources-and-whiteboards-via-api/11241/3 "2026-09-02T13:51:48Z")
Thanks a lot for the quick reply — as always, extremely helpful! 🤩
That’s exactly the hint we needed. We’ll inspect the network calls in the UI and see what else is exposed there for buttons and validation rules.
One follow-up, if you don’t mind: does that endpoint work with an API token, or only with a browser session? For a scheduled job we’d need token auth, so that’s the deciding factor for us.
And fully understood that it’s unofficial with no guarantees — we’ll treat it as best-effort and make our job alert us if it ever stops returning data, rather than silently writing an empty file.
Thank you!
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [September 2, 2026, 2:05pm UTC](https://community.fibery.io/t/exporting-automations-app-sources-and-whiteboards-via-api/11241/4 "2026-09-02T14:05:00Z")
> [@ID.000](#):
>
> does that endpoint work with an API token
Should do 🤞