@proseid v2026.07.26 SE

Swedish chemical-product register determination

Determines whether a Swedish Chemicals Agency activity report, product notification, annual quantity report, PFAS or nanomaterial review, or separate pesticide authorization action is due.

Compatible with

FormGuided assessmentDeterminationCompliance checklistAPI

Use Schema in a Flow

Publication

Protocol: Proseid_v1.0
Version: v2026.07.26
Applies in: Sweden
Fields: 15
Flow price: $0.20
Publisher fee: None

Legal history

Time periods

se_products_register_20262026-01-01 → continues indefinitely

Current

Controlling sources

Legal references

Förordning (2008:245) om kemiska produkter och biotekniska organismer 3–4 §§ and Annex 1

Source ↗

KIFS 2017:7 Chapter 3 product-register rules

Source ↗

Schema fields

15 fields

Field

Type

Description

Req

Reason the annual quantity report was late

String

—

Opt

Business

String

—

Req

The required pesticide authorization is in place

Boolean

—

Opt

The product is a pesticide

Boolean

—

Opt

The annual quantity report was submitted by 28 February

Boolean

—

Opt

The annual quantity report has been submitted

Boolean

—

Opt

The product is currently registered and has not been deregistered

Boolean

—

Opt

The business activity has been reported to the Products Register

Boolean

—

Opt

Amount manufactured or brought into Sweden during the year (kg)

Number

—

Req

The additional PFAS and nanomaterial questions have been reviewed

Boolean

—

Opt

The product is covered by the current tariff-number list or pesticide entry

Boolean

—

Req

Product name

String

—

Opt

Composition, function, use, and labelling details are complete

Boolean

—

Opt

What does the business do with the product?

Select

Choices: Manufacture in sweden, Import or bring into sweden, Package repackage or rename, Mix for further transfer, Resell unchanged in sweden, Other

Req

Calculated next action

Select

Choices: Outside identified register scope, File activity report now, File product notification by february 28, Complete product information, File annual quantity report by february 28, Document late annual quantity report, Review pfas and nanomaterial details, Obtain pesticide authorization, Products register record current

Opt

Example payload

JSON

{
  "responses": {
    "annual_quantity_report_delay_reason": "",
    "company_name": "",
    "pesticide_authorization_confirmed": false,
    "product_is_pesticide": false,
    "annual_quantity_report_by_february_28": false,
    "annual_quantity_report_submitted": false,
    "product_currently_registered": false,
    "activity_report_submitted": false,
    "annual_volume_kg": null,
    "pfas_or_nanomaterial_review_complete": false,
    "covered_tariff_or_pesticide_entry_confirmed": false,
    "product_name": "",
    "composition_and_use_details_complete": false,
    "business_activity": ""
  },
  "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": "annual_quantity_report_delay_reason",
        "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 versions

Loading published versions…

Trust ledger

Crowd → credentialed

Provenance

Community publisher (unverified)

@proseid · latest v2026.07.26

Community signal

0 votes

No votes yet.

Attestations · by version

0 total

No attestations yet. A verified professional can vouch for a specific version.

Discussion

0 comments

to join the discussion.

Time periods

Legal references

Schema fields

Example payload

API usage

Published versions

Trust ledger

Discussion

FDA food-facility registration determination

EU right-of-withdrawal record

EU whistleblowing internal-report deadlines

OSHA fatality or severe-injury reporting determination