Viewpoint Spectrum API Guide for Contractors

One-line verdict: A real two-way API lives inside Spectrum — as a licensed module your admin switches on, service by service. Openness: 3 / 5 — rated 3 because Trimble documents genuine Get/Put web services across Spectrum’s ERP data, capped by the licensed Data Exchange module, per-service admin authorization, and the absence of events or bridges.

The connection that works

Rung 1 — Direct connection, through the Data Exchange module. Trimble’s developer index names it exactly as your admin will meet it: “Viewpoint Spectrum — Data Exchange Web Services API for ERP data transfer.” The services come in two shapes — SOAP/WSDL services, and RESTful/JSON services (which require Java 11 in the Data Exchange setup, per Trimble’s own help). Trimble defines the model in one clean sentence pair: a “Get” web service returns data you define by parameters; a “Put” web service adds or updates information in Spectrum. Calls run against your own Spectrum server.

The gate is administrative and specific: before any service answers, a Spectrum admin creates an Authorization ID in the Data Exchange installation screen, scoped to specific companies and specific web services, and Get services run under an operator’s job-based security. Trimble’s App Xchange setup help confirms the same precondition from the other side: “The Data Exchange module must be active in your Spectrum instance.”

Verified from Trimble’s own List of Web Services: Accounts Payable — Add Vendor, Update Vendor, Get Vendors, vendor notes, Add Vendor Invoices, Add Subcontract; Accounts Receivable — Add Customer, Get Customers, bill-to and ship-to services, Add Cash Receipts; with Job Cost, Project Management, Purchase Order, and Work Order service families listed by module in the same index. One endpoint is documented to the ground: Vendor Invoice Multi-Line, a JSON POST that adds unposted invoice header and detail lines — with its limits printed beside it (no PO invoice receiving, no subcontract progress billings or back charges, no image updates). That is what real documentation looks like.

Not the API: Trimble’s App Xchange is a separate, separately licensed integration platform (built from the former Ryvit). Trimble states plainly that its connector documentation “represents an Open API representation of internal App Xchange functionality, and is not an API accessible to customers.” App Xchange is a connector platform you buy — it is not a public API you call, and this page does not count it as one.

Events and bridges: no webhooks or event subscriptions are documented in the Data Exchange sources — integrations call the services; nothing calls you. No Zapier or Make app was found.

Can automate

• Vendor and AP flow — vendors can be added and updated, vendor invoices posted in (multi-line, unposted), and subcontract records added, without re-keying into Spectrum.
• Customer and cash-receipt flow — customers added and read, cash receipts posted — the AR side is workable through the documented services.
• ERP data pulls — Get services across AP, AR, job cost, and work order modules feed reporting and the tools your office runs beside Spectrum.
• Per-company, per-service control — Authorization IDs scoped by company and service mean a connection gets exactly the doors it needs, and no more.

Can’t automate

• Anything with Data Exchange unlicensed — if the module isn’t on your licence, there is no API, full stop. This is the first question, not the last.
• Event-driven automation — no webhooks are documented; nothing in Spectrum announces a change. Connections poll or run on schedule.
• Rate-limit planning — UNVERIFIED. No rate limit is documented in the sources reviewed. (Some Get services have an admin-set maximum-records value — Trimble’s troubleshooting mentions setting “Max # of records” to 20,000 — that’s a per-service record cap, not a rate limit, and we won’t publish it as one.)
• App Xchange as your API — Trimble itself says the connector API is not customer-accessible; budget it as a paid platform, not a developer door.
• Zapier or Make recipes — no app exists on either bridge.

Hidden gate: Spectrum’s API is a licensed module your admin has to turn on and authorize service-by-service — if Data Exchange isn’t on your licence, there is no API. Confirm the module and the Authorization ID before anyone scopes an integration.

Build fit — what this platform supports well

• AP automation — the strongest fit: vendor invoices and vendor records are documented, writable, and specific.
• Back-office sync — customers, cash receipts, and job-cost data move in both directions through Get/Put services.
• Speed-to-Lead / Estimate Follow-Up — not what this API is for: Spectrum is the ERP of record, and no lead or estimate event surface is documented. Front-office automation lives in your CRM; Spectrum receives the results.
• Review Engine — like every platform here, Viewpoint Spectrum has no verified reviews API, so the review ask runs on our system triggered by a job-completion signal.

What this means for your shop

If Spectrum is your ERP of record, you own more API than most Spectrum shops realize — it’s just wearing a licence and an admin setup. Established contractors with an IT-minded controller can move vendor, customer, and invoice data without re-typing. Everyone else’s first step is a licence question to Trimble, not a build quote: is Data Exchange active on our instance?