# Docs

> Installing Fieldstub, and how Procore change events, budget codes and T&M tickets actually behave, verified against a live sandbox. Plus the API and MCP server.

Source: https://fieldstub.com/docs/  ·  18 pages  ·  Updated 2026-09-18

Written while building Fieldstub and verified by probing a real Procore sandbox, not read off a documentation page. Several of the findings here are not published anywhere else.

Every page is also available as markdown: add `.md` to the URL, or send `Accept: text/markdown`.

## Setting it up

For the Procore admin doing the install.

- [Installing Fieldstub in Procore](https://fieldstub.com/docs/install.md): How to install Fieldstub in a Procore company, who can sign in, what it reads and writes, and how to remove it. Requires Project Financials.
- [How the integration works](https://fieldstub.com/docs/architecture.md): The integration workflow: what Fieldstub reads from Procore, what it writes, and the human approval that sits between a field ticket and a Change Event.

## How Procore actually behaves

The API as it is, including the places it tells you something untrue.

- [Procore budget codes, and why your change event line item lands blank](https://fieldstub.com/docs/procore-budget-codes.md): A Procore change event line item needs a WBS code id. The segment_items form returns 200 and is silently discarded, filing every line under a blank code.
- [Every Procore budget code error on a change event line item](https://fieldstub.com/docs/procore-budget-code-errors.md): Wbs Code not found, budget_code is missing, must be an integer. Every response Procore gives a change event line item, including two that return 200 and file blank.
- [Creating a Procore change event over the API](https://fieldstub.com/docs/procore-change-events-api.md): Auth, the create body Procore actually accepts, line items, amounts as strings, attachments, idempotency and rate limits. Probed against a live sandbox.
- [Procore's T&M Tickets tool: what it does, and what it needs](https://fieldstub.com/docs/procore-tm-tickets.md): Procore ships a T&M Tickets tool for labor, equipment, materials and signatures. It needs a Procore seat and the mobile app, and it has no public REST API.

## Build on Fieldstub

The REST API and the MCP server.

- [The Fieldstub API](https://fieldstub.com/docs/api.md): Create extra work tickets, read where each line will land, and file them into Procore as change events. REST, API keys, and an OpenAPI spec.
- [The Fieldstub MCP server](https://fieldstub.com/docs/mcp.md): Connect an AI assistant to Fieldstub over MCP. Ten tools for capturing extra work and filing it into Procore, with approval deliberately fenced off.