Jet.Build API Reference

Log in and retrieve token

Submit credentials as form fields. JSON request bodies are not supported. Returns the user's existing token; it does not create, rotate or refresh tokens.

Encoding: application/x-www-form-urlencoded

curl --request POST "https://api.jet.build/login" \
  -H "Accept: application/json" \
  --data-urlencode "email=user@example.com" \
  --data-urlencode "password=YOUR_PASSWORD"

{
  "email": "user@example.com",
  "display_name": "Example User",
  "user_name": "Example User",
  "token": "YOUR_API_TOKEN"
}

Login objects

{
  "email": "user@example.com",
  "display_name": "Example User",
  "user_name": "Example User",
  "token": "YOUR_API_TOKEN"
}

Login errors

400 Bad Request

email or password field missing. Body is null.

401 Unauthorized

Invalid credentials. Body is null, no reason given.

Other

A missing token record is not handled locally; status depends on global error handling.

Pending confirmation: Token expiration, rotation and revocation; Rate limits and account lockout; MFA / SSO accounts and password login; CORS settings for browser integrations.

List available projects

Returns organization projects and external assignments. No pagination, search or filtering. A project can appear in both arrays — deduplicate by pk.

curl --get "https://api.jet.build/projects" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json"

{
  "org_projects": [
    { "pk": 123, "title": "Example Office Project", "status": "<status label>" }
  ],
  "ext_projects": [
    { "pk": 456, "title": "Example Residential Project", "status": "<status label>" }
  ]
}

Retrieve project details

Including project_pk selects the detail operation. The response does not include pk — keep the value you sent.

curl --get "https://api.jet.build/projects" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123"

Projects objects

{ "pk": 123, "title": "Example Office Project", "status": "<status label>" }

{
  "title": "Example Project",
  "project_uuid": "11111111-1111-4111-8111-111111111111",
  "access_type": "admin",
  "organization_id": 10,
  "companies": "…",
  "groups": [{ "pk": 12, "title": "Design Team", "members": "…" }],
  "users": ["manager@example.com"],
  "user_apps": { "RFIs": true, "Tasks": true, "…": true },
  "timezone": "America/New_York",
  "iso2": "US",
  "workflows": "…"
}

{ "pk": 12, "title": "Design Team", "members": "…" }

{
  "Daily Reports": true, "Drawings": true, "Disciplines": true,
  "Files": true, "Observations": true, "Punch Lists": true,
  "RFIs": true, "Submittals": true, "Tasks": true
}

Projects status values

Projects errors

401 Unauthorized

Unauthenticated, or user has no access to the project. Body is null.

Other

Unknown or invalid project_pk is not handled locally; do not assume 404.

List project reports

Returns every report for a project, newest date first, with main reports before subreports for the same date.

curl --get "https://api.jet.build/reports" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123" \
  --data-urlencode "iso2=US"

Create a report or subreport

Creates a main report, or a contractor subreport when contractor is present. Some data is copied from the latest previous report.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/reports" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "project_pk=123" \
  --form-string "iso2=US" \
  --form-string "report_date=11/09/2026"

Retrieve report details

Returns the full report, including every section, files, photos and weather.

curl --get "https://api.jet.build/reports/details/456" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "iso2=US"

Finalize a report

Marks the report final with the signed-in user's attribution and emails the project's report distribution list.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/reports/details/456" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "timezone=America/New_York" \
  --form-string "iso2=US"

Add a workforce entry

Inserts a workforce entry at a position. PUT updates an entry; DELETE removes one.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/reports/workforce" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "report_pk=456" \
  --form-string "position=1" \
  --form-string "company_name=Example Contractor" \
  --form-string "workers=8" \
  --form-string "hours=8" \
  --form-string "ot_hours=0" \
  --form-string "ot_rate=1.5" \
  --form-string "notes=Installed framing on level 2."

{
  "position": 1,
  "company": "Example Contractor",
  "workers": 8,
  "hours": 8.0,
  "ot_rate": 1.5,
  "ot_hours": 0.0,
  "notes": "Installed framing on level 2."
}

Add other section entries

Same pattern for inspections, equipment, deliveries, miscellaneous and safety: POST inserts, PUT (with current_position) replaces and moves, DELETE removes by position.

Encoding: multipart/form-data (DELETE reads request.data)

curl --request POST "https://api.jet.build/reports/inspections" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "report_pk=456" \
  --form-string "position=1" \
  --form-string "inspection=Framing inspection" \
  --form-string "inspection_by=City inspector" \
  --form-string "inspection_time=02:30 PM" \
  --form-string "notes=Passed."

Upload a report file

Uploads one file to a report at a position.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/reports/files" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "report_pk=456" \
  --form-string "project_pk=123" \
  --form-string "organization_id=10" \
  --form-string "position=1" \
  --form-string "title=Delivery Ticket" \
  --form "filename=@./delivery-ticket.pdf"

{
  "position": 1,
  "title": "Delivery Ticket",
  "file": "10/projects/123/reports/456/files/delivery-ticket.pdf",
  "filename": "delivery-ticket.pdf"
}

