Back to all

202 jid response when job is in progress or expired.

When retrieving a full form by ID (https://developers.fieldwire.com/reference/get_full_form_by_id) it is unclear when the Job ID expires.

For example, we send a GET request to
https://client-api.{region}.fieldwire.com/api/v3/projects/{project_id}/forms/{id}/full

This returns a 202 Accepted response with a jid in the body.

We then poll the endpoint using that jid
https://client-api.{region}.fieldwire.com/api/v3/projects/{project_id}/forms/{id}/full?jid={jid}

  • If the full form is still being generated, the API again returns a 202 with the same jid.
  • Once the form is ready, the API returns a 200 OK response with the full form data.

If polling continues for too long, the job eventually expires. When this happens, the response again returns a 202 with a jid, identical to the "still processing" response. This makes it unclear when the job is still being processed or it has expired, which can lead to endless polling.

It would be helpful if the API returned a distinct response when the jid has expired so clients can handle this case appropriately.