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

Conductor OSS Metadata API

The Metadata API from Conductor OSS — 4 operation(s) for metadata.

Conductor OSS Metadata API is one of 5 APIs that Conductor OSS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Metadata. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 9 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 3.x.

Requests are made against a single base URL, {baseUrl}/api.

9 operations 4 paths 3 schemas 2 DELETE4 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.x
Base URL
http://localhost:8080/api
License
Resource Areas
1

Paths & Operations 9

Across 4 paths, the API surfaces 9 operations — 2 DELETE, 4 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Metadata 9
GET
/metadata/workflow
List workflow definitions
listWorkflowDefinitions → 200
POST
/metadata/workflow
Register a workflow definition
registerWorkflowDefinition body → 204
PUT
/metadata/workflow
Update workflow definitions
updateWorkflowDefinitions body → 204
GET
/metadata/workflow/{name}
Get workflow definition
getWorkflowDefinition 2 params → 200
DELETE
/metadata/workflow/{name}
Delete a workflow definition
deleteWorkflowDefinition 2 params → 204
GET
/metadata/taskdefs
List task definitions
listTaskDefinitions → 200
POST
/metadata/taskdefs
Register task definitions
registerTaskDefinitions body → 204
GET
/metadata/taskdefs/{taskType}
Get task definition
getTaskDefinition 1 param → 200
DELETE
/metadata/taskdefs/{taskType}
Delete a task definition
deleteTaskDefinition 1 param → 204

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are WorkflowTask (15 properties), TaskDef (15 properties), WorkflowDef (13 properties). Each schema is shown below with its type and property counts.

TaskDef
object
15 properties 1 required
WorkflowTask
object
15 properties 3 required
WorkflowDef
object
13 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

conductor-oss-metadata-api-openapi.yml Raw ↑

Other APIs Conductor OSS publishes across the network.

Conductor MCP Server
Conductor OSS Events API
Conductor OSS Tasks API
Conductor OSS Workflow API
Where this information came from

This is an independent, third-party profile of Conductor OSS Metadata 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.