---
title: Sage 300 Construction and Real Estate API Integration on Truto
slug: sage300constructionandrealestate
category: Accounting
canonical: "https://truto.one/integrations/detail/sage300constructionandrealestate/"
---

# Sage 300 Construction and Real Estate API Integration on Truto



**Category:** Accounting  
**Status:** Beta

## MCP-ready AI tools

Truto exposes 66 tools for Sage 300 Construction and Real Estate that AI agents can call directly.

- **create_a_sage_300_construction_and_real_estate_auth_token** — Log in with the connected Windows user (Domain\User) and get an X-Credentials token (POST /api/common/user/authenticate). The connector calls it on connect and every 20 minutes and fills the body from the account; callers send no body.
- **list_all_sage_300_construction_and_real_estate_companies** — Returns a list of companies to which the authenticated user has access (GET /api/common/company).
- **list_all_sage_300_construction_and_real_estate_departments** — Gets the list of Payroll departments (GET /api/payroll/department). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_employees** — Gets the Payroll employee list (GET /api/payroll/employee). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_equipment** — Gets a list of the Equipment Cost equipment items (GET /api/equipment). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_equipment_cost_codes** — Gets a list of the Equipment Cost cost code items (GET /api/equipment/costcode). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **create_field_report_deletion** — Delete a field report (POST /api/fieldreports/fieldreports/delete) by Index and DateTimeStamp.
- **get_field_report_equipment_by_id** — Get a field report equipment observation by index (GET /api/fieldreports/equipment/{index}). id: the observation index.
- **create_field_report_equipment** — Save a field report equipment observation: creates it, or updates it when Index is given (POST /api/fieldreports/equipment/save).
- **create_field_report_equipment_deletion** — Delete a field report equipment observation (POST /api/fieldreports/equipment/delete) by Index and DateTimeStamp.
- **create_field_report_event_deletion** — Delete a field report event observation (POST /api/fieldreports/event/delete) by Index and DateTimeStamp.
- **get_field_report_event_by_id** — Get a field report event observation by index (GET /api/fieldreports/event/{index}). id: the observation index.
- **create_field_report_event** — Save a field report event observation: creates it, or updates it when Index is given (POST /api/fieldreports/event/save).
- **create_field_report_extra_deletion** — Delete a field report extra observation (POST /api/fieldreports/extra/delete) by Index and DateTimeStamp.
- **get_field_report_extra_by_id** — Get a field report extra observation by index (GET /api/fieldreports/extra/{index}). id: the observation index.
- **create_field_report_extra** — Save a field report extra observation: creates it, or updates it when Index is given (POST /api/fieldreports/extra/save).
- **create_field_report_finalization** — Finalize a field report so it can no longer be changed (POST /api/fieldreports/fieldreports/finalize) by Index and DateTimeStamp.
- **get_field_report_journal_entry_by_id** — Get a field report journal entry observation by index (GET /api/fieldreports/journalentry/{index}). id: the observation index.
- **create_field_report_journal_entry** — Save a field report journal entry observation: creates it, or updates it when Index is given (POST /api/fieldreports/journalentry/save).
- **create_field_report_journal_entry_deletion** — Delete a field report journal entry observation (POST /api/fieldreports/journalentry/delete) by Index and DateTimeStamp.
- **get_field_report_labor_by_id** — Get a field report labor observation by index (GET /api/fieldreports/labor/{index}). id: the observation index.
- **create_field_report_labor** — Save a field report labor observation: creates it, or updates it when Index is given (POST /api/fieldreports/labor/save).
- **create_field_report_labor_deletion** — Delete a field report labor observation (POST /api/fieldreports/labor/delete) by Index and DateTimeStamp.
- **create_field_report_material_deletion** — Delete a field report material observation (POST /api/fieldreports/material/delete) by Index and DateTimeStamp.
- **get_field_report_material_by_id** — Get a field report material observation by index (GET /api/fieldreports/material/{index}). id: the observation index.
- **create_field_report_material** — Save a field report material observation: creates it, or updates it when Index is given (POST /api/fieldreports/material/save).
- **create_field_report_payroll_time_deletion** — Delete a field report Payroll time observation (POST /api/fieldreports/payrolltime/delete) by Index and DateTimeStamp.
- **create_field_report_payroll_time_submission** — Send the Payroll time observations of a field report within a date range to Payroll (POST /api/fieldreports/payrolltime/sendtopayroll).
- **get_field_report_payroll_time_by_id** — Get a field report Payroll time observation by index (GET /api/fieldreports/payrolltime/{index}). id: the observation index.
- **create_field_report_payroll_time** — Save a field report Payroll time observation: creates it, or updates it when Index is given (POST /api/fieldreports/payrolltime/save).
- **create_field_report_subcontractor_deletion** — Delete a field report subcontractor observation (POST /api/fieldreports/subcontractor/delete) by Index and DateTimeStamp.
- **get_field_report_subcontractor_by_id** — Get a field report subcontractor observation by index (GET /api/fieldreports/subcontractor/{index}). id: the observation index.
- **create_field_report_subcontractor** — Save a field report subcontractor observation: creates it, or updates it when Index is given (POST /api/fieldreports/subcontractor/save).
- **create_field_report_visitor_deletion** — Delete a field report visitor observation (POST /api/fieldreports/visitor/delete) by Index and DateTimeStamp.
- **get_field_report_visitor_by_id** — Get a field report visitor observation by index (GET /api/fieldreports/visitor/{index}). id: the observation index.
- **create_field_report_visitor** — Save a field report visitor observation: creates it, or updates it when Index is given (POST /api/fieldreports/visitor/save).
- **create_field_report_weather_site_condition_deletion** — Delete a field report weather and site conditions observation (POST /api/fieldreports/weathersiteconditions/delete) by Index and DateTimeStamp.
- **get_field_report_weather_site_condition_by_id** — Get a field report weather and site conditions observation by index (GET /api/fieldreports/weathersiteconditions/{index}). id: the observation index.
- **create_field_report_weather_site_condition** — Save a field report weather and site conditions observation: creates it, or updates it when Index is given (POST /api/fieldreports/weathersiteconditions/save).
- **get_field_report_work_activity_by_id** — Get a field report work activities observation by index (GET /api/fieldreports/workactivities/{index}). id: the observation index.
- **create_field_report_work_activity** — Save a field report work activities observation: creates it, or updates it when Index is given (POST /api/fieldreports/workactivities/save).
- **create_field_report_work_activity_deletion** — Delete a field report work activities observation (POST /api/fieldreports/workactivities/delete) by Index and DateTimeStamp.
- **list_all_sage_300_construction_and_real_estate_field_reports** — Gets a list of field reports that match the given criteria (GET /api/fieldreports). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **get_field_report_by_id** — Get a field report with all its observations (GET /api/fieldreports/{index}). id: the field report index.
- **create_a_sage_300_construction_and_real_estate_field_report** — Save a field report: creates it, or updates it when FieldReportIndex is given (POST /api/fieldreports/fieldreports/save).
- **list_all_sage_300_construction_and_real_estate_files** — Gets the list of named files (GET /api/common/files). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_job_contacts** — Gets the list of job contacts for a Project Management job index (GET /api/jobs/contacts). Required: pjJob.
- **create_job_cost_batch_posting** — Post Job Cost batches from the new-transaction file (JCT_NEW_TRANSACTION) to the current-transaction file (POST /api/transactions/post). Pick batches from job_cost_batches.list.
- **list_all_sage_300_construction_and_real_estate_job_cost_batches** — Gets the list of Job Cost batches in the JCT_NEW_BATCH file, or the named file specified if allowed (GET /api/transactions/batch).
- **list_all_job_cost_categories** — Gets the Job Cost category items (GET /api/jobcost/category). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_job_cost_cost_codes** — Gets the Job Cost cost codes (GET /api/jobcost/costcode). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_job_cost_extras** — Gets the Job Cost extra items (GET /api/jobcost/extra). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_jobs** — Gets Job Cost job items (GET /api/jobcost/job). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_metadata** — Get the metadata (schema) of one or more classes, including Custom Descriptions and Custom Fields set up by the customer (GET /api/metadata). Required: classNames.
- **list_all_sage_300_construction_and_real_estate_metadata_classes** — Gets the list of aliases for metadata classes (GET /api/metadata/classes).
- **list_all_sage_300_construction_and_real_estate_pays** — Gets the Payroll pay items (GET /api/payroll/pay). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **create_a_sage_300_construction_and_real_estate_rfi_deletion** — Delete a Project Management RFI (POST /api/rfis/delete) by Index and DateTimeStamp.
- **list_all_sage_300_construction_and_real_estate_rfi_next_numbers** — Get the next RFI number for a Project Management job (GET /api/rfis/nextnumber). Required: pjJob.
- **list_all_sage_300_construction_and_real_estate_rfis** — Gets a list of Project Management RFIs (GET /api/rfis). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **get_single_sage_300_construction_and_real_estate_rfi_by_id** — Get a Project Management RFI (request for information) by index (GET /api/rfis/{index}). AnsweredBy, SubmittedBy, ReceivedFrom and CC hold Address Book person contact IDs.
- **create_a_sage_300_construction_and_real_estate_rfi** — Save a Project Management RFI: creates it, or updates it when Index is given (POST /api/rfis/save). Get a number from rfi_next_numbers.list.
- **create_a_sage_300_construction_and_real_estate_timesheet** — Submit an extended COSA (Construction Open Standards Alliance) timesheet to Payroll (POST /api/payroll/time/submit). The response repeats the timesheet with a Validation node (Processed, ErrorMessages).
- **list_all_sage_300_construction_and_real_estate_union_classes** — Gets the Payroll union classes (GET /api/payroll/unionclass). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_union_locals** — Gets Payroll union locals (GET /api/payroll/unionlocal). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_unions** — Gets a list of the Payroll unions (GET /api/payroll/union). The connector pages with Skip / Take, 100 rows per page; sort with SortField / SortDirection.
- **list_all_sage_300_construction_and_real_estate_versions** — Get the Sage 300 Construction and Real Estate product version as a single string (GET /api/common/version).

