I’ve been building automation tools for small businesses and hit a recurring pain point: every booking platform has a totally different API (if it even has one).
So I’m experimenting with a universal booking API: a single JSON interface that lets developers book, cancel, and check availability across many systems (starting with Vagaro, Mindbody, and Fresha).
Under the hood it’s a mix of native APIs and AI-assisted browser automation that handles login states, 2FA, and DOM drift. The goal is to make booking as portable as payments (think Stripe, but for scheduling).
Right now I’m validating demand. If you’ve ever had to build or maintain integrations with scheduling software, I’d love your feedback. What would make an API like this genuinely useful (or trustworthy) for you?
venuur•3mo ago
So I’m experimenting with a universal booking API: a single JSON interface that lets developers book, cancel, and check availability across many systems (starting with Vagaro, Mindbody, and Fresha).
Under the hood it’s a mix of native APIs and AI-assisted browser automation that handles login states, 2FA, and DOM drift. The goal is to make booking as portable as payments (think Stripe, but for scheduling).
Right now I’m validating demand. If you’ve ever had to build or maintain integrations with scheduling software, I’d love your feedback. What would make an API like this genuinely useful (or trustworthy) for you?