BigChange
BigChange is an all-in-one field service and job management platform (CRM, job scheduling, live tracking, a mobile workforce app, job finance, and business intelligence) known as JobWatch. Its modern REST API - the BigChange DX API at https://api.bigchange.com - lets developers manage jobs, contacts and persons, quotes, invoices and purchase orders, stock, resources, users and vehicles, worksheets, and assets, plus subscribe to webhooks. Requests are authenticated with a Bearer JWT access token (obtained through BigChange's authentication proxy from a developer-portal API key) and scoped with a required Customer-Id header.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles BigChange the way a machine reads it — 18 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — BigChange scores 37.8/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile BigChange
Each block below is one kind of artifact we hold for BigChange. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BigChange Assets API
The Assets API from BigChange — 1 operation(s) for assets.
BigChange Contacts API
The Contacts API from BigChange — 2 operation(s) for contacts.
BigChange Finance API
The Finance API from BigChange — 3 operation(s) for finance.
BigChange Jobs API
The Jobs API from BigChange — 5 operation(s) for jobs.
BigChange Persons API
The Persons API from BigChange — 1 operation(s) for persons.
BigChange Reference Data API
The Reference Data API from BigChange — 1 operation(s) for reference data.
BigChange Resources API
The Resources API from BigChange — 1 operation(s) for resources.
BigChange Stock API
The Stock API from BigChange — 1 operation(s) for stock.
BigChange Users API
The Users API from BigChange — 1 operation(s) for users.
BigChange Vehicles API
The Vehicles API from BigChange — 1 operation(s) for vehicles.
BigChange Webhooks API
The Webhooks API from BigChange — 2 operation(s) for webhooks.
Scroll within the panel for all 11 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
BigChange DX REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bigchange Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bigchange Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for BigChange — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/bigchange · machine-readable index on apis.io