Integrations

Connect Mealward to your existing systems

Signed outbound webhooks and a versioned REST API ship today — facility admins generate keys in Settings. No Salesforce tax. No six-month middleware project unless you want bidirectional clinical sync.

Three ways to integrate

Pick the depth that matches your IT maturity — all included in the platform fee.

Signed webhooks

Subscribe to order, resident, and service events. HMAC-SHA256 signatures on every payload. Delivery log with automatic retries every five minutes.

REST API + keys

Facility-scoped API keys with one-time display. v1 endpoints for residents and orders today — more resources on the roadmap.

Custom Phase 2 sync

Need bidirectional clinical or finance sync? We scope thin-sync projects per customer — typically live in about two weeks for one-way feeds.

How webhooks work

1

Create an endpoint

Facility admin adds a URL and picks event types in Settings → Integrations.

2

Verify signatures

Your receiver checks X-Mealward-Signature-256 with the endpoint secret.

3

Process the event

JSON payload includes facility_id, timestamp, and event-specific data.

4

Inspect the log

Every attempt is logged — retries happen automatically on failure.

Right-sized for your IT team

Single facility

Export yesterday's orders to a spreadsheet script, or push completion events to your rostering tool. One API key, one facility — set up in minutes.

Multi-site group

Org-level webhook endpoints fan out events to a central data warehouse. IT teams get HMAC-signed payloads and a delivery log — no shared admin passwords.

Webhook secrets are encrypted at rest. API keys are hashed — we never store the full key after creation. Keys and endpoints are facility-scoped with admin-only access. Trust details →

See integrations in the live demo

Settings → Integrations and API Keys are enabled in demo.mealward.com.au. Create a test webhook, send a test event, and inspect the delivery log.