The API Report CardAPI Index
THE API REPORT CARD / Construction / Foundation Software
Foundation Software

Foundation Software API

Construction Accounting & Payroll · foundationsoft.com

A narrow REST surface exists, documented in a public Postman workspace covering an AP API for pushing invoices and payments. OAuth2 access works only after Foundation provisions four customer-specific values, and webhooks are unsupported, so integrators poll.

Last verified: July 2026Construction
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceFAILNo developer portal; public documentation is a Postman workspace covering an AP API v1, with the rest of the surface unpublished.
AccessFAILNo self-serve onboarding; access runs through sales, and Foundation must provision customer-specific credentials before anything works.
CoveragePOORPublic Postman docs cover accounts payable only; GL, payroll, job cost, and project management surfaces are not publicly visible.
AuthFAILOAuth2 client credentials only work after Foundation issues four values: Identity API URL, client ID, CAS GUID, and subscription key.
Docs & DXFAILDocs live in a Postman workspace, not a portal; no sandbox, no SDKs, and webhooks are not supported, so integrators poll.
StabilityMIXED
MORE FROM THE REPORT CARD
Sage Intacct ConstructionD+CMiCFBuildertrendFAccuLynxD+
Supergood: Foundation Software isn't going to ship an API, so we did: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Foundation Software scores F on the API Report Card. A narrow REST surface exists, documented in a public Postman workspace covering an AP API for pushing invoices and payments. OAuth2 access works only after Foundation provisions four customer-specific values, and webhooks are unsupported, so integrators poll.

Tried to integrate with Foundation Software?
SOURCES
No public developer portal, documentation lives in a Postman workspace and partner connector docs; engineers cannot fully scope the API surface before becoming a customer postman.com ↗
API access requires Foundation to provision four customer-specific values (Identity API URL, CRM Client ID, CAS Connection GUID, Subscription Key) before any OAuth2 client credentials work, no self-serve onboarding docs.pandium.com ↗
Webhooks are not supported per the Pandium connector profile, forcing integrators to poll for changes to AP, payroll, and job-cost data docs.pandium.com ↗
API tracker profile (apitracker.io) shows nearly every developer-resource field empty (no public docs, reference, sandbox, code samples), reflecting genuinely thin public-facing developer surface area apitracker.io ↗
Documented endpoints (Foundation AP API v1 on Postman) are narrowly scoped to AP, GL, job costing, payroll, certified payroll, and project management coverage is not publicly visible and customers report needing custom services work to extract them postman.com ↗
Customers note that even getting Power-BI-style reporting against their own data requires Foundation services hours to customize extracts, indicating the read API isn't truly self-serve capterra.com ↗
Even the partner-built connectors (Pandium) require 8 distinct secrets/credentials to provision, signaling a multi-layered, hand-configured access model rather than a developer-friendly OAuth flow docs.pandium.com ↗
HQ-suite modules (WorkMax, ProjectHQ, SafetyHQ) are advertised as integrated via 'a secure API' but customers report sync glitches and occasional dual-entry, suggesting the internal API contract is not bulletproof capterra.com ↗
Users repeatedly describe the UI as dated, 'looks and feels like a 40 year old program,' lots of drilling, and basic tasks require multiple screens capterra.com ↗
Reports are 'super limited,' data is flat, and any meaningful custom report requires Foundation services hours, self-serve BI is weak capterra.com ↗
Persistent software glitches, frequent crashes, and connectivity/timeout issues when users aren't constantly active in the app capterra.com ↗
HQ-branded add-on modules (WorkMax, ProjectHQ, SafetyHQ) sync to core FOUNDATION but are described as glitchy, with some workflows requiring dual entry capterra.com ↗
Payroll processing involves many sequential steps and is time-consuming, even though the underlying construction payroll engine is powerful capterra.com ↗
Poor multi-currency / international support, Canadian vendors and multi-currency projects are a weak spot softwarefinder.com ↗
Support is knowledgeable but callback queues can stretch into the next day, painful during payroll or billing cycles capterra.com ↗
Steep learning curve, 'powerful but hard to learn,' and effective use depends heavily on Foundation's paid training and consulting hours softwareadvice.com ↗
Implementation runs roughly $3K–$8K on top of subscription ($500–$1,500+/mo per module), with mid-market deployments commonly $5K–$10K and larger ones $20K–$50K itqlick.com ↗
© Supergood Systems, Inc.