autopilot

Mark F24 Paid

Confirm one F24 as paid, and answer with the record as it now stands.

One 404 for "no such id" and "somebody else's id" alike — the store already refuses to tell them apart, and a distinct 403 would turn this route into an oracle for which record ids exist.

Idempotent: the store's update carries WHERE status = 'proposed', so a double tap on a flaky mobile connection keeps the first paid_at and still answers 200 with the paid record. The client is reporting what the user did, not asking us to transition a state machine.

post/api/autopilot/f24/{record_id}/mark-paid

Request

  • Base URL: https://api.taxcompass.it (the document declares no server; this is the origin it was published from)
  • URL: https://api.taxcompass.it/api/autopilot/f24/{record_id}/mark-paid
  • Auth: HTTP bearer

Path parameters

record_idstring uuid required

Response

Successful Response

idstring uuid required
tax_yearinteger required
kindstring required
status'proposed' | 'confirmed_paid'
totalstring
due_yearinteger nullable
due_monthinteger nullable
due_dayinteger nullable
due_datestring date nullable
paid_atstring date-time nullable
created_atstring date-time nullable
updated_atstring date-time nullable

Changes

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