Dalux Field API
54
AI ReadinessFoundational (C)54/100
Community OpenAPI document · agent-readyStorageDocument ManagementapiKey59 EndpointsREST
Know of an official OpenAPI document?
Install Jentic One Beta
Connect the Dalux Field API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dalux Field API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdalux.com%2Fdalux" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdalux.com%2Fdalux" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Dalux Field API.
Read projects, their metadata, users, and companies
Browse file areas, folders, files, and version sets
Retrieve file content and revision history
Read tasks, approvals, safety issues, and observations
Browse inspection plans, test plans, and their registrations
Upload files in chunks and retrieve project forms
Use Cases
Patterns agents use Dalux Field API for, with concrete tasks.
★ Construction document access
Field and office teams need the latest drawings and files from a project. The Dalux Field API browses file areas, folders, files, and version sets and retrieves file content, so a tool can surface the current document for a given project.
Browse a project's file areas and retrieve the latest revision of a named file
Safety and inspection tracking
Site managers track safety issues and inspection progress. The API reads tasks, approvals, safety issues, observations, and inspection and test plan registrations, so a dashboard can report open items per project.
List a project's safety issues and inspection plan registrations and summarize open items
Agent-driven field assistant
A field assistant can answer project questions and file documents. Through Jentic, an agent resolves a request about a project into reading its files and tasks and, when asked, uploading a document through the chunked upload flow.
Read a project's open tasks and files, then upload a new document to the right file area
Key Endpoints
59 endpoints — dalux field is a construction field-management platform, and this api (trybuildapi) exposes its project data.
METHOD
PATH
DESCRIPTION
GET
/5.1/projects
Get all available projects
GET
/5.0/projects/{projectId}
Get a specific project
GET
/5.1/projects/{projectId}/file_areas
Get a project's file areas
GET
/6.0/projects/{projectId}/file_areas/{fileAreaId}/files
Browse files in a file area
GET
/5.1/projects/{projectId}/tasks
Retrieve tasks, approvals, and safety issues
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Dalux wiring is one company API key plus 59 project operations with versioned path prefixes. With Jentic One you install once, import the operations you need from the API Directory, and keep the key in one place.
Permission scoping
Projects, file areas, and files are addressed by ids in the path, so you can scope an agent to specific projects and to read operations while keeping file uploads out of reach.
Credential isolation
Your Dalux API key is stored encrypted by your own Jentic One instance and injected when a call runs, so it never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents find the right Dalux operation through Jentic's intent search, matching a request like listing a project's files to the matching endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Dalux Field API through Jentic.
How does the Dalux Field API authenticate?
Dalux expects a company-specific API key in the `X-API-KEY` header, tied to an API identity in your Dalux settings. Jentic One stores that key and injects it at execution time.
Can I limit what my agent is allowed to do with Dalux Field?
Yes. Projects, file areas, and files are addressed by ids in the path, and the surface is almost entirely read plus file upload, so you can scope an agent to reading documents on specific projects while withholding uploads.
Can the API upload files?
Yes, through a chunked upload flow: create an upload slot, send the parts, then finalize the upload so the file lands in the chosen file area.
Does Dalux Field cover drawings and documents?
Yes. File areas, folders, files, and version sets hold the project's documents and drawings, and the API can retrieve file content and revision history.
What is TryBuildAPI?
TryBuildAPI is the title of the Dalux Field OpenAPI spec; it is the same interface described here for reading Dalux Field project data and uploading files.
GET STARTED