Overview
What is OpenSpace: OpenSpace is a visual intelligence platform for builders. It provides automated 360° video jobsite capture and pairs that imagery with analytics for commercial construction. The platform spans five products: OpenSpace Capture for timestamped reality capture, OpenSpace Field for image-based task management, OpenSpace Track for computer-vision progress tracking, OpenSpace Air for drone and scan imagery, and OpenSpace BIM+ for 3D field tools.
How to integrate OpenSpace with Datagrid
Implement the connection in this order: confirm OpenSpace API or export access, configure authentication, and map the one-way data sync Datagrid should ingest.
Confirm OpenSpace access
Start by confirming which OpenSpace data sources your account can expose to Datagrid. OpenSpace API access requires an Enterprise subscription, and the Usage API requires a separate purchase.
In OpenSpace, confirm Enterprise API access is active for your account.
For usage analytics, generate an API key. Go to your profile, select View profile, then Create key.
For Field Notes, captures, and progress data, confirm the applicable API or export access available on your OpenSpace account.
In Datagrid, create a custom ingestion workflow for OpenSpace API or export data.
Enter your Usage API key, approved OpenSpace API source, or exported OpenSpace data source and authorize the workflow.
Select the data objects you want to sync, such as Field Notes, progress data, or usage analytics.
Save the workflow and verify the first ingestion completes.
Use this Datagrid ingestion shape before implementation:
datagrid_ingestion_workflow:
source: "OpenSpace"
direction: "one-way: OpenSpace to Datagrid"
credential_options:
- "Usage API key"
- "approved OpenSpace API source"
- "exported OpenSpace data source"
objects_to_select:
- "Field Notes"
- "progress data"
- "usage analytics"
verification_step: "confirm first ingestion completes"Configure authentication
Use the authentication method available for the OpenSpace data source you are ingesting. The documented self-generated API-key flow is for the OpenSpace Usage API, with keys created from the user profile, per the Usage API docs. Other OpenSpace API and export workflows should be configured according to the Enterprise API access available on your account. Enterprise SSO supports SAML 2.0 and OIDC, per the OpenSpace SSO docs. OpenSpace does not publicly document an OAuth 2.0 developer flow.
Use this authentication map to separate Usage API access from other Enterprise API and export workflows:
openspace_authentication:
usage_api:
credential: "self-generated API key"
creation_path: "profile > View profile > Create key"
enterprise_api_or_exports:
credential: "approved Enterprise API or export access"
applies_to:
- "Field Notes"
- "captures"
- "progress data"
sso:
standards:
- "SAML 2.0"
- "OIDC"
oauth_2_developer_flow: "not publicly documented by OpenSpace"Map the one-way data sync
Define the OpenSpace objects Datagrid should read before you run the workflow. The OpenSpace API supports GET endpoints for most fields, so a Datagrid workflow reads data out of OpenSpace. POST and PUT endpoints for bidirectional sync are roadmapped but not yet available, per the OpenSpace Waypoint 2025 FAQ. Synced objects can include Field Notes, captures, progress data as CSV, and usage analytics.
Do not configure writeback tasks to OpenSpace until POST and PUT endpoints are available. Keep the first Datagrid workflow focused on read-side ingestion, classification, schedule comparison, and downstream routing.
Use this object map to scope the Datagrid workflow before implementation. It reflects the OpenSpace objects, formats, fields, and access paths described above.
openspace_to_datagrid:
direction: "one-way: OpenSpace to Datagrid"
access:
usage_analytics: "Usage API key"
field_notes: "Enterprise Field Note API access or export access"
progress_data: "CSV export"
captures: "export workflow"
objects:
field_notes:
fields:
- "photo evidence"
- "floor plan location pin"
- "description"
- "status"
- "due date"
- "assignee"
progress_data:
format: "CSV"
usage_analytics:
metrics:
- "capture volume"
- "engagement metrics"
captures:
export_formats:
- "JPG"
- "PowerPoint"After the first ingestion completes, use the resources below to validate API access, export behavior, and downstream workflow setup.
Why use OpenSpace with Datagrid
OpenSpace gives project teams the field record. Datagrid's AI agents turn that record into routed work, schedule checks, and consistent follow-up across projects.
Automated Field Note routing: Datagrid agents read OpenSpace Field Notes and route them to the right system based on type, location, and assignee, including custom platforms beyond native connectors.
Schedule comparison without manual review: Agents ingest OpenSpace Track progress CSVs and compare completion data against your schedule, then flag deviations before they become change orders.
Spatially indexed data for agents: OpenSpace Spatial APIs deliver spatially enriched data purpose-built for agent development and feed custom Datagrid agent workflows.
Analytics pipeline automation: The Usage API exports capture volume and engagement metrics that Datagrid transforms before loading into warehouses or dashboards.
Cross-platform consistency: Datagrid applies the same classification and routing logic across every project, so field observations follow your standards every time.
Drone capture processing: OpenSpace Air exports aerial imagery that Datagrid agents analyze for anomaly detection and site comparison over time.
What you can build with OpenSpace Datagrid integration
The following workflows turn OpenSpace jobsite data into repeatable execution patterns for operations, PM, and field teams. Start with one OpenSpace data source, verify ingestion, then route structured records into the downstream systems your project teams already use.
Field Note triage agent: Build an agent that pulls Field Notes from the OpenSpace API, classifies each one by trade and severity, then creates matching records in your project management platform. Photo evidence, location pins, and assignees carry through automatically.
Progress reporting pipeline: Export OpenSpace Track progress data as CSV, then have a Datagrid agent compare it against your construction schedule and generate weekly status reports. The agent flags tasks behind plan for the PM to review.
Analytics warehouse loader: Use the Usage API to export capture volume and user engagement metrics. A Datagrid agent transforms the data and loads it into your reporting warehouse, replacing manual reporting pulls.
Drone anomaly detector: Ingest OpenSpace Air JPG exports into Datagrid. An agent compares site captures across dates and flags unexpected changes for the field team to inspect.
Each workflow keeps OpenSpace as the field record and uses Datagrid as the execution layer. Project teams keep the source system intact while agents handle classification, comparison, transformation, and routing.
Resources and documentation
Datagrid Developer Quickstart to connect external data sources and build agents.
API Swagger reference to review endpoint and policy details.
Usage API docs to validate analytics export and API key generation.
Frequently asked questions
Does the OpenSpace API support two-way sync with Datagrid?
OpenSpace API-based sync does not support writeback yet. OpenSpace currently supports GET endpoints for most fields, so you can take data out. POST and PUT endpoints for bidirectional sync are roadmapped but not available. Native two-way sync exists with Procore and Autodesk Construction Cloud (ACC), but API-based sync into Datagrid runs one-way for now.
What subscription do I need to use OpenSpace with Datagrid?
API access requires an Enterprise subscription, and the Usage API requires a separate purchase before access is granted. OpenSpace states that Enterprise "includes SSO, access to OpenSpace APIs for integration with your tech stack."
How do I authenticate the connection?
The Usage API uses self-generated API keys. Create one from your profile by selecting View profile, then Create key. For other OpenSpace APIs and export workflows, use the access method available to your Enterprise account. For SSO, OpenSpace supports SAML 2.0 and OIDC.
What data objects can Datagrid pull from OpenSpace?
A custom Datagrid workflow can pull Field Notes, captures, progress data, and usage analytics from OpenSpace APIs and exports. Field Notes include photo, floor plan location pin, description, status, due date, and assignee. Progress data exports as CSV via OpenSpace Track.
What export formats does OpenSpace support for Datagrid ingestion?
For the workflow described here, Datagrid ingestion can use CSV for progress and tracker data and JPG or PowerPoint for capture reports. The BCF export carries XYZ coordinates for BIM tools.
Similar integrations
Procore: Native two-way syncing with OpenSpace for punch items, observations, and sheet/user imports makes Procore a common downstream system for Field Notes.
Autodesk Construction Cloud (ACC): Autodesk Construction Cloud provides the BIM and issue-tracking counterpart OpenSpace syncs with for two-way issues, model imports, and BIM alignment.
PlanGrid: PlanGrid supports SSO and embedded workflows with OpenSpace, so project teams can reference Field Notes and captured imagery inside plan viewers.
Revizto: Revizto receives OpenSpace Field Notes exported as Issues with XYZ coordinates for issue routing between VDC and field teams.
Revit: Revit connects via BIM model import workflows to align OpenSpace captures and enable automated BIM data extraction and saved-view comparisons.