This is placeholder copy for a landing page aimed at developers. Use the pages content collection in src/content/pages/ to build out vertical-specific landing pages — one per audience, one per use case, or one per feature.
What works for engineers
The Acme API is the same one the dashboard runs on. There’s no second-class API surface — everything you can do in the UI, you can do programmatically.
- REST, not RPC. Predictable URLs, standard HTTP verbs, and structured errors. If you’ve used Stripe’s API, you’ll be at home.
- Webhooks for every event. Get notified when state changes instead of polling. Signed payloads, automatic retries, replay support.
- SDKs that don’t lock you in. Open-source, type-checked, generated from the OpenAPI spec. Switch languages or write your own client whenever you want.
Quick example
curl https://api.example.com/v3/widgets \
-H "Authorization: Bearer your-api-token" \
-H "Content-Type: application/json" \
-d '{"name":"My widget","colour":"blue","quantity":12}'See the API documentation for the full reference.
Replace this page
This is one of three demo pages the starter ships with. Open src/content/pages/ to see them all — and overwrite or delete each one as you build out your own pages.
Frequently asked questions
Which languages do the SDKs cover?
Node, Python, Ruby, and Go are first-class. The OpenAPI spec is published so you can generate clients for any other language.
Are webhooks reliable?
Yes. We retry failed deliveries with exponential backoff for up to 24 hours, and all deliveries are signed so you can verify they came from us.
Is there a sandbox?
Every API token is scoped to a project, so you can create a separate sandbox project for testing. There's no separate sandbox environment.