DocsSign in
  • APIs
  • Generators
  • Stacks
  • Projects
  • Docs
  • History
  • Schema
  • Generate
Links3
  • get/linksList capture links
  • post/linksCreate a capture link
  • post/links/{token}/revokeRevoke a capture link
Projects5
  • get/meWhich company this key belongs to
  • get/projectsList Procore projects for this company
  • get/projects/{project_id}/cost-codesSearch the project cost codes
  • post/projects/{project_id}/budget-codesCreate a budget code the project does not have yet
  • get/projects/{project_id}/capabilityWhere a ticket on this project can be filed
Tickets7
  • get/ticketsList tickets
  • post/ticketsCreate a ticket
  • get/tickets/{id}Get one ticket, including where each line will land
  • post/tickets/{id}/approveApprove, and write a Change Event to Procore
  • post/tickets/{id}/rejectReject a ticket
  • post/tickets/{id}/restoreSend a rejected ticket back to Needs review
  • post/tickets/{id}/photosAttach photos to a ticket that is not yet in Procore
    FI

    Fieldstub API

    Construction: capture out-of-scope work tickets and approve them into Procore change events

    15 operations·8 schemas·1 revision

    Changes

    Full history

    Source

    View schema
    Spec
    OpenAPI 3.1.0
    Document
    app.fieldstub.com · JSON, 36 KB
    Retrieved
    Oct 19, 2026, 17:23 UTC
    Digest
    f0365e1796fe

    For agents

    Every page here has a markdown twin. The overview is one fetch; the llms.txt lists every operation with a link to its own markdown.

    curl https://skmtc.dev/fieldstub/apis/fieldstub-api.md
    curl https://skmtc.dev/fieldstub/apis/fieldstub-api/llms.txt