Contractor portal

hours.correction.request

Report a mistake in one of your approved time entries (hoursId, its expectedRevision, the corrected date, minutes and description, and a reason). The approved entry stays as it is and is held out of payouts until finance decides. Hours that were already paid are raised with finance as an adjustment instead. One correction can be open per entry.

POST/api/v1/contractor/hours.correction.request

Permissions

contractor:readcontractor:write

Who can call it

contractor

Retries

Idempotency key required, with expectedRevision

MCP

contractor_hours_correction_request

Fields

  • hoursIdstring (ID)Required

    The ID of the related record.

  • expectedRevisionintegerRequired

    The record's current revision, from the last time you read it. If someone changed the record since, the request is refused with a conflict so you can reload and check before trying again.

    at most 9007199254740991 · greater than 0

  • idempotencyKeystringRequired

    Any unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match.

    8–150 characters

  • datestring (date)Required

    A date, as YYYY-MM-DD.

  • minutesintegerRequired

    1 to 1440

  • descriptionstringRequired

    A short description.

    1–2000 characters

  • valuesmap
  • reasonstringRequired

    A short note saying why, kept in the record's history.

    3–1000 characters

  • confirmDuplicateboolean

Example

curl https://app.getoatmilk.com/api/v1/contractor/hours.correction.request \
  -H "Authorization: Bearer $OATMILK_OAUTH_TOKEN" \
  -H "X-Accounting-Organization: $OATMILK_ORGANIZATION_ID" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "hoursId": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "expectedRevision": 3,
  "date": "2026-09-01",
  "minutes": 90,
  "description": "Synthetic example from the docs",
  "reason": "Synthetic example from the docs"
}'
Response
{
  "data": { … }
}

Try it

Try it

Checks your input with this action’s real schema and answers like the API, with synthetic data. No key needed, and nothing changes.

POST/api/v1/contractor/hours.correction.request
curl https://app.getoatmilk.com/api/v1/contractor/hours.correction.request \
  -H "Authorization: Bearer $OATMILK_OAUTH_TOKEN" \
  -H "X-Accounting-Organization: $OATMILK_ORGANIZATION_ID" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "hoursId": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "expectedRevision": 3,
  "date": "2026-09-01",
  "minutes": 90,
  "description": "Synthetic example from the docs",
  "reason": "Synthetic example from the docs"
}'

More in Contractor portal.