Event contract
Event request.created includes event_id, occurred_at, request_id, department and summary. The receiver validates required fields before accepting the event.
VSPO-authored work sample · VSPA-SIM-018
MapleWorks Admin • Webhook Contract
A complete representative event contract and response matrix using fictional identifiers. No endpoint is contacted.
VSPO-authored demonstration based on an existing VSPA simulation brief. Organizations, records and figures are fictional. This is not completed client work, an assessed learner submission, a client endorsement or evidence of live commercial results.
Service: API, Webhook & Systems IntegrationFamily: Automation, AI & Systems IntegrationSource: VSPA-SIM-018 — Workflow Automation Simulation
Representative output
Explore the work.
One event. One traceable record.
{
"event_id": "evt-demo-101",
"type": "request.created",
"request_id": "REQ-101",
"department": "operations",
"summary": "Prepare weekly pack",
"synthetic": true
}Validate → deduplicate → accept or route for review. Repeated events use the same key.
This example illustrates part of the package. It does not imply that all contracted deliverables, integrations or production controls are present. Interactive previews use synthetic data and do not send messages, process payments or save business records.
The complete written sample
Content, decisions and handover context.
Example payload
{"event_id":"evt-demo-101","type":"request.created","request_id":"REQ-101","department":"operations","summary":"Prepare weekly pack","synthetic":true}
Delivery policy
Use authenticated HTTPS in production. A duplicate event_id returns the prior outcome. Transient failures retry with backoff; permanent validation failures go to review.
Reconciliation
Compare accepted source events with destination records by request_id. Investigate missing, duplicated or unmapped records before closing the reporting period.
| Condition | Response policy | Recovery |
|---|---|---|
| Valid new event | Accept once | Record reference |
| Duplicate event | Return existing result | Do not recreate |
| Missing request_id | Reject validation | Correct source record |
| Destination unavailable | Queue retry | Escalate after limit |
How a commissioned output is reviewed
Acceptance is part of the brief.
- ✓ Mappings have valid and invalid examples
- ✓ Repeated event does not create duplicates
- ✓ Authentication and failure modes are documented
- ✓ Destination totals can be reconciled
These are review criteria, not a claim that this demonstration was independently assessed.