Overview

This area is for integrators and developers. Day-to-day product help stays under Using BUKMI.

Planned integration capabilities

Nothing here is a commitment or public offer yet-the list describes the direction for future work:

• HTTP API - versioned REST-style endpoints for businesses, services, bookings, and related objects, with stable URLs, authentication, and rate limits suitable for server-to-server use.
• Authentication for integrations - clear ways for external systems to obtain and refresh credentials (for example API keys or standard delegated auth flows), plus guidance on scopes and revocation.
• Webhooks - outbound events (for example booking created or updated, subscription changes) delivered to your HTTPS endpoints, with signed payloads and documented retry behaviour.
• Environments - separate sandbox and production credentials and data where that makes sense for testing integrations safely.

Detailed reference docs (machine-readable API descriptions, event catalogs, code samples) will appear here as each surface ships. Until then, BUKMI is used through the web app and guest booking links documented for customers.

Website embed (available now)

If you build or maintain a client’s marketing site, the embed widget is documented separately:

• Embed widget reference - embed.js attributes, iframe URLs, postMessage events, CSP
• Embed booking on your website - owner setup in the dashboard