POST Flow/Tickets/Update

Update information about Flow Tickets that are already Approved. For more information, see Flow Ticket status codes.

Requirements

  • Token scope:  Any valid scope, such as Agent, Certificate, or SSH:Approve

Headers

  • Content type: Content-Type:application/json.

  • Token: The bearer access token that you received. For example, Authorization:Bearer 4MyGeneratedBearerTknz==. For more information, see Passing a bearer token in your API calls.

Parameters

Input parameters

Name

Description

TicketId

Case sensitive. A Flow Ticket Id that is Pending review for approval or rejection. Carefully review and use an Id from POST Flow/Tickets/Enumerate.

TicketIDs

Case sensitive. An array of Flow Ticket Ids that are Pending review for approval or rejection. Carefully review and use Ids from POST Flow/Tickets/Enumerate.

useCount (Optional) Case sensitive. The maximum number of times the ticket may be used before a new ticket is required. Default is null to allow an unlimited number of times the ticket can be reused.
notBefore (Optional) Case sensitive. The earliest time the ticket may be approved. Specify the Coordinated Universal Time (UTC), for example YYYY-MM-DDTHH:MM:SS.mmm.
Expires (Optional) The maximum duration the ticket may be used before a new ticket is required.
Comment A comment that describes the change.

Returns

Response description

Name

Description

Error

The reason the HTTP 400 Bad Request occurred.

Result

The Result code of this API call. For more information, see Flow Ticket result codes. Appears only when the operation was unsuccessful.

Message

If the operation was successful, the string is empty. Otherwise, the reason why the operation failed is displayed, along with a Result.

Example: Delay the ability to join a team

Request

POST https://tpp.venafi.example/vedsdk/Flow/Tickets/Update
Authorization:Bearer 4MyGeneratedBearerTknz=={
   "TicketIDs":[
      3,
      4
   ],
   "notBefore":"2020-07-03 19:15:16.620"
}

Response

HTTP/1.1 200 OK
{
   "Message": ""
}