Upload photos

Appends one or more photos to a report. Repeat filename for each photo.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/reports/photos" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "organization_id=10" \
  --form-string "project_pk=123" \
  --form-string "report_pk=456" \
  --form-string "location=Level 2" \
  --form-string "notes=Framing progress." \
  --form-string "photo_time=02:30 PM" \
  --form "filename=@./photo-1.jpg" \
  --form "filename=@./photo-2.jpg"

Update photo details

Updates time, location and notes on the first photo with an exact filename match. The image itself is not replaced.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/reports/photos" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "report_pk=456" \
  --form-string "filename=photo-1.jpg" \
  --form-string "photo_time=02:30 PM" \
  --form-string "location=Level 2" \
  --form-string "notes=Framing complete."

Add a quantity

Adds a line-item quantity to a report. Progress is based on today's amount only.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/reports/quantities" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "report_pk=456" \
  --form-string "position=1" \
  --form-string "today=25.5" \
  --form-string "line_item_total=400" \
  --form-string "line_item_id=88" \
  --form-string "line_item_title=Concrete slab" \
  --form-string "line_item_units=CY"

Update a quantity

Updates today's amount and recalculates the running total from earlier reports. Reads request.data (JSON).

Encoding: application/json

curl --request PUT "https://api.jet.build/reports/quantities" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  --data '{"report_pk":456,"current_position":1,"position":1,"today":25.5}'

Daily Reports objects

{ "date": "11/09/2026", "display": "Nov 09, 2026" }

{ "position": 1, "company": "Example Contractor", "workers": 8, "hours": 8.0, "ot_rate": 1.5, "ot_hours": 0.0, "notes": null }

{ "position": 1, "title": "Framing inspection", "by": "City inspector", "time": "02:30 PM", "notes": "Passed." }

{ "pk": 88, "position": 1, "title": "Concrete slab", "units": "CY", "today": 25.5, "to_date": 125.5, "total": 400.0, "progress": 31.38 }

{
  "file": "10/projects/123/reports/456/photo-1.jpg",
  "filename": "photo-1.jpg",
  "location": "Level 2",
  "time": "02:30 PM",
  "notes": "Framing progress."
}

{ "morning": { "time": "...", "temp": 0, "prec": 0, "wind": 0, "icon": "..." }, "noon": { ... }, "evening": { ... }, "units": { ... } }

Daily Reports status values

Daily Reports errors

401 Unauthorized

Missing or invalid token. Response data is null.

304 Not Modified

File upload with no file.

400 Bad Request

Photo DELETE (not implemented).

Other

Unknown ids, missing fields, invalid positions or quantities, division by zero and storage failures are handled by global exception handling.

Silent fallbacks

Invalid numbers become 0, invalid times and incident ids become null, unmatched photo updates and empty photo uploads still return 200.

Retries

No idempotency or locking. Repeats can duplicate reports, entries, files or photos, resend finalization emails, or delete a different entry. Read details before retrying.

Partial completion

Reports save before background work finishes; files may upload before the report saves. updated_at is not reliable for sync.

Pending confirmation: Canonical root URL: /reports or /reports/; Deployed multipart PUT and JSON parser configuration; Global permission and error handling; Request, file-size and photo-format limits; default_weather and weather units; Undocumented routes: /reports/correspondences, /reports/download-photos/<project_pk>, /reports/download-reports/<project_pk>; Line-item lookup endpoint and quantity business rules; Parent workforce duplication during subreport creation; Daily Report Ball-in-Court email preference selection; Any intended restriction on editing finalized reports.

List project disciplines

Ordered by title ascending. An empty array does not prove the project exists.

curl --get "https://api.jet.build/drawings/disciplines/123" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json"

[
  { "pk": 45, "title": "Architectural", "uuid": "11111111-1111-4111-8111-111111111111" },
  { "pk": 46, "title": "Structural", "uuid": "22222222-2222-4222-8222-222222222222" }
]

Current sheets for a discipline

Returns the discipline's current sheets. Item schema, ordering and version rules are pending confirmation.

curl --get "https://api.jet.build/drawings/disciplines/latest/45" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json"

Sheet titles for a discipline

Returns titles only — no numbers or versions. Do not use it to find sheet numbers for revision uploads.

curl --get "https://api.jet.build/drawings/sheets/45" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json"

["Ground Floor Plan", "Second Floor Plan", ""]

Upload sheets or revisions

Upload one PDF. Page N maps to updated_sheets[N]. Existing sheet numbers get a new version; new numbers create sheets. Processing runs in the background.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/drawings/sheets/45" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form "filename=@./architectural-revisions.pdf" \
  --form-string 'updated_sheets=["A-101","A-102","A-103"]' \
  --form-string "drawing_set_id=NA" \
  --form-string "organization_id=10" \
  --form-string "project_pk=123" \
  --form-string 'intended_for_groups=[12,34]' \
  --form-string 'intended_for=["manager@example.com"]'

Current sheets across a project

Flat array of current sheets across all disciplines. Use these values to build an RFI linked_sheet reference.

curl --get "https://api.jet.build/drawings/get-sheets/123" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json"

