The platform is in public beta — this covers the conventions every Bakaify API follows. Product-specific references ship with each product's GA.
Beta: API access is currently granted on request. Contact us with your use case and we'll set you up.
Bakaify products share one platform: a unified account, consistent API conventions, and the same security model everywhere.
Every product currently in public beta is available from the products page. Coming-soon products accept waitlist signups and we notify you the day access opens.
All Bakaify APIs are JSON-over-HTTPS. Requests use standard verbs (GET/POST/PATCH/DELETE), responses always include an explicit status code, and errors return a machine-readable shape: { "error": string }.
Rate limits apply per IP and per API key. Exceeding them returns 429 with a Retry-After header. Write endpoints validate against strict schemas — unknown fields are rejected, not ignored.
Public API keys are scoped per product and per environment (test/live). Keys are passed via the Authorization: Bearer header — never in URLs.
Per-product API access ships with each product's general availability. During beta, integration access is granted on request via support.
Products that emit events deliver them as signed webhooks. Every delivery includes an HMAC signature header you should verify before trusting the payload, plus an idempotency key for safe retries.
Webhook endpoints are configured per product. Failed deliveries retry with exponential backoff for 24 hours.
Bugs and integration questions go through the support form — every submission opens a tracked ticket. Typical first response is under one business day; urgent production issues for paid plans are prioritised.
Status and uptime are published on the status page.
Docs grow with the platform. If you need something that isn't covered, open a ticket — documentation requests are tracked like any other issue.