Tickets

Create a ticket

The same validation the capture form uses. A ticket created here is exactly as trusted as one submitted from a jobsite, which is to say not at all until someone approves it.

post/tickets

Request

  • Base URL: https://app.fieldstub.com/v1
  • URL: https://app.fieldstub.com/v1/tickets
  • Auth: HTTP bearer

Request body

project_idstring required
descriptionstring required

What was done.

reasonstring required

Why it is out of scope.

directed_bystring required

Who authorized it.

captured_bystring

Response

OK

idstring uuid
status'submitted' | 'written' | 'rejected'
project_idstring
descriptionstring
reasonstring

Why the work is out of scope.

directed_bystring

Who on the GC side authorized it.

captured_atstring date-time
captured_viastring

qr, sms, link or api.

captured_bystring nullable
totalnumber
signatureobject nullable
photo_countinteger
link_tokenstring nullable
approved_bystring nullable

Who released the ticket into Procore: a reviewer's email address, or "key:<name> (<prefix>)" when an API key or an agent approved it. Null when the approval predates this field or no actor could be established. Procore's own audit shows the service account that wrote the change event, so this is the only record of the person.

approved_atstring date-time nullable
warningsstring[]

Changes

No recorded changes to this operation across all 1 revision of this API.