[
  {
    "discipline": 45,
    "number": "A-101",
    "title": "Ground Floor Plan",
    "version": 0,
    "file": "10/projects/123/drawings/45/A-101/0"
  }
]

Drawings objects

{ "pk": 45, "title": "Architectural", "uuid": "11111111-1111-4111-8111-111111111111" }

{ "discipline": 45, "number": "A-101", "title": "Ground Floor Plan", "version": 0, "file": "10/projects/123/drawings/45/A-101/0" }

{
  "number": "A-101",
  "position": 1,
  "title": "",
  "obsolete": false,
  "versions": [
    { "number": 0, "set": null, "file": "10/projects/123/drawings/45/A-101/0", "annots": [] }
  ],
  "sketches": []
}

{ "number": 0, "set": null, "file": "10/projects/123/drawings/45/A-101/0", "annots": [] }

Drawings status values

Drawings errors

401 Unauthorized

Missing or invalid token. Body is null.

404 Not Found

Unknown discipline on the latest-sheets endpoint only.

Other

Missing fields, bad JSON or invalid PDFs are not handled locally.

Pending confirmation: Routes /drawings/copy-discipline, /drawings/sets/{project_pk} and /drawings/sketches/ are registered but not yet documented..

Retrieve top-level folders

Lists folders with no parent for the project. The path value 0 represents the project folder root; it is not an actual folder record. Root-level files and links are not returned by this operation.

curl --get "https://api.jet.build/files/folders/0" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123"

{
  "folders": [
    {
      "pk": 45,
      "folder_name": "Contracts"
    }
  ],
  "files": null,
  "links": null,
  "path": null
}

Browse a folder

Returns a folder's immediate child folders, the files and live links directly in it, and its hierarchy path. Use a nonzero folder database primary key.

curl --get "https://api.jet.build/files/folders/45" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "organization_id=10"

Create a folder

Creates a folder. Use folder_id = 0 for a top-level folder, or an existing folder's database primary key to create a child.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/files/folders/0" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "folder_name=Contract Documents" \
  --form-string "project_pk=123"

{
  "pk": 45,
  "folder_name": "Contract_Documents",
  "folder_id": "11111111-1111-4111-8111-111111111111"
}

Upload files and return records

Creates file records and returns their serialized details. No email distribution is queued by this POST branch.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/files/files" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "organization_id=10" \
  --form-string "project_pk=123" \
  --form-string "folder_id=45" \
  --form-string "file_path=Contracts/" \
  --form-string "timezone=America/New_York" \
  --form "filename=@./agreement.pdf" \
  --form "filename=@./schedule.xlsx"

Upload files with email distribution

Creates new file records and queues a new-files email. This operation does not edit or replace an existing file record.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/files/files" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "organization_id=10" \
  --form-string "project_id=123" \
  --form-string "folder_id=45" \
  --form-string "timezone=America/New_York" \
  --form-string "project_name=Example Project" \
  --form-string "add_text=Please review the attached documents." \
  --form-string "intended_for=manager@example.com" \
  --form-string "intended_for_groups=12" \
  --form "filename0=@./agreement.pdf" \
  --form "filename1=@./schedule.xlsx"

Create a live link

Creates a named link within a folder. Links are retrieved through folder browsing.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/files/links" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "folder_id=45" \
  --form-string "project_pk=123" \
  --form-string "link_name=Project Resource" \
  --form-string "link_url=https://example.com/project-resource" \
  --form-string "timezone=America/New_York"

Files objects

{
  "pk": 789,
  "uploaded_on_local": "Mon Nov 09, 2026 at 03:30 PM",
  "distributions": [],
  "object_details": {
    "file_path": "10/projects/123/files/Contracts/agreement.pdf",
    "document_url": "<generated download URL>",
    "file_name": "agreement.pdf",
    "is_office": false,
    "is_image": false,
    "size": {
      "display": "250.00KB",
      "amount": 250
    }
  }
}

{
  "display": "1.25MB",
  "amount": 1.25
}

{
  "pk": 321,
  "link_name": "Project Resource",
  "link_url": "https://example.com/project-resource",
  "uploaded_on_local": "Mon Nov 09, 2026 at 03:30 PM"
}

Files status values

Files errors

401 Unauthorized

Unauthenticated requests; the view sets response data to null. The is_public folder flag does not remove the authentication requirement.

403 Forbidden

Failed folder browsing access check; response data is null.

404 Not Found

Unknown nonzero folder identifier during browsing; response data is null.

400 Bad Request

Unimplemented branches: DELETE /files/folders/<folder_id>, PUT /files/folders/<folder_id>, DELETE /files/files and DELETE /files/links do not perform deletion or editing. Do not infer folder renaming, moving, deletion, file replacement or link deletion.

Form parsing

GET uses path and query parameters; POST and PUT read form fields from request.POST, not assumed JSON. File uploads use multipart/form-data; when using JavaScript FormData, do not manually specify Content-Type. Deployed multipart PUT parsing remains to verify.

Other

