Firebase rest api proxy for webflow site
Firestore-backed Webflow dynamic content
You should not store Firebase credentials in Webflow client code. Firestore REST reads via edge with service token vault injection. RealComposer Secret Vault injects headers on Cloudflare Workers so only your edge URL is public.
Why Firebase rest api proxy for webflow site is hard without an edge proxy
Calling Firebase directly from Webflow risks leaked secrets, CORS blocks, or oversized JSON that slows rendering.
- Exposed API keys in Webflow bundles or DevTools
- Sequential upstream calls on slow mobile networks
- Third-party rate limits and surprise billing spikes
How RealComposer Solves This at the Edge
Store credentials in Secret Vault
Save FIREBASE_API_KEY in RealComposer.
Configure edge pipeline
Add upstream steps with vault header injection and map the response fields your client needs.
Call from Webflow
Use your workspace edge URL with a restricted client token.
const res = await fetch('https://realcomposer.com/v1/workspace/firebase-rest-proxy-webflow', {
headers: { Authorization: 'Bearer rc_live_client_token' }
});
const data = await res.json();
{
"status": 200,
"debug_trace": "trace_batch2",
"data": {
"id": "obj_batch2",
"status": "active",
"audit_logs": [
{
"action": "fetch",
"timestamp": 1714589200
}
],
"internal_metadata": {
"cluster": "edge"
},
"result": {
"name": "Sample",
"tags": [
"batch2"
]
}
}
}
{
"id": "obj_batch2",
"status": "active",
"result": {
"name": "Sample",
"tags": [
"batch2"
]
}
}
curl -X GET "https://realcomposer.com/v1/workspace/firebase-rest-proxy-webflow" \ -H "Authorization: Bearer rc_live_client_token"
Developer Questions & Troubleshooting
Is it safe to call Firebase from Webflow?
Only if secrets stay off the device. RealComposer injects credentials on the server edge so clients never hold production keys.
Does RealComposer add latency?
Cloudflare edge execution adds a few milliseconds; caching can answer repeat calls in under 10ms.
Deploy this Webflow + Firebase Recipe
Clone this pre-configured pipeline into your RealComposer workspace in one click. We pre-populate upstream URLs, headers, and mapping rules.