domain: support.rentman.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In Rentman, go to the Configuration module > Integrations > Webhooks section and click Connect to enable webhooks; this generates a shared Token and lets you set a target URL.
On each account event (create/update/delete of items like Project, Contact, Equipment, SerialNumber, Quotation, etc.), Rentman POSTs a JSON payload to your URL containing account, user, eventType, itemType, items[], and eventDate.
For each item in the payload, use the included 'ref' value (e.g. /contacts/12014) appended to https://api.rentman.net to fetch the full record via the regular Public API.
Verify authenticity by computing an HMAC digest of the raw request body using the shared token and comparing it against the Digest header Rentman sends (format: sha512=<digest>).
Handle duplicate deliveries and out-of-order delivery defensively, since Rentman documents both as known limitations.
Known gotchas
After 50 consecutive delivery failures Rentman automatically disables the webhook endpoint; you'll need to re-save the URL in Configuration to re-enable it.
Delete events send a bare array of integer IDs in items (no ref/parent object), unlike create/update events which send full item/parent objects — your handler needs to branch on eventType.
This is a separate feature from the resource-oriented REST API itself; webhooks are configured through the Rentman UI, not a POST /webhooks endpoint.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?