Missing required fields, invalid time zones, invalid numeric or email group identifiers, missing referenced records, storage upload failures, file-size lookup failures, serialization failures and notification submission failures are not handled locally; global error handling determines those responses.

Partial completion

A folder is saved before recipient processing; POST upload stores files and creates records before returning; PUT upload creates records before queuing its email. A failure can occur after some work has completed.

Retries

No idempotency mechanism is shown. Repeated requests can create duplicate folders, file records or live links and repeat distribution emails. Filename collisions may target the same storage key. Inspect folder contents before retrying an uncertain mutation.

Pending confirmation: Registered routes /files/copy-skeleton and /files/bulk-actions: view implementations were not supplied, so methods and behavior are not established; LiveLinks model constraints; File distribution-history item schema; get_obj_files output used for email attachments (files processed with expires=604800, uploaded_on=False); Global permission and error handling; Upload limits and accepted file types; Filename collision policy; Confirmation of deployed multipart PUT parsing.

List project inspections

Returns project inspections ordered by inspection_date descending. Same-date ordering is not defined. No pagination, status/date-range filters, search or custom sorting is implemented.

curl --get "https://api.jet.build/inspections" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

[
  {
    "pk": 456,
    "title": "Level 2 Framing Inspection",
    "inspection_id": "11111111-1111-4111-8111-111111111111",
    "inspection_date": {
      "date": "11/20/2026",
      "display": "Nov 20, 2026"
    },
    "inspection_by": "Example Inspector",
    "inspection_time": "02:30 PM",
    "status": {
      "status": "UPCOMING",
      "days_overdue": -5
    },
    "bic": {
      "groups": [],
      "users": [
        "inspector@example.com"
      ]
    }
  }
]

Retrieve one inspection

Reads the inspection and its checklist by database primary key. project_pk does not constrain the detail lookup in the supplied view.

curl --get "https://api.jet.build/inspections" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "inspection_pk=456" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

Create an inspection

Creates an open inspection and optionally copies checklist items from a QA/QC list. Creation does not read a submitted status. No created_by field is stored; notifications identify the authenticated user separately.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/inspections" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "title=Level 2 Framing Inspection" \
  --form-string "notes=Review framing before wall closure." \
  --form-string "project_id=123" \
  --form-string "inspection_date=11/20/2026" \
  --form-string "inspection_time=02:30 PM" \
  --form-string "inspection_by=Example Inspector" \
  --form-string "linked_list=NA" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "timezone=America/New_York" \
  --form-string "iso2=US" \
  --form-string "intended_for=manager@example.com" \
  --form-string "wf1_emails=inspector@example.com"

{
  "pk": 456,
  "inspection_id": "11111111-1111-4111-8111-111111111111",
  "title": "Level 2 Framing Inspection",
  "status": {
    "status": "UPCOMING",
    "days_overdue": 0
  },
  "bic": {
    "groups": [],
    "users": [
      "inspector@example.com"
    ]
  }
}

Edit inspection details and status

Replaces title, date, inspector attribution, notes, time, status and the entire workflow. Recipients (ccd), checklist items, project association and existing attachment contents are not replaced.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/inspections" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "inspection_pk=456" \
  --form-string "put_type=inspection" \
  --form-string "title=Level 2 Framing Inspection" \
  --form-string "notes=Review framing before wall closure." \
  --form-string "inspection_date=11/20/2026" \
  --form-string "inspection_time=02:30 PM" \
  --form-string "inspection_by=Example Inspector" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "timezone=America/New_York" \
  --form-string "iso2=US" \
  --form-string "wf1_emails=inspector@example.com" \
  --form-string "status=pass" \
  --form-string "wf1_complete=1"

Upload inspection attachments

Appends files to the inspection-level files array. Retrieve inspection details after uploading.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/inspections" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "inspection_pk=456" \
  --form-string "put_type=files" \
  --form-string "timezone=America/New_York" \
  --form-string "organization_id=10" \
  --form-string "project_id=123" \
  --form "filename0=@./inspection-photo.jpg" \
  --form "filename1=@./inspection-record.pdf"

Add a checklist item

Inserts an incomplete item with no files and repositions all stored items sequentially from 1.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/inspections/items/456" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "inspection_pk=456" \
  --form-string "position=1" \
  --form-string "title=Verify framing alignment" \
  --form-string "notes=Review Grid B before wall closure."

{
  "timestamp": 1794236400,
  "position": 1,
  "title": "Verify framing alignment",
  "notes": "Review Grid B before wall closure.",
  "complete": false,
  "files": []
}

Edit or move a checklist item

Selects an item by zero-based source index and moves it to a one-based destination. Timestamp, completion and attachments are retained; all positions are renumbered.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/inspections/items/456" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "inspection_pk=456" \
  --form-string "previous_position=0" \
  --form-string "put_type=item" \
  --form-string "new_position=2" \
  --form-string "title=Verify revised framing alignment" \
  --form-string "notes=Include the revised detail at Grid B."

Toggle checklist completion

Toggles false to true or true to false. No desired complete value is read. This operation is not idempotent: repeating it reverses the change.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/inspections/items/456" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "inspection_pk=456" \
  --form-string "previous_position=0" \
  --form-string "put_type=complete"

