Commerce & Payments · Integration
Booqable
Add Booqable to your product for your customers, and give your AI agents governed access to it.
There is no shared api.booqable.com host: every account gets its own subdomain, so calls go to https://<company>.booqable.com/api/, which means the tenant subdomain is part of the credential set and not just the token. Two generations run side by side, the older /api/1/ routes and the newer /api/boomerang/ surface which is JSON:API with relationships and sideloaded includes, and the two disagree on field naming, so pick one and stay on it. The object that trips people up is the planning: an order line does not simply reference a product, it creates a planning with a starts_at and stops_at that reserves stock for that window, and availability across the whole catalogue is computed from plannings rather than from a quantity column. Products sit under product groups that hold variations such as size or colour, and serialised kit is tracked as individual stock items, so the same catalogue entry can be quantity-tracked or identity-tracked depending on setup. Both surfaces return 401 on unauthenticated requests, which makes credential checks straightforward. fastn holds each customer's subdomain and API key together and keeps the calls pinned to one API generation.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Booqable account, subdomain and key included, without pasting URLs
Pull rental orders and their plannings into your operations view so pickups and returns are visible
Check availability for a product over a date window before your product offers it to an end customer
Sync Booqable customers into your own contact records, keeping the Booqable id as the join key
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent draft a rental order with plannings for a requested window, held for staff confirmation
Have an agent report items due back today that have not been checked in, audited per tenant
Let an agent flag product groups whose stock items are all reserved for an upcoming period
Example prompt
Do we have four of the large lighting kits free for the weekend of the 12th?
Set up Booqable in 4 steps
- 01Enable the Booqable connector from your fastn dashboard.
- 02Have each customer authorise their own Booqable account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Booqable integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Booqable integration without building it. Your customers connect their own Booqable account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Booqable update is not your on-call problem.
- One integration serves your product and your agents. The same governed Booqable connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Booqable, across other categories.
NetSuite
Notion
Box
DocusignBooqable integration FAQ
How do I add a Booqable integration to my product?
Enable the Booqable connector in your fastn dashboard, then let each customer authenticate their own Booqable account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Booqable client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Booqable account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Booqable account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Booqable integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent draft a rental order with plannings for a requested window, held for staff confirmation
Who maintains the Booqable integration?
fastn does. When Booqable changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Booqable integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Booqable integration?
A common starting point: let a customer connect their own Booqable account, subdomain and key included, without pasting URLs. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Booqable integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Booqable does not change your per-connector cost. You can start free with 3 connected accounts.
Add Booqable to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.