Docs.

Every request is authenticated with an API key. Open the keys dashboard, create a key, and copy the secret. The full secret is shown once — we store only a hash, so if you lose it you rotate the key rather than recover it.

Send the key as a bearer token on every request. Keep it server-side; never ship it in client code or commit it to a repo.

Point requests at your deployment's base URL. Here's a poll created with curl:

curl -X POST https://booqit.online/api/polls \
  -H "Authorization: Bearer $BOOQIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Team sync",
    "options": [
      "2026-07-10T09:00:00Z",
      "2026-07-10T14:00:00Z",
      "2026-07-11T09:00:00Z"
    ]
  }'

The response includes the poll id, a shareable link, and an adminKeyfor reading results. List a booking page's open slots the same way:

curl https://booqit.online/api/bookings/pages/$SLUG/slots \
  -H "Authorization: Bearer $BOOQIT_KEY"

The same backend speaks the Model Context Protocol, so any MCP-capable client can create polls and book slots without a browser. Run the bundled MCP server over stdio and point it at your deployment with your key:

{
  "mcpServers": {
    "booqit": {
      "command": "npx",
      "args": ["-y", "@booqit/mcp-server"],
      "env": {
        "BOOQIT_BASE_URL": "https://booqit.online",
        "BOOQIT_API_KEY": "ak_your_secret_here"
      }
    }
  }
}

Add that block to your MCP client's server configuration, restart it, and the booking tools become available. The server talks to the REST API above over HTTPS — the key you paste is the one you minted in step 1.

Keys carry scopes. A key created from the dashboard can manage other keys (keys:write); mint narrower keys for servers that only need to read or write bookings. Rotate a key to issue a replacement while the old one keeps working through a short grace window, then revoke the old one once your services have switched over.