Overview

This flow is the cloud half of the Revit export seam. The Revit Connector add-in produces the contract-v1 JSONL. Project Delivery Graph owns ImportRun and the definition graph the artifact becomes.

Plugin sequence (also on the OpenAPI operations):

1. POST upload-url
2. PUT gzip to uploadUrl (or local-dev putLocalRevitImportArtifact)
3. POST register
4. POST process, or poll GET until ready / failed

ENABLE_CRON_JOBS=true is required for the minute cron. POST …/process does not replace cron.

HTTP

Do not invent other operation ids. Do not copy request/response schemas here; use generated OpenAPI.

Step	Method and path	OpenAPI operationId
Upload URL	POST /api/v1/projects/{id}/revit-imports/upload-url	requestRevitImportUploadUrl
Local PUT	PUT /api/v1/projects/{id}/revit-imports/local-upload	putLocalRevitImportArtifact
Register	POST /api/v1/projects/{id}/revit-imports	registerRevitImport
List log	GET /api/v1/projects/{id}/revit-imports	listRevitImports
One run	GET /api/v1/projects/{id}/revit-imports/{runId}	getRevitImport
Process now	POST /api/v1/projects/{id}/revit-imports/{runId}/process	processRevitImport
Summary	GET /api/v1/projects/{id}/definition-graph/summary	getProjectDefinitionGraphSummary
Rematerialize	POST /api/v1/projects/{id}/definition-graph/summary/rematerialize	rematerializeProjectDefinitionGraphSummary

Code References

• apps/api-v1/src/modules/project-delivery-graph/core/application/use-cases/RegisterSourceImportUseCase.ts
• apps/api-v1/src/modules/project-delivery-graph/core/application/use-cases/ProcessSourceImportUseCase.ts
• apps/api-v1/src/modules/project-delivery-graph/core/application/use-cases/ReadRevitImportsUseCase.ts
• apps/api-v1/src/modules/project-delivery-graph/core/application/use-cases/RematerializeSummaryViewUseCase.ts
• apps/api-v1/src/modules/project-delivery-graph/adapters/inbound/rest/revit-imports/revitImports.openapi.ts