canonical: https://jentic.com/apis/fieldstub.com/fieldstub

# Fieldstub API

The Fieldstub API captures out-of-scope construction work as tickets and, when a ticket is approved, writes it into Procore as a Change Event with typed line items on real budget codes. Creating a ticket is a safe record of a claim, while approving writes money into a customer's financials and is not reversible, so approval is a deliberate step a reviewer owns. Each ticket carries a routing breakdown showing where every line of money will land, and capture links let field crews without a Procore seat submit work by QR code. Projects, cost codes, budget codes, and photo attachments round out the flow from the jobsite to the change event.

## For AI agents

Create and review construction extra-work tickets, inspect how each line routes to a Procore budget code, and approve a ticket to write it into Procore as a Change Event. Manage projects, cost codes, capture links, and photos.

## Scope

Does not handle full project management, scheduling, or accounting ledgers. Use for capturing construction extra work and filing it into Procore as a Change Event only.

## Capabilities

- Create a ticket for out-of-scope construction work with labor, equipment, and material line items
- List and read tickets, including the routing that shows where each line of money will land
- Approve a ticket to write a Change Event into Procore, or reject and later restore it
- Search a project's cost codes and create a budget code a line needs
- Mint a shareable capture link as a QR code so field crews without a Procore seat can submit work
- Attach photos to a ticket before it is written to Procore

## Use cases

### Agent-assisted change-event review through Jentic

An AI agent reviews submitted tickets, reading each one's routing to see which lines landed on a real budget code and which are flagged for review. It can gather the project's cost codes, create a missing budget code, and set per-line routing, then hand a clean ticket to a reviewer for the irreversible approval that writes the Change Event into Procore.

Example prompt: List submitted tickets for a project, read the routing on the newest one, and create a budget code for any line flagged as needing review

### Field capture without a Procore seat

Subcontractors and field crews who have no Procore login still need to log extra work. Fieldstub mints a capture link that can be printed as a QR code and taped in the gang box, so a worker submits a ticket with photos from their phone, and the office later attaches more photos before the ticket is approved.

Example prompt: Create a capture link for a project, then attach two photos to the ticket it produced

### Routing extra work to the right budget code

Procore accepts a line item with a blank budget code without warning, which is how costs go missing. Fieldstub's routing shows each line's budget code and whether it needs review, and the API can create the WBS code the project does not have yet, so an integration can route unplanned work to a real code before anything is written.

Example prompt: Search a project's cost codes for a trade, create the matching budget code, and read the updated routing on a ticket

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/projects` | List Procore projects for this company |
| GET | `/projects/{project_id}/cost-codes` | Search the project cost codes |
| POST | `/projects/{project_id}/budget-codes` | Create a budget code the project lacks |
| GET | `/tickets` | List tickets |
| POST | `/tickets` | Create a ticket |
| GET | `/tickets/{id}` | Get a ticket, including where each line will land |
| POST | `/tickets/{id}/approve` | Approve and write a Change Event to Procore |
| POST | `/tickets/{id}/reject` | Reject a ticket |

## Key resources

- **Tickets** — Create, list, read, approve, reject, and restore extra-work tickets and attach photos
- **Projects** — List Procore projects, search cost codes, and create budget codes
- **Capture links** — Create and revoke shareable links that field crews use without a Procore seat

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 77 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/fieldstub.com/fieldstub/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Fieldstub API by hand means handling its Bearer key, checking a project's Change Events capability before you write, and respecting the routing and approval guards yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so it can create tickets, read them, and inspect routing while the approve operation that writes money into Procore stays out unless you add it. Approving is irreversible from here, so leaving it off keeps a person on that decision.
- **Credential handling:** Your Fieldstub token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a construction ticket' or 'read a ticket's routing', and Jentic returns the matching Fieldstub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Procore** — Procore is the construction management platform Fieldstub writes Change Events into.
- **Agave** — Agave offers a unified API across construction systems that can sit alongside Fieldstub's Procore-specific capture.
- **Dalux Field** — Dalux Field captures jobsite data and issues, an alternative approach to field capture from Fieldstub.

## FAQ

### What authentication does the Fieldstub API use?

It uses a Bearer token, an API key issued from the review queue, sent in the Authorization header as described in its OpenAPI spec. Every operation runs against the company that key belongs to, which the account check endpoint will confirm.

### Can I see where a ticket's costs will land before approving with the Fieldstub API?

Yes. Reading a ticket returns a routing breakdown with each line's amount, its budget code, whether it was routed exactly or matched loosely, and whether it needs review. That is the field to check before approval, because approving writes a Change Event into Procore and is not reversible from the API.

### What are the rate limits for the Fieldstub API?

The OpenAPI spec does not state a request rate limit. Check the Fieldstub documentation for current limits, and note that ticket list reads accept a limit of up to 200 per page to keep large pulls efficient.

### Is there a Fieldstub MCP server?

Yes, Fieldstub offers an MCP server for AI tools. You can also connect Fieldstub directly through Jentic: your agent gets the full 15-endpoint surface without loading another server's tool definitions into its context, your token is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

### Can I limit what my agent is allowed to do with the Fieldstub API?

Yes. Write a rule that allows ticket creation, the ticket and routing reads, and photo attach, but not the approve operation that writes money into Procore, so your agent prepares and inspects a ticket while a person owns the irreversible write. Every call it makes is recorded in your Jentic One audit log.

### How do I prepare a change-event ticket with the Fieldstub API through Jentic?

Search Jentic for 'create a construction ticket', add the Fieldstub API from the directory, and store your token once; your agent then creates the ticket, reads its routing, and resolves budget codes before a reviewer approves it. To run it on your own infrastructure, install Jentic One from its GitHub repo.