Prepare an RFA template
Upload a family to your project. The Revit client reads its types, parameters, formulas and write-access properties.
Turn product parameters into Revit families with modelKit. Prepare an RFA template, submit a configuration through the API and get a generated family, 3D preview geometry and DWG views.
Architectural illustration. Explore the parameter workflow below.
Explore a generic family using illustrative dimension keys. Your selected template contract defines the actual parameter names and allowed values.
Learn how to validate parameters with the API →Product dimensions and options change. The underlying family stays the same. modelKit connects order parameters to a prepared Revit family. Manage templates and revisions in the dashboard, send configurations through the API and let your connected Revit client generate the outputs for each job.
Prepare and validate your family once. Then use its published parameters to create new configurations through the dashboard or your integration.
Upload a family to your project. The Revit client reads its types, parameters, formulas and write-access properties.
Configure parameters and mappings. Run validation scenarios in Revit, approve the revision and publish it for API access.
Validate parameters with preview. Review the warnings, then create a job with a unique request_id.
Your connected Revit client processes a copy of the family. The job status lists available outputs and any export errors.
Prepare geometry and dependencies in the RFA. The published contract defines which values can change.
Preview shows mappings and skipped fields. It validates the request without running Revit or verifying the resulting geometry.
Each job retains its parameters, revision, processing stage and files. Partial exports show both available results and errors.
Send product configurations from your own system. The API links each request to a published RFA template, validates its values and queues a job for the connected Revit client.
{
"request_id": "order-123-item-1-rev-1",
"product_type_id": "<product_type_id>",
"parameters": {
"Width": 3000,
"Height": 3000,
"Depth": 400
},
"accept_mapping_warnings": true,
"outputs": [
"rfa",
"mesh.json",
"front.dwg",
"top.dwg",
"side.dwg",
"combined.dwg"
]
}Use the template ID and parameter keys from your catalog contract; the dimension keys above are illustrative. Validate your values with preview and review any warnings before submitting. A new request returns 202: the job has been queued.
Retrying with the same ID and body returns the original job. Use a new ID when the configuration changes.
The ModelKit Revit Host Windows client helps install the extension and configure the connection. The pyRevit extension receives jobs, processes RFA families and uploads the outputs to the server.
The client applies parameters to a copy of the RFA, regenerates it and saves the job output.
A client linked to the project and running the required Revit version picks up the job. Until then, it stays queued.
Get an RFA file, mesh.json for 3D viewing, front, top and side DWG views, plus a combined DWG.
The monitor shows the current task and stage. Errors are available in the local log and dashboard history.
The client requests jobs from the server. It needs installed Revit, pyRevit and an active interactive Windows session.
Your server and storage locations determine where data is held. This exchange does not require an inbound HTTP port on the Windows machine.
Build repeatable workflows for parametric product families. Each template defines its capabilities through the prepared RFA and published contract.
Configure dimensions and options in your own Revit families. Each published template defines the parameters available for your design.
Upload families, inspect them in Revit and configure editable parameters. Validate each new family before publishing it.
Send data through parameters or CProduct.inputParameters. Preview shows which fields will be applied.
Prepare changes in a draft. Jobs retain their original revision; new revisions become available after validation and publication.
Organizations, projects and roles control access to templates and outputs. Integration keys have their own permissions.
Review API calls, processing stages, errors and files in the dashboard. Retrying a job keeps the original attempt in its history.
modelKit's web workspace is where a team manages projects, Revit families, Revit servers and API jobs.

Open the login page and click Explore demo. Or sign in with login demo-manager and password demo-modelkit.
The ModelKit · Demo company workspace, a project with sample Revit families — Nordic bar bench, spring rocker and parametric wardrobe — each family card with its publication pipeline, and the template catalog.
Once Revit processes a family, its card can include parameters, a 3D preview and DWG views. The demo is read-only: nothing can be changed.
A Revit family with your parameters applied
Preview geometry in mesh.json
Front, top, side and combined DWG views
Available files and job metadata
The essentials for BIM teams and developers connecting product data to Revit.
modelKit connects product parameters to a prepared Revit family. It validates the configuration, queues a job and uses your connected Revit client to generate a separate family and its requested exports. The geometry and formulas must already exist in the RFA template.
Explore the automation workflow →Yes. Upload a family, inspect it in Revit and configure its editable numeric and Boolean parameters. Run validation scenarios and publish the revision to make its contract available through the API. Each template defines its own supported configurations.
Read about RFA templates and contracts →Request an RFA family, mesh.json geometry for 3D previews, front.dwg, top.dwg, side.dwg and combined.dwg. A ZIP package contains available files and job metadata. Check the job status for partial exports. PDF, IFC, RVT and XLSX are not supported outputs.
See output formats and downloads →Yes. Processing requires a connected Windows machine with Revit 2025 or 2027, the pyRevit extension and an active interactive session. The client must match the job version. Without a compatible client, the job remains queued.
View Revit client requirements →Use a project integration key to read the catalog and retrieve a template contract. Validate your parameters with preview, then submit a job with a unique request_id. Poll its status or configure callbacks, and download the available files using the same key.
Start with API authentication →