## How it works

1. **Link your customer's Sage 300 Construction and Real Estate account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach Sage 300 Construction and Real Estate.** The Proxy API is a 1-to-1 mapping of the Sage 300 Construction and Real Estate API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Bridge field apps to the Sage 300 CRE back office** — Offer construction field management customers a native Sage 300 CRE sync so daily logs, labor hours, and equipment usage captured on mobile devices land directly in their ERP as compliant field reports — eliminating double entry for office staff.
- **Push certified payroll and union time into Sage** — Time-tracking and workforce management SaaS can submit COSA-standard timesheets directly into Sage Payroll, respecting union, prevailing wage, and multi-class rules that generic payroll connectors can't handle.
- **Sync RFIs and change impacts with the accounting system of record** — Project management platforms can keep RFIs aligned between the field, architects, and accountants — and post resulting cost impacts as Job Cost batches so forecasts and WIP stay accurate without manual reconciliation.
- **Automate job cost actualization from third-party spend tools** — Expense, AP automation, and procurement SaaS can post approved material, equipment, and subcontractor costs into Sage Job Cost batches coded to the right job, cost code, category, and extra — giving controllers real-time budget visibility.
- **Pre-populate construction apps with Sage's job and payroll master data** — Any SaaS onboarding a construction customer can pull jobs, cost codes, categories, employees, equipment, and union structures from Sage so users never have to re-create their chart of accounts or workforce setup in a second system.

