Skip to content

A scheduling API open to all your tools

Scoped tokens, signed webhooks, OAuth apps, Zapier and Make. Your bookings flow to where you work.

A scheduling API matters as soon as your bookings need to live outside the booking tool: business software, a client portal, a data warehouse, an automation tool.

Why a complete scheduling API

Artibox Calendar exposes a public REST API under /api/v1: meeting types, availability, bookings, polls, single-use links, link sends and webhooks. It follows the same rules as the app — same rights, same isolation between organisations, same locked booking. A token can do what its member can do, nothing more. Bookings made through the API respect the same rules as your booking page.

How it works

  1. Create a personal token

    Pick its scopes. Tokens start with rdv_pat_.

  2. Call the API

    Send the token in the x-api-key header. Calls outside its scopes get a 403.

  3. Subscribe to events

    Declare a webhook URL and the events you need.

  4. Follow deliveries

    The webhook log shows each delivery; test and replay from there.

Built for production

Clear limits

100 calls per minute per token, page-number pagination, and an Idempotency-Key header on creations, kept for 24 hours, so a retried call never creates a duplicate.

Signed webhooks

Get notified when a booking is created, rescheduled, cancelled or marked, when a guest votes on a poll or a poll is confirmed. Each delivery is signed (X-Signature), retried from one minute up to twelve hours, and the subscription is disabled after 20 failures. The log keeps 30 days of deliveries.

OAuth for software vendors

Declare an OAuth app: consent screen, single-use 10-minute code with PKCE (S256), 2-hour access token, rotating refresh token. Members revoke access from « Connected apps ».

No code: Zapier, Make and the widget

The Zapier and Make connectors plug in as OAuth apps. The widget.js script adds a booking button to your site and keeps utm_*, gclid, fbclid and ref on the booking.

Plans

API, Zapier and Make come with the Pro plan; webhooks with the Team plan. For HubSpot, Salesforce and Pipedrive, see CRM integrations. Security details are on the security page. Only a fingerprint of each token is stored, never the token itself, and webhooks can never target an internal network address.

Who it's for

Frequently asked questions

How do I authenticate?

With a personal token (rdv_pat_…) or an OAuth access token in the x-api-key header. Each token has its scopes.

What are the rate limits?

100 calls per minute per token. Creations accept an Idempotency-Key header, kept for 24 hours.

How do I verify a webhook?

Each delivery is signed in the X-Signature header. Check the signature before processing the payload.

Which plan includes the API?

API, Zapier and Make from the Pro plan; webhooks from the Team plan. See pricing.

Connect your meetings to your tools

Create your free account, then your first API token.

Create my account