Create a key in any site's API tab. Every request: Authorization: Bearer dc_live_…. JSON in, JSON out. Rate limit 600/min.
Put a DonCloud widget on a site we don't host (Wix, WordPress, a link page): <script src="https://doncloud.com/runtime/embed.js" data-site="your-slug" data-widget="booking" defer></script>. Same widgets as above. Leads, bookings and orders land in the owner's dashboard.
An app is an https page or script that uses /v1 with the key DonCloud issues when an owner installs it. Submit from your dashboard (POST /api/apps/submit with {id, name, tagline, url, scopes, price_cents, categories}). You keep 70% of the price. Scopes: read, write, leads, bookings, payments, credit.
The engine composes sites from sections in templates/sections/<id>/. A section is two files:
Template syntax: {{KEY}} escaped, {{{KEY}}} raw, {{#if KEY}}…{{/if}}, {{#each LIST}}…{{/each}} with {{this}} or item fields. Use the CSS variables from luxury.css (--bg, --fg, --accent, --muted, --line) so every palette works. No <script> tags. Submit with POST /api/engine/sections/submit {id, name, category, families, needs, html}; the library is public at GET /api/public/engine/sections. Approved sections are credited to you on every site that uses them.
GET /api/public/dataset (JSON) or ?format=csv. Median and average service prices and review stats by city and category, min 3 businesses per cell. CC BY 4.0.
GET /api/search?q=… streams Server-Sent Events: results → token* → answer → done. Add &stream=0 for one JSON response. Anonymous: 20/day per IP; send your user token for unlimited.
Add an HTTPS endpoint in the API tab. We POST {event, site_id, created_at, data} with headers X-DonCloud-Event and X-DonCloud-Signature: t=<unix>,v1=<hex> where v1 = HMAC_SHA256(secret, t + "." + body). Retried up to 5 times; an endpoint is paused after 50 failures.
Use a "Webhooks by Zapier → Catch Hook" trigger as your endpoint URL, and "Webhooks → POST" with your API key for actions. A native Zapier app uses these same endpoints.
A signed-in DonCloud user calls POST /api/sso/token {audience} and receives a 5-minute token. Your app verifies it with POST /api/public/sso/verify {token} → {user:{id,email,name}, audience}. Share the same SSO_SHARED_SECRET across ITLTube, Buildroom and DonForge for offline verification (HMAC-SHA256 over the base64url payload).
Any page on a DonCloud site can mount widgets with data-dc="booking|estimate|reviews|pay|plans|locations|team|lang|menu|specials|order|loyalty|hours|waitlist|tip". Public per-site JSON is at /s/<slug>/config.