Create a gig contract

​

Body·

required
application/json

Fields accepted when creating a gig contract. Unknown or read-only fields are rejected.

  • References gigs.id.

  • The signed PDF. References attachments.id.

  • Text printed below the total.

  • Text printed above the lines: the performance clause, a travel-included sentence.

  • The first agreement, or a change to it.

  • E.g. "Performance Agreement", "Addendum 1".

  • The band’s contract number as printed, e.g. "260502-IE1", "260502-IE1|A1". Unique.

  • When the client signed, from the PDF.

Responses

  • application/json
  • application/json
  • application/json
  • application/json
  • application/json
Request Example for post/gig-contracts
curl https://api.weddingoperatingsystems.com/api/v1/gig-contracts \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "label": null,
  "gig_id": null,
  "kind": "contract",
  "number": null,
  "header": null,
  "footer": null,
  "signed_at": null,
  "attachment_id": null
}'
{
  "data": {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "label": null,
    "gig_id": null,
    "kind": "contract",
    "number": null,
    "header": null,
    "footer": null,
    "signed_at": null,
    "attachment_id": null,
    "created_time": "2026-10-08T19:05:34.874Z",
    "last_edited_time": "2026-10-08T19:05:34.874Z",
    "amount_total": 1
  }
}