Sent to your registered webhook endpoint when a Call+ plan is launched. Carries the fiche complémentaire figures and the identifiers to match the beneficiary, employer and accounting firm.
plan.launched is an outbound call: Call+ sends a signed POST request to the HTTPS endpoint you register at onboarding. There is no URL to call on our side, and your API key plays no role — the request is authenticated by its HMAC signature instead. Respond with any 2xx status within 10 seconds to acknowledge the delivery.
Request format
POST https://<your-registered-endpoint>
Content-Type: application/json
X-Callplus-Event-Id: 3f8e9a3c-6a68-4c69-9a1d-1f9f8b1f2a34
X-Callplus-Event-Type: plan.launched
X-Callplus-Signature: t=1786356000,v1=<64 lowercase hex characters>| Header | Description |
|---|---|
X-Callplus-Event-Id | Same value as eventId in the body — usable for deduplication before parsing. |
X-Callplus-Event-Type | Same value as eventType in the body. |
X-Callplus-Signature | HMAC-SHA256 signature over the raw body — always verify it before trusting the payload: Verifying webhook signatures. |
Every webhook body uses the same envelope; data carries the event-specific payload:
{
"eventId": "3f8e9a3c-6a68-4c69-9a1d-1f9f8b1f2a34",
"eventType": "plan.launched",
"apiVersion": 1,
"occurredAt": "2026-08-10T12:00:00+02:00",
"data": { "…": "…" }
}Where everything else lives
- Field-by-field payload description and the 60-day taxation rule — The plan.launched event
- Signature verification, with code and a test vector — Verifying webhook signatures
- Acknowledgement, retries, deduplication, per-firm consent, onboarding — Delivery, retries & onboarding
Not triggered by simulations.
POST /api/v1/simulationsruns a hypothetical calculation and never emits this event.