The API Report CardAPI Index
BigChange

BigChange API

bigchange.com

A documented REST API, BigChange DX, lives at developers.bigchange.com with a free plan and permission-scoped API keys. Auth is long-lived keys only, no OAuth; the full reference and webhook catalog sit behind portal login, and legacy SOAP services linger on a separate domain.

Last verified: July 2026Field Service
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistenceGOODBigChange DX is a documented REST API at developers.bigchange.com with a free tier; a legacy SOAP surface coexists.
AccessGOODThe DX API has a free plan and self-generated, permission-scoped keys; the full reference sits behind a portal login.
CoveragePOOR
AuthPOORLong-lived API keys only, no OAuth flow; keys do carry fine-grained per-endpoint permission scoping.
Docs & DXPOORThe full API reference and webhook catalog sit behind the portal login; legacy SOAP docs live on a separate domain.
StabilityMIXEDLegacy SOAP and REST web services co-exist with the newer DX API, leaving ambiguity over which surface is long-lived.
Supergood: BigChange has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

BigChange scores D on the API Report Card. A documented REST API, BigChange DX, lives at developers.bigchange.com with a free plan and permission-scoped API keys. Auth is long-lived keys only, no OAuth; the full reference and webhook catalog sit behind portal login, and legacy SOAP services linger on a separate domain.

Tried to integrate with BigChange?
SOURCES
API authentication is long-lived API keys only, no OAuth flow documented, complicating third-party app distribution and per-user permissioning developers.bigchange.com β†—
Full API reference and event/webhook catalogue gated behind developer-portal access rather than fully public docs, slowing pre-sales integration scoping developers.bigchange.com β†—
Legacy SOAP/REST web services co-exist with the newer DX REST API at separate domains, creating ambiguity about which surface to build against for long-lived integrations documentation.ops.bigchange.com β†—
Heavy reliance on partner-built connectors (Cyclr, Power Automate, telephony partners) to plug gaps where native integrations are missing, rather than first-party expansion docs.cyclr.com β†—
Practical data-portability friction reinforced by long contracts and reported difficulty getting data out at end-of-contract, limits real-world value of the API as an escape hatch for departing customers trustpilot.com β†—
Long lock-in contracts, multiple customers report 3- to 5-year terms with auto-renewal and unclear cancellation clauses that were not flagged clearly during the sales process trustpilot.com β†—
Unexpected price increases mid-contract with limited recourse, and 'coercive selling' allegations from former customers attempting to leave trustpilot.com β†—
Continued direct-debit charging after notice of cancellation; disputes around hidden T&Cs around contract length and extra charges trustpilot.com β†—
Dated/clunky UI relative to newer FSM competitors; learning curve cited as steep for non-technical office staff and field engineers g2.com β†—
Customer feedback frequently 'brushed off' with claims that platform improvements would take too long or are not possible trustpilot.com β†—
Post-sale support quality drops once contract is signed and direct debits are set up; gap between sales promises and delivered functionality trustpilot.com β†—