Developer Center
A documented API for every site
Each connected website gets its own credentials, a token-authenticated REST Content API and HMAC-signed rebuild webhooks today, with SDKs and GraphQL on the roadmap. Write credentials never touch the browser.
Example credentials — not your site
Every value on this page is a fictitious documentation placeholder. After you connect a website, your real, site-scoped credentials appear in the dashboard Developer Center — they are never shown to public visitors.
Site connection credentials Example
- Site ID
- site_EXAMPLE_0000
- Tenant ID
- tenant_EXAMPLE_0000
- API URL
- https://your-vibebackend-app.com/api/v1
- Public Read Token
- pk_EXAMPLE_public (browser-safe)
- Server API Credential
- sk_EXAMPLE_••• (server only, coming soon)
- Webhook Signing Secret
- whsec_EXAMPLE_••• (shown once when you add an endpoint)
A public read token is issued per site today. Server credentials, allowed-domain controls and self-service rotation are on the roadmap.
Environment variables
Add these to your hosting provider. Keep server tokens out of client bundles.
VIBEBACKEND_SITE_ID=site_EXAMPLE_0000 VIBEBACKEND_API_URL=https://your-vibebackend-app.com/api/v1 VIBEBACKEND_PUBLIC_TOKEN=pk_EXAMPLE_public
Example queries
# Fetch published pages for a site (read-only, token-authenticated). # Replace the example values with YOUR site's real credentials from # the dashboard Developer Center. curl https://your-vibebackend-app.com/api/v1/sites/site_EXAMPLE_0000/pages \ -H "Authorization: Bearer pk_EXAMPLE_public_read_token" # Single page by slug: curl https://your-vibebackend-app.com/api/v1/sites/site_EXAMPLE_0000/pages/home \ -H "Authorization: Bearer pk_EXAMPLE_public_read_token"
I already have a vibe-coded website.
Give it the backend it's missing.
Connect your site in minutes and hand your clients a professional CMS, forms and lead tracking — with SEO, media and more on the way, no redesign required.