API documentation

Authentication

All API requests use an API key as a bearer token. Create one in the app under Developer → API keys. Keys are either read-only or read/write.

curl https://savrsoft.com/api/v1/events \
  -H "Authorization: Bearer savr_live_your_key_here"

Base URL: https://savrsoft.com/api/v1 · All responses are JSON. Errors return { "error": "…" } with a 4xx/5xx status.

Endpoints

Your organization (id, name, currency).

List events (most recent first). Returns { "data": [...] }.

One event with its dishes.

Create an event. Body:

{ "name": "Acme holiday party", "event_date": "2026-12-18",
  "guests": 120, "price_per_head": 55, "event_type": "corporate" }

List recipes (with allergens & diet flags), or one recipe with ingredients.

List or create clients. Create body: { "name": "...", "email": "...", "phone": "...", "company": "..." }

List invoices with computed totals, or one invoice with line items.

Webhooks

Register an endpoint under Developer → Webhooks. We POST a JSON payload when events occur:

{
  "id": "evt_abc123",
  "type": "event.inquiry",
  "created_at": "2026-07-17T18:20:00.000Z",
  "data": { "id": 42, "name": "Corporate lunch — Dana Ruiz", ... }
}

Event types

Verifying signatures

Each delivery includes an x-savrsoft-signature header: the HMAC-SHA256 of the raw request body, keyed with your webhook signing secret. Compute the same and compare:

// Node.js
const crypto = require('crypto');
const sig = crypto.createHmac('sha256', SIGNING_SECRET)
  .update(rawBody).digest('hex');
if (sig !== req.headers['x-savrsoft-signature']) reject();