How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Venafi Legacy Workflow APIs API

The Workflow/Ticket interface manages certificates in an automated workflow. Trust Protection Foundation engines rely upon workflow object settings and their assignment to folders for the creation of workflow tickets and their impact on the objects to which they apply.The methods provided in this section allow for workflow tickets to be generated, updated, and removed independent of Trust Protection Foundation processing, making them applicable to external use cases that involve Trust Protection Foundation objects. A workflow can now apply to certificate renewal and provisioning to Windows or SSH devices.

Venafi Legacy Workflow APIs API is one of 58 APIs that Venafi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Legacy Workflow APIs. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 7 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 26.1.1.

Requests are made against 3 base URLs: /, https://REPLACEdnsnameME/, https://{dnsname}/.

7 operations 7 paths 11 schemas 7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
26.1.1
Base URL
https://api.venafi.cloud
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Venafi Legacy Workflow APIs API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (AccessToken). By default, every request must be authenticated.

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 POST. Each is listed below with its method, path, parameters, and response codes.

Legacy Workflow APIs 7

The Workflow/Ticket interface manages certificates in an automated workflow.

POST
/vedsdk/workflow/ticket/create
Create a workflow ticket
Venafi_Core_WebSDK_WorkflowTicketRest_TicketCreate body → 200400401500
POST
/vedsdk/workflow/ticket/delete
Remove a workflow ticket
Venafi_Core_WebSDK_WorkflowTicketRest_TicketDelete body → 200400401500
POST
/vedsdk/workflow/ticket/details
Get workflow ticket details
Venafi_Core_WebSDK_WorkflowTicketRest_TicketDetails body → 200400401500
POST
/vedsdk/workflow/ticket/enumerate
Enumerate workflow tickets
Venafi_Core_WebSDK_WorkflowTicketRest_TicketEnumerate body → 200400401500
POST
/vedsdk/workflow/ticket/exists
Verify workflow ticket exists
Venafi_Core_WebSDK_WorkflowTicketRest_TicketExists body → 200400401500
POST
/vedsdk/workflow/ticket/status
Get workflow ticket status
Venafi_Core_WebSDK_WorkflowTicketRest_TicketStatus body → 200400401500
POST
/vedsdk/workflow/ticket/updatestatus
Update workflow ticket status
Venafi_Core_WebSDK_WorkflowTicketRest_TicketUpdateStatus body → 200400401500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Core_WebSDK_WorkflowTicketsWebResponse (14 properties), Core_WebSDK_WorkflowTicketsWebRequest_ticket_updatestatus (5 properties), Core_WebSDK_WorkflowTicketsWebRequest_ticket_create (5 properties), Core_WebSDK_WorkflowTicketsWebRequest_ticket_enumerate (2 properties). Each schema is shown below with its type and property counts.

Core_WebSDK_WorkflowTicketsWebRequest_ticket_updatestatus
object
5 properties 2 required
Core_WebSDK_WorkflowTicketsWebRequest_ticket_status
object
1 property 1 required
Core_WebSDK_WorkflowTicketsWebRequest_ticket_exists
object
1 property 1 required
Core_WebSDK_WorkflowTicketsWebRequest_ticket_create
object
5 properties 5 required
Core_WebSDK_WorkflowTicketsWebRequest_ticket_delete
object
1 property 1 required
Core_IdentityType
integer
0: Undefined Undefined 1: User User object 2: Group Group object 4: Container Container of users and groups 8: DistributionList Distribution List 16: Machine M…
Core_WebSDK_WorkflowTicketsWebRequest_ticket_enumerate
object
2 properties
Core_WebSDK_WorkflowTicketsWebResponse
object
14 properties
Core_WorkflowResult
integer
0: None None 1: Success Success 2: GenericFailure Nondescript failure 3: TicketDoesNotExist The referenced ticket does not exist 4: InsufficientPrivileges Not…
Core_IdentityEntry_EntryState
integer
0: Normal No special state associated with the entry 1: Disabled The identity has been disabled 2: LockedOut The identity has been locked out 4: Deleted The id…
Core_WebSDK_WorkflowTicketsWebRequest_ticket_details
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

venafi-legacy-workflow-apis-api-openapi.yml Raw ↑

Other APIs Venafi publishes across the network.

Venafi Access Management APIs API
Venafi AlgorithmSelector APIs API
Venafi Application API
Venafi Authentication Server APIs API
Venafi Certificate Approvals API
Venafi Certificate Auto-renewal Monitoring API
Venafi Certificate Discovery API
Venafi Certificate Expiration Reports API
Venafi Certificate Import API
Venafi Certificate Installations API
Venafi Certificate Inventory Monitoring API
Venafi Certificate Management APIs API
Where this information came from

This is an independent, third-party profile of Venafi Legacy Workflow APIs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.