Upload checklist item attachments

Appends files to the selected item's files array, separate from inspection-level attachments.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/inspections/items/456" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "inspection_pk=456" \
  --form-string "previous_position=0" \
  --form-string "put_type=files" \
  --form-string "timezone=America/New_York" \
  --form-string "organization_id=10" \
  --form-string "project_id=123" \
  --form "filename0=@./alignment-photo.jpg"

Inspections objects

{
  "pk": 456,
  "inspection_id": "11111111-1111-4111-8111-111111111111",
  "title": "Level 2 Framing Inspection",
  "inspection_date": {
    "date": "11/20/2026",
    "display": "Nov 20, 2026"
  },
  "inspection_by": "Example Inspector",
  "inspection_time": "02:30 PM",
  "status": "opn",
  "status_display": {
    "status": "UPCOMING",
    "days_overdue": 0
  },
  "ccd": {
    "groups": [
      12
    ],
    "users": [
      "manager@example.com"
    ]
  },
  "responses": [],
  "files": [],
  "items": [],
  "notes": "Review framing before wall closure.",
  "workflow": [],
  "bic": null
}

{
  "timestamp": 1794236400,
  "position": 1,
  "title": "Verify framing alignment",
  "notes": "Review Grid B before wall closure.",
  "complete": false,
  "files": []
}

[
  {
    "groups": [
      12
    ],
    "users": [
      "inspector@example.com"
    ],
    "complete": false
  }
]

{
  "file": "10/projects/123/inspections/456/inspection-record.pdf",
  "filename": "inspection-record.pdf",
  "uploaded_on": "Mon Nov 09, 2026 at 03:30 PM"
}

Inspections status values

Inspections errors

401 Unauthorized

Missing authentication; view response data is null. Additional project/role authorization is not established by the supplied views.

405

Unsupported root inspection put_type falls through to HTTP 405.

Unsupported item PUT

Use only item, complete or files. The item is removed before put_type is checked; an unsupported value saves the array without reinserting it and returns HTTP 200 with the removed item. Do not rely on error rejection.

Form parsing

POST/PUT read request.POST, not assumed JSON. Use form fields; for files use multipart/form-data and distinct filename-prefixed fields. Let FormData supply Content-Type/boundary. Deployed PUT parsing remains to verify.

Other

Unknown inspection/list, missing fields, invalid zones/groups/indices, upload or job-submission failures have no locally structured errors; global exception handling determines responses.

Retries

No idempotency mechanism. Repeated creation can duplicate inspections/items; uploads append again; completion toggles back; edits can queue further emails/jobs. Reconcile current state before uncertain retries.

Partial completion

Inspection may save before notification/time-zone failure; files may upload before save succeeds. A failed request does not establish that nothing changed.

Concurrent changes

Checklist operations read/modify/save the whole items array without shown locking/version checks. Coordinate writes and refresh indices to avoid overwriting changes or addressing the wrong item.

Pending confirmation: Canonical root URL slash behavior (/inspections or /inspections/); item route has no trailing slash; Deployed form parsing for PUT; Global project permissions and error handling; File-size limits and supported types; File download handling; QA/QC list lookup endpoint; Groups and Directory lookup endpoints.

List project punch list items

Returns every item for a project, ordered by database primary key descending. No pagination, search, date filtering, completion filtering or custom sorting.

curl --get "https://api.jet.build/punch-lists" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

Retrieve one item

The presence of item_pk selects single-item retrieval. The lookup uses item_pk directly; a project_pk parameter does not constrain it in this view.

curl --get "https://api.jet.build/punch-lists" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "item_pk=456" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

Create a standard item

Creates an item with an optional linked drawing reference. Do not include from_sheet — its presence (even from_sheet=false) selects drawing-pinned creation.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/punch-lists" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "title=Repair damaged wall finish" \
  --form-string "about=Repair and repaint the damaged finish near Door 201." \
  --form-string "new_number=27" \
  --form-string "linked_sheet=NA" \
  --form-string "project_id=123" \
  --form-string "created_by=Example User" \
  --form-string "due_by=11/20/2026" \
  --form-string "iso2=US" \
  --form-string "timezone=America/New_York" \
  --form-string "organization_id=10" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "location=Level 2 Corridor" \
  --form-string "contractor=Example Contractor" \
  --form-string "intended_for=manager@example.com" \
  --form-string "wf1_emails=contractor@example.com" \
  --form "filename0=@./damaged-finish.jpg"

Create an item pinned to a drawing

The presence of from_sheet selects drawing-pinned creation — even from_sheet=false. Omit the field entirely for standard creation. new_number and linked_sheet are not read in this branch.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/punch-lists" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "title=Repair damaged wall finish" \
  --form-string "about=Repair and repaint the damaged finish near Door 201." \
  --form-string "project_id=123" \
  --form-string "created_by=Example User" \
  --form-string "due_by=11/20/2026" \
  --form-string "iso2=US" \
  --form-string "timezone=America/New_York" \
  --form-string "organization_id=10" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "from_sheet=1" \
  --form-string "discipline_pk=45" \
  --form-string "sheet_no=A-101" \
  --form-string "version_no=0" \
  --form-string "X=125.5" \
  --form-string "Y=240.0"

