Skip to main content
PATCH
Renames an approval on a ticket.

Authorizations

X-API-Key
string
header
required

Your Gorelo API key. See Generate API key. If your data is hosted in Australia, click the base URL at the top of this page and select https://api.aue.gorelo.io.

Path Parameters

ticketId
string<uuid>
required

Ticket identifier.

approvalId
string<uuid>
required

Approval identifier, from the conversations endpoint.

Body

The new name.

Renames an approval on a ticket. The name is the only part of an approval that can change after it is created; its approvers answer through their own links.

Name
string
required

The approval's new label. Cannot be cleared. Sending the name it already has changes nothing.

Minimum string length: 1

Response

OK

StatusCode
enum<integer>
Available options:
100,
101,
102,
103,
200,
201,
202,
203,
204,
205,
206,
207,
208,
226,
300,
301,
302,
303,
304,
305,
306,
307,
308,
400,
401,
402,
403,
404,
405,
406,
407,
408,
409,
410,
411,
412,
413,
414,
415,
416,
417,
421,
422,
423,
424,
426,
428,
429,
431,
451,
500,
501,
502,
503,
504,
505,
506,
507,
508,
510,
511
IsSuccess
boolean
Data
object

Full details of one approval on a ticket — this is where approval status lives, the conversations list being deliberately lean. Attachments belong to the approval's comments rather than to the approval itself, so there is no attachments field here. Timestamps are UTC.

DataContext
object | null
Example:

null

Notifications
object[]