Fertiliser records

Update Fertiliser Record

Change what a fertiliser carries after the fact: any of the attributes below, and products, which REPLACES the whole product set (position is the array index, at most 10). An attribute that is not sent is left alone. Answers with the task, exactly as GET /tasks/{id} would, with its fertiliser. Needs a grant that allows editing the task. Never invent a batch, expiry, rate or withholding period. The id is the fertiliser.id of the task, not the task's id. Photos. A file on disk: call createImageUpload, run the returned curl_example from the shell, then pass image_upload_ids. Never base64-encode a local photo into a tool call. A public http(s) URL: pass image_urls. Only a tiny generated image (under about 100 KB decoded) uses image_base64s. One upload can be attached to several records until it expires. On update, image_mode defaults to append (add to the existing photos); replace swaps them all out; remove_image_ids deletes specific ones. If any image fails, the whole create or update is rolled back. The attaching call still needs confirm: true. createImageUpload and its PUT do not.

put/fertiliser-records/{id}

Request

  • Base URL: https://api.purplegrain.com/api/v1
  • URL: https://api.purplegrain.com/api/v1/fertiliser-records/{id}
  • Auth: HTTP bearer

Path parameters

idstring required

The fertiliser record's id (fertiliser.id on the task).

Request body

Example request

{
  "data": {
    "date": "2026-09-28"
  }
}

Response

The task, with its fertiliser.

Example response

{
  "data": {
    "type": "task"
  }
}

Changes

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