Swedish serious workplace-event notification
Determines whether a workplace event requires prompt notice to the Swedish Work Environment Authority and records the event information, timing, acknowledgement, and follow-up investigation.
Compatible with
FormGuided assessmentDeterminationCompliance checklistAPI
Publication
- Protocol
- Proseid_v1.0
- Version
- v2026.07.26
- Applies in
- Sweden
- Fields
- 14
- Flow price
- $0.20
- Publisher fee
- None
Standard base $0.20 · exact total is frozen when a Flow is created
Legal history
Time periods
se_work_event_20262026-01-01 → continues indefinitely
CurrentControlling sources
Legal references
Schema fields
14 fieldsField
Type
Description
Req
The event occurred in connection with work
Boolean
—
Req
The event was reported as soon as possible, preferably the same day
Boolean
—
Opt
Notice was submitted to the Swedish Work Environment Authority
Boolean
—
Opt
Date of the event
Date
—
Req
The submission acknowledgement has been saved
Boolean
—
Opt
Number of people affected
Number
—
Req
Most serious outcome or risk
Select
Choices: Death, Serious personal injury, Several workers injured, Incident with serious danger, Other injury or incident, Uncertain
Req
Calculated notification position
Select
Choices: Outside this notice test, Urgent classification needed, Notify authority promptly, Document late notice, Complete notice record, Notification record current
Opt
A contact person is included in the notice
Boolean
—
Opt
The employer's cause and prevention investigation has started
Boolean
—
Opt
What happened
String
—
Req
Reason the notice was not submitted promptly
String
—
Opt
Employer
String
—
Req
Where the event happened
String
—
Req
Example payload
JSON
{
"responses": {
"work_related": false,
"reported_as_soon_as_possible": false,
"authority_notice_submitted": false,
"event_date": "",
"acknowledgement_saved": false,
"people_affected": null,
"event_category": "",
"contact_person_recorded": false,
"internal_investigation_started": false,
"what_happened": "",
"delay_reason": "",
"employer_name": "",
"event_location": ""
},
"effective_at": "2026-07-26"
}The request body this schema expects. Fill in responses and keep the field IDs unchanged. Validation becomes callable after you use this release in a published Flow.
API usage
Create a Flow from this schema, then replace the route placeholders with that Flow's organization and address. Validation is free and runs against the exact release bound to the Flow. It returns the engine's resolved fields and legal time period when ready, or a structured error with field-level issues.
cURL
curl -X POST https://proseid.com/api/v1/validate/{your-org}/{flow-slug} \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d @payload.json 200 OK
{
"valid": true,
"status": "READY",
"definitions": { ... },
"issues": [],
"effective_at": "2026-07-19",
"temporal_context": {
"logic_version": "current",
"valid_range": ["2026-01-01", null]
}
} 422 Invalid
{
"error": {
"code": "validation_failed",
"message": "the document did not pass validation",
"details": {
"status": "INCOMPLETE",
"issues": [{
"field_id": "work_related",
"kind": "missing_required",
"severity": "error",
"trigger": "completion",
"message": "Required field is missing"
}]
}
}
}A completed webhook also depends on the Flow's experience, signing, pricing, and delivery settings. Create a Flow with this schema, then use Send sample completion in its delivery settings to receive the full signed JSON without using your balance. Webhook guide
Published versions
Permanent, attributable versionsLoading published versions…
Trust ledger
Crowd → credentialedP
Provenance
Community publisher (unverified)
@proseid · latest v2026.07.26
Community signal
0
0 votes
No votes yet.
Attestations · by version
0 totalNo attestations yet. A verified professional can vouch for a specific version.
Discussion
0 comments
to join the discussion.