Full item update

Replaces multiple fields; this is not a partial update. Omit from_mobile — its presence selects the limited update. Verify deployed form parsing for PUT.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/punch-lists" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "item_object_pk=456" \
  --form-string "title=Repair damaged wall finish" \
  --form-string "about=Repair and repaint the finish near Door 201." \
  --form-string "due_by=11/23/2026" \
  --form-string "iso2=US" \
  --form-string "linked_sheet=NA" \
  --form-string "status=incomplete" \
  --form-string "timezone=America/New_York" \
  --form-string "organization_id=10" \
  --form-string "project_id=123" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "location=Level 2 Corridor" \
  --form-string "contractor=Example Contractor" \
  --form-string "wf1_emails=contractor@example.com"

Limited update (title, description, completion)

The presence of from_mobile selects the limited branch — even from_mobile=false. Despite the name, the branch is selected by the form field rather than the client platform. Omit the field for full updates.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/punch-lists" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "item_object_pk=456" \
  --form-string "from_mobile=1" \
  --form-string "title=Repair damaged wall finish" \
  --form-string "about=Repair completed and ready for verification." \
  --form-string "status=complete"

Punch Lists objects

{
  "pk": 456,
  "title": "Repair damaged wall finish",
  "about": "Repair and repaint the damaged finish near Door 201.",
  "item_number": 27,
  "item_id": "22222222-2222-4222-8222-222222222222",
  "due_by": { "date": "11/20/2026", "display": "Nov 20, 2026" },
  "is_complete": false,
  "status": "OPEN",
  "days_overdue": -5,
  "created_by": "Example User",
  "sent_on_local": "Mon Nov 09, 2026 at 03:30 PM",
  "responsible_contractor": "Example Contractor",
  "location": "Level 2 Corridor",
  "sheet": { "discipline": "45", "number": "A-101", "version": "0" },
  "bic": { "groups": [12], "users": ["contractor@example.com"] }
}

{
  "pk": 456,
  "title": "Repair damaged wall finish",
  "item_number": 27,
  "status": "OVERDUE",
  "days_overdue": 3,
  "ccd": { "groups": [12, 34], "users": ["manager@example.com", "owner@example.com"] },
  "responses": [
    { "text": "Work corrected.", "user": "contractor@example.com", "name": "Example Contractor", "on": "11/12/2026", "status": "WORK CORRECTED", "timestamp": 1794236400, "files": [] }
  ],
  "file": [
    { "file": "10/projects/123/punches/1794236400/photo.jpg", "filename": "photo.jpg", "uploaded_on": "Mon Nov 09, 2026 at 03:30 PM", "document_url": "<presigned download URL>" }
  ],
  "workflow": [
    { "groups": [12], "users": ["contractor@example.com"], "complete": false }
  ],
  "distributions": []
}

{
  "file": "10/projects/123/punches/1794236400/photo.jpg",
  "filename": "photo.jpg",
  "uploaded_on": "Mon Nov 09, 2026 at 03:30 PM",
  "document_url": "<presigned download URL>"
}

{
  "text": "Work corrected.",
  "user": "contractor@example.com",
  "name": "Example Contractor",
  "on": "11/12/2026",
  "status": "WORK CORRECTED",
  "timestamp": 1794236400,
  "files": []
}

{
  "discipline": "45",
  "number": "A-101",
  "version": "0",
  "X": "125.5",
  "Y": "240.0"
}

Punch Lists status values

Punch Lists errors

401 Unauthorized

Unauthenticated requests; the view sets response data to null. Additional project and role authorization is not established by the supplied view.

Unsupported methods

Only GET, POST and PUT are declared. DELETE is not supported by this view; no item deletion operation is implemented.

Form parsing

GET uses query parameters. POST and PUT read form fields from request.POST — do not assume application/json bodies are supported. Attachments use multipart/form-data; when using JavaScript FormData, do not manually specify Content-Type. Deployed form parsing, especially for PUT, remains to verify.

Dates

An unparseable date silently becomes the server's current date under the shared date parser. Only the exact uppercase value US selects month-first parsing. Validate dates before submission.

Retries

No idempotency mechanism is shown. Repeated POST requests can create duplicate items and trigger additional notifications; repeated full updates containing files can append attachments again; repeated incomplete-item updates can send additional Ball-in-Court emails. Reconcile current item state before retrying uncertain writes.

Partial completion

Creation saves the item before activity logging and notification submission; full updates save before their conditional logging and email processing. A request can fail after data has already been stored.

Other

Unknown item identifiers, missing required fields, invalid time zones, invalid group identifiers, malformed drawing references, storage failures and notification submission failures are not handled locally; global error handling determines those responses. Do not assume unknown items return a particular 404 response.

Pending confirmation: Canonical root URL slash behavior; Deployed form parsing for PUT; Global permissions and error responses; Upload limits and accepted file types; PDF coordinate origin, rotation handling and bounds; Distribution-history item schema; Groups and Directory lookup endpoints.