## What you can build

- **Native daily field report builder** — Let foremen compose a daily log in your app that creates a Sage field report with labor, materials, equipment, subcontractors, visitors, weather, events, and work activities attached — then finalize it in one submission.
- **COSA timesheet submission with validation handling** — Push approved weekly timesheets into Sage Payroll via the timesheet endpoint, surface validation errors back to managers inline, and route labor hours from field reports straight to payroll time submission.
- **Bidirectional RFI workflow** — Reserve the next RFI number from Sage, create and fetch RFIs with full metadata, and delete or supersede them as the PM workflow evolves — keeping the ERP and your PM UI in lockstep.
- **Job cost batch posting for change orders and expenses** — Post job cost batches to Sage's new-transaction file so approved change orders, committed costs, or reimbursables update project budgets without a controller re-keying them.
- **Master data sync for jobs, cost codes, and workforce** — Continuously mirror jobs, job cost cost codes, categories, extras, employees, departments, equipment, equipment cost codes, pays, unions, union locals, and union classes so dropdowns in your app always match Sage.
- **Multi-company connection management** — Enumerate all Sage 300 CRE companies behind a single customer connection and let users choose which company data flows into — supported natively through the companies and metadata endpoints.

## FAQs

### How does authentication work for Sage 300 Construction and Real Estate?

Truto handles the Sage 300 CRE auth token exchange for you. Your end user provides their Sage credentials in Truto's connect flow, and Truto manages token creation, storage, and refresh so your app only deals with a Truto connection ID.

### Is Sage 300 CRE a cloud API or on-premise?

Sage 300 CRE is traditionally on-premise or privately hosted. Integrations run against the customer's hosted instance, so data freshness and latency depend on their environment — Truto normalizes the connection details so you don't have to handle per-customer endpoint configuration.

### Can we create full daily field reports, not just read them?

Yes. You can create a field report shell and then append labor, material, equipment, subcontractor, visitor, weather/site condition, event, journal entry, extra, payroll time, and work activity records to it, then finalize the report and submit its payroll time.

### How do we push timesheets into Sage Payroll?

Use the timesheet create endpoint, which accepts extended COSA-format timesheets. The response includes validation nodes so your app can detect and surface processing errors (invalid cost codes, missing union classes, etc.) back to the user before payroll runs.

### Can we post transactions to Job Cost?

Yes. The job cost batch posting endpoint lets you push transactions into Sage's new-transaction file. You can also list existing job cost batches, categories, cost codes, and extras to validate coding before posting.

### What master data can we sync to pre-populate our app?

You can list companies, departments, employees, equipment, equipment cost codes, jobs, job cost categories, cost codes, extras, pays, unions, union locals, union classes, job contacts, files, and metadata classes — covering the master data needed for most field, payroll, and PM workflows.

### Does the integration support multiple Sage companies per customer?

Yes. The list companies endpoint returns every company available on the connection, so you can let the end user pick which company subsequent reads and writes target.
