Pull your venues, guest sign-ups and visit stats into any system with a read-only REST API and self-serve keys. Included on Growth and above. 30-day free trial.
The CaptiFi REST API exists for the systems no directory can cover: a bespoke booking platform, an in-house CRM, a data warehouse, a reporting spreadsheet a finance team already lives in. Rather than asking you to export a CSV every week, CaptiFi gives you a read-only JSON API over the same guest data your dashboard shows, with self-serve keys you create and revoke yourself.
Create a key in the dashboard, name it after the system that will use it, and send it as a bearer token against https://app.captifi.io/api/v1/customer. Four endpoints cover the ground: /venues for your sites, /guests for sign-ups with filtering and pagination, /stats for visit and opt-in totals over a period, and /me to confirm which account a key belongs to. Every response comes back in the same envelope, with your rows under data and paging or totals under meta, so a single client handles all of them.
The API is deliberately read-only. Nothing a key can do will change your splash pages, your settings or your guest records, which makes it safe to hand to a developer or an agency without handing over your dashboard. Keys are stored hashed like passwords and revealed exactly once, you can hold up to five at a time, and revoking one never affects the others. Pair the API with webhooks: webhooks for live events as guests arrive, the API to backfill history and build reports.
Pull venues, guest sign-ups and visit statistics straight into a booking platform, CRM, warehouse or reporting tool, without a weekly CSV export and without waiting for a native connector to be built.
A key can read your data and nothing else. It cannot edit splash pages, change settings or touch guest records, so handing one to a developer or agency carries none of the risk of sharing a dashboard login.
Create up to five keys yourself, one per system, so you can retire or rotate a single integration without breaking the rest. Keys are stored hashed and shown once, exactly like a password.
Every endpoint returns rows under data and paging or totals under meta, so the client you write for guests works unchanged for venues and stats.
Open API Keys in your CaptiFi dashboard and give the key a name matching the system that will use it. The key appears once, immediately after creation, so copy it straight away: it is stored hashed and cannot be shown again.
Send the key as an Authorization: Bearer header, with Accept: application/json, against the base URL https://app.captifi.io/api/v1/customer.
Use /venues for your sites, /guests for sign-ups with filters and pagination, /stats for visit and opt-in totals, and /me to confirm the account. Responses always carry rows under data and paging under meta.
Use the API to pull history and build reports on your own schedule, and add a webhook endpoint so new sign-ups are pushed to you the second they happen rather than on your next poll.
A group pulls guest sign-ups nightly into its own data warehouse so WiFi opt-ins sit alongside bookings and spend in the same reporting suite.
An in-house CRM calls /guests every hour with a date filter, so new opted-in diners appear in the marketing team tooling without anyone exporting a spreadsheet.
A marketing agency is given its own read-only key per client, builds a live footfall and opt-in dashboard from /stats, and the venue can revoke that single key at the end of the engagement.
30-day free trial. Cancel anytime.