Schema record
@proseid v2026.07.26 US

FDA food-facility registration determination

Determines whether a domestic or foreign food facility must register with FDA, renew during the even-year window, update changed information, cancel and re-register after ownership changes, or document an exemption.

Compatible with
FormGuided assessmentDeterminationCompliance checklistAPI
Use Schema in a Flow
Publication
Protocol
Proseid_v1.0
Version
v2026.07.26
Applies in
United States
Fields
17
Flow price
$0.20
Publisher fee
None
Standard base $0.20 · exact total is frozen when a Flow is created

Schema fields

17 fields
Facility location
Select
Choices: Domestic, Foreign
Req
The facility manufactures, processes, packs, or holds food for consumption in the United States
Boolean
Req
The new owner completed a new facility registration
Boolean
Opt
Documented registration exemption
Select
Choices: None, Private residence, Farm, Retail food establishment, Restaurant, Nonprofit food establishment, Fishing vessel within exemption, Facility exclusively regulated by usda, Other documented exemption
Req
The facility owner has changed
Boolean
Req
Required registration information has changed
Boolean
Req
Status of the applicable biennial renewal window
Select
Choices: No renewal currently due, Upcoming in current even year, Open october 1 to december 31, Passed without required renewal
Req
The current biennial renewal is complete
Boolean
Opt
An FDA-acceptable unique facility identifier is included
Boolean
Opt
The foreign facility's United States agent is confirmed
Boolean
Opt
The former owner cancelled the registration within 60 calendar days
Boolean
Opt
Changed registration information was updated within 60 calendar days
Boolean
Opt
A valid food-facility registration has been restored after the missed renewal
Boolean
Opt
Calculated registration position
Select
Choices: Outside food facility test, Document exemption, Documented exemption, Register before operations, Complete registration identifiers, Cancel and reregister for new owner, Update information within 60 days, Prepare for biennial renewal, Renew between october and december, Registration expired after missed renewal, Registration current
Opt
Exemption analysis reference
String
Opt
Facility
String
Req
The facility's initial FDA registration is complete
Boolean
Opt

Example payload

JSON
{
  "responses": {
    "facility_location": "",
    "manufactures_processes_packs_or_holds_food_for_us": false,
    "new_owner_registered_facility": false,
    "exemption_basis": "",
    "facility_owner_changed": false,
    "required_registration_information_changed": false,
    "renewal_window_status": "",
    "biennial_renewal_complete": false,
    "acceptable_ufi_included": false,
    "foreign_us_agent_confirmed": false,
    "former_owner_cancelled_within_60_days": false,
    "information_updated_within_60_days": false,
    "expired_registration_restored": false,
    "exemption_analysis_reference": "",
    "facility_name": "",
    "initial_registration_complete": false
  },
  "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": "facility_location",
        "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
P
Provenance
Community publisher (unverified)
@proseid · latest v2026.07.26
Community signal
0
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.