List RFIs for a project

Ordered by descending pk. No pagination, search or filters.

curl --get "https://api.jet.build/rfis" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

Retrieve one RFI

Including rfi_pk returns one RFI instead of a list. The UUID (rfi_id) is not accepted.

curl --get "https://api.jet.build/rfis" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "rfi_pk=456" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

Create an RFI

The caller supplies the RFI number and subnumber. New RFIs default to open.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/rfis" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "rfi_title=Clarify slab edge detail" \
  --form-string "new_number=27" \
  --form-string "sub_rfi_number=0" \
  --form-string "about=Please confirm the slab edge dimension at Grid B." \
  --form-string "project_id=123" \
  --form-string "created_by=Example User" \
  --form-string "due_by=11/05/2026" \
  --form-string "iso2=US" \
  --form-string "timezone=America/New_York" \
  --form-string "linked_sheet=NA" \
  --form-string "organization_id=10" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "intended_for=manager@example.com" \
  --form-string "wf1_emails=architect@example.com" \
  --form "filename0=@./detail.pdf"

Update, close or reopen an RFI

Not a partial update — send every field you want to keep. Omitted optional values reset to defaults and omitted workflow fields clear the workflow.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/rfis" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "rfi_object_pk=456" \
  --form-string "rfi_title=Clarify slab edge detail" \
  --form-string "about=Please confirm the revised slab edge dimension." \
  --form-string "due_by=11/06/2026" \
  --form-string "iso2=US" \
  --form-string "linked_sheet=NA" \
  --form-string "status=opn" \
  --form-string "timezone=America/New_York" \
  --form-string "organization_id=10" \
  --form-string "project_id=123" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "wf1_emails=architect@example.com"

RFIs objects

{
  "pk": 456,
  "rfi_id": "33333333-3333-4333-8333-333333333333",
  "title": "Clarify slab edge detail",
  "number": 27,
  "sub_number": 0,
  "due_by": { "date": "11/05/2026", "display": "Nov 05, 2026" },
  "is_open": true,
  "status": { "status": "OPEN", "days_overdue": -8 },
  "created_by": "Example User",
  "sent_on_local": "Wed Oct 28, 2026 at 03:30 PM",
  "updated_at": "…",
  "sheet": {},
  "from_contractor": null,
  "bic": { "groups": [], "users": ["architect@example.com"] }
}

{
  "pk": "456",
  "title": "Clarify slab edge detail",
  "about": "Please confirm the slab edge dimension at Grid B.",
  "is_open": true,
  "is_bid_rfi": false,
  "from_contractor": null,
  "cost_impact": "0.00",
  "schedule_impact": "0.00",
  "due_by": { "date": "11/05/2026", "display": "Nov 05, 2026" },
  "status": { "status": "OPEN", "days_overdue": -8 },
  "tags": "",
  "sheet": {},
  "ccd": { "groups": [], "users": ["manager@example.com"] },
  "responses": [],
  "file": [],
  "workflow": [{ "groups": [], "users": ["architect@example.com"], "complete": false }],
  "distributions": []
}

{
  "pk": 456,
  "rfi_id": "33333333-3333-4333-8333-333333333333",
  "title": "Clarify slab edge detail",
  "number": "27",
  "sub_number": "0",
  "due_by": { "date": "11/05/2026", "display": "Nov 05, 2026" },
  "is_open": true,
  "status": { "status": "OPEN", "days_overdue": -8 },
  "created_by": "Example User",
  "sent_on_local": "Wed Oct 28, 2026 at 03:30 PM",
  "sheet": {},
  "ball_in_court": { "groups": [], "users": ["architect@example.com"] }
}

// linked_sheet = 45|*|A-101|*|0
{ "discipline": "45", "number": "A-101", "version": "0" }

{
  "text": "Please use the revised detail.",
  "user": "architect@example.com",
  "name": "Example Architect",
  "on": "Wed Oct 28, 2026 at 04:15 PM",
  "accepted": false,
  "accepted_by": null,
  "accepted_on": null,
  "timestamp": 1793218500,
  "files": [{ "file": "example/path/revised-detail.pdf", "filename": "revised-detail.pdf" }]
}

RFIs status values

RFIs errors

401 Unauthorized

Missing or invalid token.

Other

Missing fields, unknown ids, bad time zones and upload failures are not handled locally.

Invalid date

Silently replaced with the server's current date — validate before sending.

List project submittals and versions

Returns parents grouped with their matching versions. Parents are ordered by descending pk; versions by descending version number. Parents with no matching versions are omitted. No pagination, search or client sorting.

curl --get "https://api.jet.build/submittals" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

