contractors

Waive Strike

Clear a strike the contractor could not have avoided.

Frederick, 2026-09-17: if somebody cannot clock in because of OUR equipment or systems -- a device not registered, a network not configured, intake refused for a missing tub count -- no strike stands.

⛔THE ROW IS KEPT, NEVER DELETED. It is the only evidence the failure was ours rather than theirs, and the party it protects is the contractor. See service.waive_strike and migration 0498.

The reason is required and is refused blank by the service AND by the database's own CHECK -- a waiver with no stated cause is a strike that vanished, which is the thing keeping the row was meant to prevent.

post/api/contractors/strikes/{strike_id}/waive

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/contractors/strikes/{strike_id}/waive
  • Auth: none declared

Path parameters

strike_idstring uuid required

Request body

object required

Response

Successful Response

object required

Changes

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