Skip to content

Embed scheduling in your platform or CRM

One OAuth app for all your customers' organisations, signed links that tie each booking to your record, and webhooks to keep everything in sync.

You build a CRM, business software or a platform used by other companies, and want to embed scheduling in your platform without rebuilding it.

Embed scheduling in your platform: three building blocks

  1. An OAuth app, declared once, that each customer authorises for their account. Declare it in Settings › Integrations › OAuth apps (Pro plan): you get a client_id (rdv_app_…) and a secret (rdv_cs_…). Members of any organisation can authorise it; each token acts on behalf of that member, in their organisation, within the granted scopes. See authentication.
  2. Signed context links: POST /types/{id}/signed-links with {source, type, id, libelle?, prerempli?: {nom, email, telephone}, organisateur?, days?} returns a /r/{space}/{type}?c=… link, valid 1 to 90 days (14 by default). The context is stored on the booking, sent in webhooks (contexte) and filterable with GET /bookings?context_source=…&context_id=….
  3. Webhooks for reservation.* events: see webhooks.

The owner generates a context key (shown once). The context token is payload.signature: payload is the base64url JSON of the context, signature the base64url HMAC-SHA256 of payload with the key. The JSON takes source, type, id (required), libelle, prerempli, organisateur and exp (Unix seconds).

import crypto from "node:crypto";

const key = process.env.RDV_CONTEXT_KEY;
const payload = { source: "my-crm", type: "deal", id: "DEAL-42", exp: Math.floor(Date.now() / 1000) + 14 * 86400 };
const body = Buffer.from(JSON.stringify(payload)).toString("base64url");
const signature = crypto.createHmac("sha256", key).update(body).digest("base64url");
const url = `https://your-application-domain/r/my-space/intro-call?c=${body}.${signature}`;

Prefill and tracking

The booking page also reads name (or first_name and last_name), email, phone, a1 to a10 for the type's questions, and keeps utm_*, gclid, fbclid and ref on the booking. The embed widget passes them for you.

Best practices

Ask for the narrowest scopes, keep secrets and keys server-side, handle webhooks idempotently, refresh tokens before they expire, and stay under 100 calls a minute per token: see limits and errors.

Declare your app

Create your account, switch to Pro and declare your OAuth app in Settings › Integrations.

Create my account