[
  {
    "submittal": {
      "pk": 456,
      "number": "27",
      "title": "Interior Door Hardware",
      "display": "#27 Interior Door Hardware",
      "specification": null,
      "specification_sbm_number": null,
      "status": { "status": "...", "display": "..." },
      "responsible": null,
      "bic": null
    },
    "versions": [
      {
        "pk": 789,
        "version": { "version": 1, "display": "01" },
        "version_id": "VERSION_UUID",
        "about": "Product data and hardware schedule for review.",
        "status": { "status": "opn", "display": "..." },
        "due_by": { "date": "11/20/2026", "display": "Nov 20, 2026" },
        "received_on": { "date": null, "display": "" },
        "created_by": "Example User",
        "sent_on_local": "...",
        "accepted_final": false,
        "accepted_by": null,
        "accepted_on": null,
        "bic": "..."
      }
    ]
  }
]

Retrieve a parent submittal

Returns parent details plus settings from the version with the highest version number.

curl --get "https://api.jet.build/submittals" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "submittal_pk=456" \
  --data-urlencode "iso2=US"

Create a submittal and Version 1

Saves the parent, then creates Version 1 through the shared version helper.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/submittals" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "submittal_name=Interior Door Hardware" \
  --form-string "new_number=27" \
  --form-string "project_id=123" \
  --form-string "registry_item=NA" \
  --form-string "spec_section=NA" \
  --form-string "about=Product data and hardware schedule for review." \
  --form-string "due_by=11/20/2026" \
  --form-string "received_on=11/09/2026" \
  --form-string "iso2=US" \
  --form-string "timezone=America/New_York" \
  --form-string "created_by=Example User" \
  --form-string "organization_id=10" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "intended_for=manager@example.com" \
  --form-string "wf1_emails=architect@example.com" \
  --form "filename0=@./product-data.pdf"

Retrieve a version

Returns one version by its database primary key (not its UUID).

curl --get "https://api.jet.build/submittals/versions" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "pk=789" \
  --data-urlencode "iso2=US"

{
  "pk": 789,
  "version": 1,
  "about": "Product data and hardware schedule for review.",
  "timestamp": "...",
  "status": "opn",
  "ccd": { "groups": [12], "users": ["manager@example.com"] },
  "due_by": "11/20/2026",
  "received_on": null,
  "responses": [],
  "files": [],
  "submittal_id": 456,
  "workflow": [ { "groups": [], "users": ["architect@example.com"], "complete": false } ]
}

Create another version

Adds a version under an existing parent identified by submittal_object_pk.

Encoding: multipart/form-data

curl --request POST "https://api.jet.build/submittals/versions" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "submittal_object_pk=456" \
  --form-string "new_version_number=2" \
  --form-string "about=Revised product data addressing review comments." \
  --form-string "due_by=11/25/2026" \
  --form-string "iso2=US" \
  --form-string "timezone=America/New_York" \
  --form-string "created_by=Example User" \
  --form-string "project_id=123" \
  --form-string "organization_id=10" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "intended_for=manager@example.com" \
  --form-string "wf1_emails=architect@example.com" \
  --form "filename0=@./revised-product-data.pdf"

Update a version

Replaces due date, received date, status, description and workflow, and appends attachments. Not a partial update.

Encoding: multipart/form-data

curl --request PUT "https://api.jet.build/submittals/versions" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --form-string "version_object_pk=789" \
  --form-string "due_by=11/27/2026" \
  --form-string "received_on=11/09/2026" \
  --form-string "iso2=US" \
  --form-string "status=opn" \
  --form-string "about=Updated review package." \
  --form-string "timezone=America/New_York" \
  --form-string "organization_id=10" \
  --form-string "project_id=123" \
  --form-string "project_name=Example Project" \
  --form-string "project_uuid=11111111-1111-4111-8111-111111111111" \
  --form-string "wf1_emails=architect@example.com"

Submittals objects

Submittal #27 (pk 456)
├── Version 02 (pk 790)
└── Version 01 (pk 789)

{
  "file": "10/projects/123/submittals/456/<timestamp>/product-data.pdf",
  "filename": "product-data.pdf",
  "uploaded_on": "..."
}

Submittals status values

Submittals errors

401 Unauthorized

Missing or invalid token. Response data is null.

404 Not Found

Parent detail request with no versions for that parent.

Other

Missing fields, unknown versions, bad time zones, group ids, uploads or version numbers are handled by global exception handling.

Invalid date

Silently replaced with the server's current date — validate before sending.

Partial completion

No transaction wrapper. A parent, version or file may exist after a failure.

Pending confirmation: Exact registered endpoint paths and trailing slashes; status choices, display structures and model constraints; parent bic vs ball_in_court equivalence; responses and files item schemas; update_contractor_recipients behavior and registry reference format; final-acceptance and response endpoints; multipart PUT parsing and request limits.

List tasks for a project

Ordered by descending pk. Always supply project_pk.

curl --get "https://api.jet.build/tasks" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "project_pk=123" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

Retrieve one task

Returns the raw stored status, not a computed status object. No attachments in this response.

curl --get "https://api.jet.build/tasks" \
  -H "Authorization: Token YOUR_API_TOKEN" \
  -H "Accept: application/json" \
  --data-urlencode "task_pk=456" \
  --data-urlencode "timezone=America/New_York" \
  --data-urlencode "iso2=US"

Create a task

If new_number is omitted, the next number for the project is assigned (starting at 1).

Encoding: multipart/form-data