The API documentation for the Incident API PATCH operation (labeled as "Update An Incident") does not list any way to provide an update message when updating an incident: the only related field is `body`, which is described as "The initial message, created as the first incident update. There is a maximum limit of 25000 characters." I don't want to replace the initial message; I want to provide an update message.
The body is not replacing the initial message in the incident, the body in the update incident will set the first incident update message, and then if you need to add more updated you will use Incident Updates to do that.
it appears that the "Incident Updates" APIs are to _modify a previous Incident Update_, not to add updates to an incident.
My question might have been ambiguous (I'll edit it to be less so): I am referring to using PATCH against an incident itself, within the Incidents API; I am not talking about the "Incident Updates" API.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So there are two ways to create the initial update of an incident, either via Patch or Put. But the payload is the same for both. And if you look at the description of the body that is for the initial incident update. This is the important part:
The initial message, created as the first incident update.
After you have created the initial update you will use the Incident Updates (PATCH) to add new updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My point is, then, that the API documentation is incorrect. (a) The initial update is created when you create the incident (using POST). (b) I am looking at the PATCH API documentation and it has the verbage I put in the description, which you repeated, which is apparently not correct if that's the same field you use to provide an update message for each subsequent update.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, so you can set the initial update in two (or three if you count PATCH and PUT) via the API. You can do it either via Create an incident, or via the Update incident. The body is not a required field so you just have to pick which option you like better. Then when you add a new update you will use Incident Updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please explain what you mean by "use Incident Updates"?
The API calls listed under the "Incident Updates" section of the API documentation explicitly say they are to Update a previous incident update -- not to add an update to an incident -- and they require the ID of an already-existing incident update to modify.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.