Fieldwire
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Fieldwire the way a machine reads it — 97 machine-readable artifacts across 6 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 — Fieldwire scores 57.3/100 (strong), with a separate agent-readiness read of 21/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Fieldwire's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fieldwire/"
title="Fieldwire on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fieldwire.svg"
alt="Fieldwire Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fieldwire/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fieldwire/"
title="Fieldwire on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fieldwire/card.svg"
alt="Fieldwire Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Fieldwire
Each block below is one kind of artifact we hold for Fieldwire. 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 18
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.
Fieldwire Actual Costs API
Actual cost entries logged against budget lines.
Fieldwire Authentication API
Refresh-token / JWT exchange and session management.
Fieldwire Budget Line Items API
Project budget line items tied to tier cost codes.
Fieldwire Building Information Models API
BIM and BIM versions attached to a project.
Fieldwire Change Orders API
Project change orders that adjust scope and budget.
Fieldwire Custom Stamps API
Account-level custom stamps used on markups across projects.
Fieldwire Floorplans API
Floorplan lifecycle, hierarchy, and collections.
Fieldwire Form Inputs API
Inputs (text, number, photo, signature, choice, etc.) inside a section.
Fieldwire Form Records API
Captured form responses per project.
Fieldwire Form Sections API
Section structure within a form template.
Fieldwire Form Templates API
Account-level form template lifecycle, duplication, and transfer.
Fieldwire Hyperlinks API
Single and multi-hyperlink jumps between sheets.
Fieldwire RFIs API
Requests for Information lifecycle.
Fieldwire Sheets API
Sheet upload and version management.
Fieldwire Spec Sections API
Specification sections used to organise submittals.
Fieldwire Submittals API
Submittal lifecycle, approvals, and types.
Fieldwire Subscriptions API
Webhook subscription lifecycle.
Fieldwire Users API
Account-level user, role, and permission management.
Scroll within the panel for all 18 ·
Postman Collections 29
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 29 ·
Open Collections 36
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).
API Collection
OPEN COLLECTIONFieldwire Account API
OPEN COLLECTIONFieldwire Account Actual Costs API
OPEN COLLECTIONFieldwire Account Actual Costs Attachments API
OPEN COLLECTIONFieldwire Account Actual Costs Authentication API
OPEN COLLECTIONFieldwire Account Actual Costs Bubbles API
OPEN COLLECTIONFieldwire Account Actual Costs Budget Line Items API
OPEN COLLECTIONFieldwire Account Actual Costs Change Orders API
OPEN COLLECTIONFieldwire Account Actual Costs Custom Stamps API
OPEN COLLECTIONFieldwire Project Financials API
OPEN COLLECTIONFieldwire Account Actual Costs Floorplans API
OPEN COLLECTIONFieldwire Account Actual Costs Form Inputs API
OPEN COLLECTIONFieldwire Account Actual Costs Form Records API
OPEN COLLECTIONFieldwire Account Actual Costs Form Sections API
OPEN COLLECTIONFieldwire Account Actual Costs Form Templates API
OPEN COLLECTIONFieldwire Forms API
OPEN COLLECTIONFieldwire Account Actual Costs Hyperlinks API
OPEN COLLECTIONFieldwire Account Actual Costs Markups API
OPEN COLLECTIONFieldwire Plans and Sheets API
OPEN COLLECTIONFieldwire Account Actual Costs Project Stats API
OPEN COLLECTIONFieldwire Account Actual Costs Project Teams API
OPEN COLLECTIONFieldwire Account Actual Costs Project Users API
OPEN COLLECTIONFieldwire Account Actual Costs Projects API
OPEN COLLECTIONFieldwire Account Actual Costs RFIs API
OPEN COLLECTIONFieldwire RFIs and Submittals API
OPEN COLLECTIONFieldwire Account Actual Costs S3 Tokens API
OPEN COLLECTIONFieldwire Account Actual Costs Sheets API
OPEN COLLECTIONFieldwire Account Actual Costs Spec Sections API
OPEN COLLECTIONFieldwire Account Actual Costs Submittals API
OPEN COLLECTIONFieldwire Account Actual Costs Subscriptions API
OPEN COLLECTIONFieldwire Account Actual Costs Task Check Items API
OPEN COLLECTIONFieldwire Account Actual Costs Task Relations API
OPEN COLLECTIONFieldwire Account Actual Costs Tasks API
OPEN COLLECTIONFieldwire Account Actual Costs Users API
OPEN COLLECTIONFieldwire Webhooks API
OPEN COLLECTIONScroll within the panel for all 36 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Fieldwire GraphQL Schema
This document describes a conceptual GraphQL schema for the Fieldwire construction management API. Fieldwire provides a REST API (https://developers.fieldwire.com/) covering pro...
GRAPHQLPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
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.
Fieldwire 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.
Fieldwire Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Fieldwire Webhooks
Outbound webhook events delivered by Fieldwire to subscriber `post_url` endpoints. Subscribers register through the Webhooks REST API; Fieldwire POSTs JSON payloads describing e...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Fieldwire Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Fieldwire Task
JSON SCHEMAExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security 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 Fieldwire — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 8
Reference material describing how the API behaves
Scroll within the panel for all 8 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 6
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fieldwire · machine-readable index on apis.io
This is an independent, third-party profile of Fieldwire, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.